Security Architecture for Software Architects
Security architecture designs protection into the structure of a system instead of adding it afterwards. Zero trust treats every request as untrusted and verifies identity and context each time, while threat modelling identifies what can go wrong and compliance requirements, such as audit and data residency, constrain the design.
Stage: Security, Reliability and Cost · Part of the Software Architect roadmap · Last reviewed 19 November 2026
What to learn in Security Architecture
- Explain zero trust principles and how they differ from perimeter security
- Design service-to-service authentication with mutual TLS or tokens
- Apply least privilege to roles and cloud permissions
- Run a STRIDE threat model on a data flow diagram
- Map a compliance requirement to a concrete design control
- Plan secrets management and key rotation
Security Architecture interview questions
What is threat modelling and when do you do it?
It is a structured way to find security risks by examining a system's components, data flows and trust boundaries, for example using STRIDE. It is best done at design time, when fixes are cheap, and repeated when the design changes.
What does zero trust mean?
Zero trust assumes no request is trustworthy just because it comes from inside the network. Every user and service is authenticated and authorised on each access, with least privilege and continuous verification, rather than relying on a trusted perimeter.
Where Security Architecture fits in the Software Architect roadmap
Security Architecture belongs to the Security, Reliability and Cost stage (advanced level), which takes about 7 hours. The non-negotiables.
Other units in this stage
Back to the full Software Architect roadmap