Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A security architect translates risk decisions into system design: patterns, standards, threat models, and control choices made before a system is built rather than after it breaks.

What Does a Security Architect Do?
A security architect decides how security is built into systems rather than bolted onto them. The role sits between risk management, which says what the organisation will and will not accept, and engineering, which builds the thing, and its output is design: patterns, standards, reference architectures, and documented decisions that other people implement.
The measure of a good one is unglamorous. Fewer surprises at the end of projects, fewer exceptions on the risk register, and fewer security requirements discovered the week before launch.
Architects are judged on artefacts, not opinions. The common deliverables are:
Most architects hold some form of design authority: a project cannot proceed to build without sign-off, or must record an exception if it deviates from an approved pattern. Used well, this is a fast mechanism. Used badly it becomes a gate that teams route around, and delivery managers learn to avoid the architecture forum entirely.
The architects who stay effective treat approval as a service with a response time, publish patterns teams can self-serve, and reserve formal review for designs that are genuinely novel or high risk. The NCSC’s secure design principles capture the same philosophy in five themes: establish the context, make compromise difficult, make disruption difficult, make compromise detection easier, and reduce the impact of compromise. They are a better starting point for a design conversation than a control catalogue, because they describe intent.
| Role | Question it answers |
|---|---|
| Security architect | How should this system be designed so the risk is acceptable? |
| Security engineer | How do I build, configure, and run the control that design requires? |
| Risk manager | Is this level of risk acceptable to the organisation at all? |
| Enterprise architect | How do all systems fit together to serve the business strategy? |
| Penetration tester | Does the implemented design actually resist attack? |
The boundary with engineering is the one most often blurred. Architects who cannot build lose credibility quickly; architects who spend their week building stop producing the patterns everyone else needs.
Technical breadth comes first: identity and federation, network design, cryptography at the level of choosing protocols rather than implementing them, cloud platform security models, and enough application knowledge to reason about a service mesh or a message queue. Zero trust and defence in depth are the two structural ideas most designs lean on, and knowing when each is overkill is part of the craft.
The non-technical half is where architects succeed or fail. Writing clearly enough that a design decision survives the departure of its author, explaining a trade-off to a product owner in terms of cost and delivery, and accepting that “no” is rarely available as an answer: the realistic job is finding the design that makes an acceptable version of what the business wants.
Formal frameworks exist. SABSA is the best known security architecture method, structuring design from business attributes downwards; TOGAF provides the enterprise architecture scaffolding many organisations already use. In the UK, the Cyber Security Council’s chartered titles cover secure system architecture, continuing the specialism formerly recognised through the NCSC Certified Cyber Professional scheme, and both appear in public sector procurement requirements.
Few architects start as architects. The usual background is five to ten years in infrastructure, network, cloud, or software engineering, often with a period in security operations that teaches what actually gets detected. For analysts weighing up this move, it is one of the branches off the security analyst career path, and reading real incident and test reports is the fastest way to learn which designs fail in practice, which is why architects with operational scars write better patterns than those with only frameworks.
If you want an independent view of an existing design before it goes live, our infrastructure and architecture review services assess designs against both attack paths and compliance requirements.
The architect decides what should be built and why, producing designs, patterns, and requirements based on a threat model and the organisation’s risk appetite. The engineer builds, configures, and operates the controls that result. The roles overlap in small organisations, where one person does both, but the split becomes necessary once several delivery teams need consistent guidance.
They need to read code and understand how systems are built, even if they rarely ship production software. An architect who cannot follow an authentication flow in source, inspect an infrastructure-as-code template, or reason about an API contract will produce designs engineers quietly ignore. Writing proof-of-concept patterns and reference templates is a common and useful part of the job.
SABSA for security architecture method, TOGAF where the organisation already uses it for enterprise architecture, and the NCSC secure design principles for practical guidance. Control catalogues such as ISO 27001 Annex A and NIST SP 800-53 supply the detail once a design decision is made. Frameworks structure the thinking; they do not replace knowing the technologies in play.
By publishing reusable patterns teams can adopt without a meeting, setting a predictable turnaround for design reviews, and reserving formal approval for genuinely novel or high-risk designs. Embedding with delivery teams early is more effective than reviewing finished designs, because changing a decision before build costs hours rather than the weeks it costs afterwards.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.