Direct answer
An architecture security review is a structured assessment of how a system is designed to protect data and enforce trust. It maps trust boundaries, identity and access paths, sensitive data flows, and control gaps — usually before or during major builds — so teams fix design risks earlier than a late-stage pen test can.
When is an architecture security review most valuable?
It is most valuable before a major launch, during a platform rewrite, when adopting multi-tenant SaaS patterns, moving to zero-trust or new identity providers, or after an incident that suggests design-level failure rather than a single bug.
What methods are commonly used?
Reviewers typically combine document and diagram analysis with facilitated threat modelling (for example STRIDE or PASTA), abuse-case walkthroughs, and control mapping against references such as NIST SP 800-207 (Zero Trust) and OWASP ASVS architecture-relevant requirements. The output should be decision-ready for engineering leads — not only a slide narrative.
What should the deliverable include?
A strong deliverable includes a boundary diagram or clarified data-flow view, prioritised findings with risk rationale, open design decisions, and a short remediation sequence. See our fictional architecture review sample and threat model sample for format depth.
How does it relate to penetration testing?
Architecture review asks “is this design sound?” Pen testing asks “can this implementation be broken today?” Teams that only pen test often rediscover the same class of issues; architecture review prevents whole categories of findings.
Related service
If you need this work delivered, see Architecture Security Review or start a conversation.