When I first stepped into the world of UX design, I thought “edge cases” were my biggest challenge, considering how a button behaves, or how a form fails, or what happens if someone abandons a checkout at 99 %. But one afternoon changed my perspective forever.
It was during a sprint planning session with our engineering and security team. Someone mentioned that a recent industry report projected global cybercrime losses at approximately US $10.5 trillion by 2026; yes, trillion with a T factoring in downtime, reputational damage, lost productivity and recovery costs. I sat there stunned.
Earlier that week, I’d been quietly proud of how intuitive my onboarding flows were. But then I heard about a breach at a major auto manufacturer; the Jaguar Land Rover cyberattack in 2025, which knocked production offline and ultimately cost the UK economy nearly £1.9 billion.
That’s when it hit me: UX isn’t just about what feels good — it’s about what keeps users safe.
UX Design Is No Longer “Just UX”, It’s Safety Design
For years, UX teams focused on accessibility, aesthetics, and persona-based workflows. But today, the user journey can’t be separated from the attack surface that journey travels.
A login screen is not just a UI element; it’s a potential vector for credential stuffing, phishing, or brute force attacks. A data export button isn’t just a feature; it could be a floodgate for mass data leakage if misconfigured.
Threat Modeling: Your New UX Tool
Threat modeling might sound like something only security engineers care about, but it’s one of the most powerful ways to anticipate how users might not behave or how attackers could exploit your work.
Here’s how I apply it to my design process:
- Define the asset and risk scenario: What data flows through this feature? Who has access? What happens if it leaks?
- In a recent payments project, I sketched out how an attacker could pivot from a forgotten password flow to gain unauthorized access. That informed a decision to redesign that flow entirely.
- Evaluate vulnerability exposure: Which steps in the user journey are unauthenticated, insecure, or easily mimicked by automated scripts?
- Seeing how bots hammered our support forms in production taught me that rate limits + CAPTCHA aren’t just page design choices, they’re protective barriers.
- Align security controls to UX outcomes: Security should complement, not contradict usability. Tools like multifactor authentication (MFA) don’t just prevent breaches; they communicate that you value the user’s safety.
- Collaborate early with security professionals: Invite them into design sprint retros, not just code reviews.
Security Patterns Every UX Designer Should Know
Here are a few security techniques that translate directly to UX design decisions:
- Principle of Least Privilege: Users should have only the access they need, nothing more.
- This often means reducing cognitive overload: don’t show options a user will never use or shouldn’t touch.
- Multifactor Authentication (MFA): Adds resilience without sacrificing flow, when designed empathetically (e.g., SMS + contextual prompts), users adopt it willingly.
- Progressive Disclosure of Risk: Don’t overwhelm users with security jargon upfront. Explain why you’re asking for permissions, this builds trust and understanding.
Why This Matters Now
Cyber attacks don’t wait; every 39 seconds, a new attack attempt hits businesses somewhere in the world. With rising digital transformation and remote work, the “attack surface” has ballooned.
And here’s the rub; most breaches aren’t due to exotic malware- they start with human error, reused passwords, misplaced trust, or predictable UI affordances.
As UX practitioners, we are the guardians of how users interact with technology. If we don’t think about security flows as part of UX flows, users will pay the price.
Final Thought
Security isn’t just a checkbox or a compliance requirement, it’s an experience promise. We protect users not just from friction, but from harm. And in a world where losses are measured in trillions, it’s time all UX designers include threat modeling by default in their design playbooks.
