Security architects who cannot speak the enterprise architecture team's language end up reviewing designs after the decisions are made, instead of shaping them. In many large organisations that language is the TOGAF Standard from The Open Group. This guide explains what a security architect needs from TOGAF: which certifications exist and what the exams involve, where security sits in the Architecture Development Method (ADM) according to the Open Group's own security Series Guide, how TOGAF and SABSA fit together, and how to apply this in practice without adopting the whole framework. It is written for security architects, enterprise architects who own security outcomes, and security leaders deciding whether TOGAF training is worth the time. It summarises public Open Group material, checked in November 2026, and does not reproduce the standard. For SABSA itself, see the SABSA guide.
Key takeaways
- TOGAF is an enterprise architecture method, not a security framework. Its value to a security architect is a shared method and vocabulary with the architects who make the design decisions.
- The security content lives in a Series Guide. The TOGAF Standard, 10th Edition is split into Fundamental Content and Series Guides; security is covered by "Integrating Risk and Security within a TOGAF Enterprise Architecture", developed by The Open Group Security Forum.
- Security touches every ADM phase. The guide places security drivers, principles and risk appetite in the Preliminary Phase, a security policy architecture, domain model and risk register in Phase B, and a Security Services Catalog in Phase C.
- The Foundation exam is short and closed book; the Practitioner adds scenarios. OGEA-101 is 40 multiple-choice questions in 60 minutes with a 60% pass mark; the combined OGEA-103 adds 8 open-book scenario questions in 90 minutes.
- TOGAF and SABSA are designed to work together. The Open Group and The SABSA Institute published an integration white paper in 2011, and the security Series Guide uses SABSA business attribute profiling and places security services in SABSA's logical layer.
What TOGAF is and why security architects meet it
The TOGAF Standard is The Open Group's framework for developing and governing an enterprise architecture. Its core is the ADM, an iterative cycle of phases that takes an organisation from architecture principles and vision through business, information systems and technology architectures to migration planning, implementation governance and change management. The current edition is the TOGAF Standard, 10th Edition, published in April 2022, which the Open Group divides into:
- Fundamental Content: the core concepts and practices, including the ADM, architecture content and governance.
- Series Guides: guidance on configuring and applying the Fundamental Content for particular needs, such as agile delivery, digital, business architecture and security.
TOGAF Standard, Version 9.2 is still referenced and still has its own certifications, so you will meet architects trained on either edition. Download of the standard is offered through the Open Group as a licensed download; check the licence terms on the Open Group site before using its text in internal methods or training material.
A security architect meets TOGAF in three ways: as a reviewer in an architecture board that follows the ADM, as the author of security deliverables that must fit TOGAF artefact names and phases, and in job descriptions that list TOGAF certification. The Security Architect Career Guide covers the role itself; this page covers the TOGAF part.
TOGAF certifications and exams
The Open Group runs the TOGAF certification portfolio. The facts below come from the Open Group's certification pages, checked on 14 November 2026; exam details change, so confirm before booking.
| Certification or credential | Based on | Exam | Format (as published) | Relevance to security architects |
|---|---|---|---|---|
| TOGAF Enterprise Architecture Foundation | 10th Edition | OGEA-101 (EA Part 1) | 40 multiple-choice questions, 60 minutes, pass mark 60% (24 of 40), closed book, no prerequisites; test centre or online proctored | Vocabulary and ADM structure; enough to work in an architecture board |
| TOGAF Enterprise Architecture Practitioner | 10th Edition | OGEA-102 (Part 2) after Part 1, or OGEA-103 (combined) | Combined exam: 48 questions in 150 minutes; Part 2 is 8 scenario-based questions in 90 minutes, open book with an electronic copy of the body of knowledge, pass mark 24 of 40; both parts must be passed | Applying the ADM to situations; useful for lead and principal architects |
| TOGAF EA Bridge | 9.2 to 10th Edition | OGEA-10B | For holders of TOGAF 9 Certified | Upgrade path for architects trained on 9.2 |
| TOGAF Business Architecture Foundation | 10th Edition | Business Architecture Part 1 | Foundation level exam on business architecture | Helps when shaping security requirements with business architects |
| Integrating Risk and Security (certification credential) | Security Series Guide | Short learning path | The Open Group describes its credentials as short learning paths starting at about 3 hours | The only security-specific item in the TOGAF portfolio |
| TOGAF 9 Foundation and TOGAF 9 Certified | Version 9.2 | Legacy exams | Still listed in the portfolio | Common on existing CVs; equivalent vocabulary |
- Retakes: for the combined Practitioner exam, a candidate who fails one part retakes only that part, after waiting one month.
- Training: the Open Group recommends an accredited training course, which typically includes the exam voucher. Practitioners who complete Practitioner Learning Studies with an accredited provider can earn an Applied Practitioner badge.
- Not a security credential: TOGAF certification shows you know an architecture method. It does not replace security architecture credentials such as SABSA or the ISC2 ISSAP concentration; see the ISC2 CISSP Concentrations Guide and the Cybersecurity Certifications Guide.
Security in the ADM: the Integrating Risk and Security Series Guide
The Open Group lists one Series Guide under security architecture: "Integrating Risk and Security within a TOGAF Enterprise Architecture", developed by The Open Group Security Forum and readable on the Open Group publications site. Its premise is that security is a cross-cutting concern: it touches the business, data, application and technology domains that the ADM develops, so parts of the security architecture must be built in step with the enterprise architecture rather than bolted on afterwards. It also deliberately avoids being a controls checklist, and it takes a broad view of risk based on ISO 31000, in which uncertainty can have positive as well as negative effects on objectives.
The table summarises, in our own words, the security activities and artefacts the guide associates with each phase.
| ADM phase | Security focus (summary) | Typical security deliverables |
|---|---|---|
| Preliminary | Set the ground rules for security in architecture work | Security drivers and principles, risk appetite, key risk areas and business impact analysis, security architect role and governance |
| A: Architecture Vision | Show stakeholders the target risk is acceptable | Security stakeholders and concerns, a high-level security blueprint, business case material starting from a SABSA business attribute profile |
| B: Business Architecture | Express security in business terms | Security policy architecture, security domain model, trust framework, risk assessment, business risk model or risk register, registers of applicable law and regulation and of control frameworks |
| C: Information Systems Architectures | Define security services and data handling | Security Services Catalog (security services treated as architecture building blocks), security classification of assets, data quality ownership and measures |
| D: Technology Architecture | Confirm technology realises earlier decisions | Usually no dedicated artefact; optionally a technology security view linking technologies to the business risks they mitigate |
| E: Opportunities and Solutions | Turn security building blocks into solutions | Security value measures in work packages, solution building blocks, risk mitigation plan including risks introduced by the new architecture |
| F: Migration Planning | Secure the transition itself | Transition risk assessment, rollback planning, security impact analysis of the target state |
| G: Implementation Governance | Check what is built matches what was designed | Security audit of designs, code and configuration, security testing, training and awareness |
| H: Architecture Change Management | Keep the architecture current as threats change | Security impact analysis for significant changes, security expertise in the governance body, new ADM iterations when threats, compliance or vulnerabilities demand it |
| Requirements Management | Trace security requirements to business goals | Business attribute profiling with metrics and targets, control objectives derived from business objectives, ongoing validation |
The guide positions itself relative to other standards as references rather than formal mappings: ISO/IEC 27001 for the security management system, ISO 31000 for enterprise risk management, Open FAIR for quantitative risk analysis, O-ISM3 and O-ESA from The Open Group, COBIT for governance, the NIST Cybersecurity Framework and SABSA. Note that it cites ISO/IEC 27001:2013, ISO 31000:2009 and the original 2014 NIST CSF; if you use it today, map its artefacts to ISO/IEC 27001:2022 and NIST CSF 2.0 yourself. For quantitative risk, see the FAIR Model and Open FAIR Standard Guide.
TOGAF and SABSA: how they fit
TOGAF answers "how do we develop and govern an enterprise architecture"; SABSA answers "how do we derive security from business requirements and prove traceability". They overlap in method but differ in focus, which is why The Open Group's Security and Architecture Forums and The SABSA Institute published a joint TOGAF and SABSA integration white paper in November 2011, built around SABSA business attributes profiling.
| Question | TOGAF | SABSA |
|---|---|---|
| Primary purpose | Enterprise architecture development and governance | Business-driven security architecture |
| Core structure | ADM phases and architecture content | Layered matrix from contextual to component, with traceability |
| Who uses it | Enterprise, solution and business architects | Security architects |
| How security appears | Through the Integrating Risk and Security Series Guide | Throughout, as the subject of the method |
| Where they meet | Business attribute profiles captured with business architecture (Phase A and B); security services defined as building blocks in Phase C, aligned with SABSA's logical layer; traceability carried by requirements management | |
Choosing between them: if your organisation already runs an architecture board on TOGAF, learn TOGAF enough to work inside it and use SABSA techniques for the security content. If there is no enterprise architecture practice, SABSA alone, or a lighter method, may serve a security team better. Most security architects benefit from TOGAF Foundation level vocabulary; Practitioner level makes sense when you lead architecture work across domains.
Applying it in practice
- Find out how your organisation actually uses TOGAF: which edition, which phases the architecture board enforces, and which artefacts it expects. Many organisations use the ADM loosely; match the real practice, not the book.
- Agree security artefacts and owners in the Preliminary Phase equivalent: security principles, risk appetite statement, and which security deliverables each architecture engagement must produce. Record the security architect's sign-off points.
- Build a Security Services Catalog: describe identity, access, logging, key management, secrets and data protection services as reusable building blocks with conceptual definitions and operational owners, so solution teams consume services instead of designing controls each time.
- Use business attribute profiles in Phases A and B: express security needs as measurable attributes (for example available, auditable, access controlled) with metrics, so they survive into requirements management.
- Add security checkpoints to Phases E to G: risk mitigation plans in work packages, transition risk and rollback in migration plans, and design and configuration reviews and testing in implementation governance.
- Wire Phase H to threat and vulnerability intake: define which security events (new threat, regulatory change, critical vulnerability in a core building block) trigger an architecture change request.
- Pilot on one engagement, then standardise: trial the artefact set on one programme, cut what nobody used, and only then publish it as the house method.
Small organisations: take the artefact ideas (principles, risk register, services catalog, change triggers) without formal ADM governance. Large organisations: embed security deliverables in the architecture repository and board terms of reference so they cannot be skipped.
Where identity fits
Identity is one of the services that benefits most from TOGAF's building block approach. Defining workforce identity, privileged access and non-human identity (service accounts, workload identities, API keys, AI agents) as catalogued security services in Phase C gives every solution a standard way to authenticate and authorise, and gives the architecture board a place to ask how each new system's machine identities are issued, rotated and retired. The trust framework and security domain model in Phase B are also where federation with partners and cloud providers should be recorded. For the identity architecture itself, see the SABSA guide's identity section and the AI Security Architecture Reference Guide.
Measuring whether it works
- Coverage: share of architecture engagements with security deliverables completed before the design decision gate.
- Reuse: share of new solutions consuming catalogued security services rather than bespoke controls.
- Traceability: share of security requirements traced to a business attribute or risk register entry.
- Late findings: number of security design issues found in Phase G or after go-live that should have been caught in Phases B to D; this should fall.
- Change responsiveness: time from a security change trigger to an approved architecture change.
Common failure patterns
- Security joins at Phase D: the security architect is invited only to the technology review, after business and data decisions have fixed the risk profile.
- Certification without practice: a TOGAF certificate on the team, but no security deliverables written into the board's terms of reference, so nothing changes.
- Artefact overload: every artefact in the Series Guide produced for every project, which slows delivery and teaches teams to treat security as paperwork.
- Stale references: mappings still pointing at ISO/IEC 27001:2013 or the 2014 NIST CSF because the Series Guide cites them, rather than current editions.
- No owner for the services catalog: a catalog written once and never maintained, so solution teams stop trusting it.
- Machine identities left out: identity services catalogued for people only, leaving service accounts and API keys to each project.
Framework mapping
| Framework | Reference | Link to TOGAF security work |
|---|---|---|
| NIST SP 800-53 Rev 5 | PM-7 Enterprise Architecture; PL-8 Security and Privacy Architectures | Controls that explicitly require an enterprise architecture and a security architecture aligned with it |
| NIST SP 800-53 Rev 5 | SA-8 Security and Privacy Engineering Principles; SA-17 Developer Security and Privacy Architecture and Design; PM-9 Risk Management Strategy | Principles, design and risk strategy captured in the Preliminary Phase and Phases A to C |
| NIST CSF 2.0 | GV.OC-01, GV.RM-01, GV.PO-01, GV.RR-02 | Mission context, risk objectives, policy and roles: Preliminary Phase and Phase B outputs |
| NIST CSF 2.0 | ID.RA-05 | Risk assessment and prioritisation used in Phases B and E |
| ISO/IEC 27001:2022 Annex A | 5.8 Information security in project management; 8.27 Secure system architecture and engineering principles | Security built into architecture and change work |
Practitioner checklist
- Confirm which TOGAF edition and which ADM phases your architecture board actually uses.
- Take TOGAF Foundation (OGEA-101) if you sit on architecture boards; consider Practitioner if you lead cross-domain architecture.
- Read the Integrating Risk and Security Series Guide on the Open Group publications site and choose the artefacts you will actually use.
- Write security principles, risk appetite and security sign-off points into the board's terms of reference.
- Publish and maintain a Security Services Catalog that includes identity and non-human identity services.
- Use business attribute profiles to carry security requirements from Phase A into requirements management.
- Define the security events that trigger Phase H change, and map artefacts to ISO/IEC 27001:2022 and NIST CSF 2.0.
- Track coverage, reuse, traceability and late findings to show the integration is working.
Standards and references
- The Open Group: TOGAF Series Guide, Integrating Risk and Security within a TOGAF Enterprise Architecture
- The Open Group: Security and Risk Concepts in the TOGAF ADM
- The Open Group: The TOGAF Standard
- The Open Group: TOGAF Certification Portfolio
- The Open Group: TOGAF Enterprise Architecture Part 1 Exam
- The Open Group: TOGAF Enterprise Architecture Combined Part 1 and Part 2 Exam
- The Open Group: TOGAF and SABSA integration guide announcement
Related NHI Mgmt Group resources: SABSA · Security Architect Career Guide · ISC2 CISSP Concentrations Guide · FAIR Model and Open FAIR Standard Guide