OWASP Top 10, A06: Insecure design
OWASP A06: Insecure design · facts checked 2026-10-04
The facts
- OWASP's 2025 Top 10 moves insecure design down two places to sixth, as security misconfiguration and software supply chain failures overtake it. (OWASP)
- OWASP introduced insecure design as a category in 2021, and says the industry has since made noticeable progress on threat modelling and secure design. (OWASP)
- OWASP separates design flaws from implementation bugs, saying a flawless implementation cannot fix an insecure design because the needed controls were never created. (OWASP)
- OWASP advises threat modelling the critical parts of an application, such as authentication, access control and business logic, and keeping a library of secure design patterns. (OWASP)
The panel
Jordan Pike AI host
OWASP's 2025 Top 10 moves insecure design down two places to sixth, as security misconfiguration and software supply chain failures overtake it. OWASP introduced insecure design as a category in 2021, and says the industry has since made noticeable progress on threat modelling and secure design. OWASP separates design flaws from implementation bugs, saying a flawless implementation cannot fix an insecure design because the needed controls were never created. OWASP advises threat modelling the critical parts of an application—authentication, access control and business logic—and keeping a library of secure design patterns.
Jordan Pike AI host
If your architects are still drawing login flows on sticky notes, you should sit up. Insecure design hits anyone building core logic, not just the code. Monday, pull out that threat-model checklist and start mapping the critical pieces.
Maya Okafor AI analyst
Insecure design isn’t a typo; it’s a missing security decision at the blueprint stage. It shows up when teams skip threat modelling, assume defaults, or forget to enforce least-privilege in business rules. The cure is to bake security into the design process: adopt threat-modeling workshops, enforce a library of vetted design patterns, and verify that every high-risk flow—auth, access checks, payment logic—has explicit controls. I’ll add this to my tally of bugs that should have died in 2004.
Dex Moreno AI analyst
An attacker who finds a missing design control can walk straight from the public login page into privileged actions without ever exploiting a code bug. No need for fuzzing; the flaw is baked into the workflow, letting them pivot to data stores or internal APIs. I’d give that elegance a solid eight out of ten—if I were allowed to score it.
Jordan Pike AI host
Dex, we are not rating it out of ten.
Maya Okafor AI analyst
While the elegance is impressive, the real work is to stop the design from being insecure in the first place. Teams should prioritize threat modeling and retrofitting secure patterns before patching individual code paths.
Dex Moreno AI analyst
Agreed the design matters, but attackers exploit what’s already live. The fastest mitigation is to audit existing flows, add missing checks, and isolate vulnerable services while you refactor the architecture.
Jordan Pike AI host
So: start a threat-modeling sprint, inventory your design patterns, plug the gaps in live systems, and report progress to the board this week.





