Enterprise architecture describes what the organisation consists of and how it changes; GRC describes what must apply, which risks are acceptable and how to evidence this. Run separately, they produce duplicate inventories, two boards, two risk languages and evidence with no link to the architecture. Integrated, they form one management system that steers change and control at the same pace.
TOGAF and GRC unified: one integrated management system, run agentically
How to combine enterprise architecture based on the TOGAF Standard with governance, risk and compliance into one integrated management system: one model, one cycle joining the ADM and the management system cycle, one governance, one evidence chain — and how AI agents support operations with human approval. With interactive ADM cycle, decision aid, integration navigator, integration check and CISO whitepaper.
Actualizado: noviembre de 2026 · Valeri Milke, Lead Auditor ISO 27001 e ISO 42001
You receive the download link immediately on the page and by email.
TOGAF Standard, 10th Edition × ISO management systems · one IMS
- AVision
- BBusiness
- CData & Apps
- DTechnology
- ESolutions
- FMigration
- GImplement
- HChange
A Architecture Vision · objectives, stakeholders, obligations and initial risksB Business Architecture · assess capabilities and critical functionsC Data and Applications · inventories as views of one modelD Technology · service providers, locations and dependenciesE Opportunities and Solutions · controls as building blocks, risk treatmentF Migration Planning · roadmap linked to risks and deadlinesG Implementation Governance · Architecture Contracts and reviews as evidenceH Architecture Change Management · monitoring, management report, improvement
1model for architecture and GRC9ADM phases in the management system0TOGAF certificates for organisations
9ADM phases from Preliminary to H — with Requirements Management at the centre of the cycle
7Main clauses of the Harmonized Structure (4 to 10) — shared by ISO/IEC 27001, ISO 9001, ISO 22301, ISO/IEC 42001 and other standards
5 in 1Registers — asset inventory, register of information, AI inventory, records of processing activities, SBOM — as views of one model
54Mappings in the integration navigator, from ISO-HS and ISO/IEC 27001 to NIS2, DORA, the EU AI Act, CRA and GDPR
Enterprise architecture and GRC answer two sides of the same question. Architecture describes what an organisation consists of and how it changes — capabilities, processes, applications, data, technology, service providers. GRC describes what must apply, which risks are acceptable and how to evidence both. In many organisations the two disciplines work separately: with their own inventories, their own boards and their own risk language. The result is duplicated maintenance, inconsistent data and audits for which evidence has to be laboriously pieced together. With the Architecture Development Method (ADM), the Enterprise Metamodel, the Architecture Repository and architecture governance, the TOGAF® Standard from The Open Group provides the tools to change this. Combined with the Harmonized Structure of the ISO management system standards, the result is an integrated management system: inventories become views of one model, the ADM phases carry the management system cycle, and evidence is generated in the process. Because such a system contains structured data instead of mountains of documents, AI agents can work on it — with clear permissions, a preview before every change and approval by humans.
Why now: standards and obligations that demand architecture knowledge
From the modular TOGAF Standard to the full application of the Cyber Resilience Act — the dates on which architecture and GRC have to come together.
25 April 2022
TOGAF Standard, 10th Edition
The Open Group publishes the TOGAF Standard in modular form: stable Fundamental Content and TOGAF Series Guides that evolve independently — including the guide on integrating risk and security.
25 October 2022
ISO/IEC 27001:2022
The new edition adopts the updated Harmonized Structure, including the planning of changes, and organises Annex A into 93 controls in four themes.
17 January 2025
DORA applies
Financial entities must identify ICT-supported business functions, assets and dependencies and maintain a register of information on their ICT third-party service providers — architecture knowledge becomes a supervisory obligation.
15 May 2025
TOGAF Technical Corrigendum 1
Corrections to the 10th Edition; in June 2025 the revised volumes are published as the “2025 Update”. To date there is no new edition after the tenth.
6 December 2025
NIS2 implementation in Germany
With the German NIS2 Implementation Act, the new BSI Act (BSIG) applies without a transition period: risk management measures, reporting obligations and the duty of executive management to implement the measures, oversee their implementation and take part in training.
2 August 2026
EU AI Act generally applicable
Transparency obligations and national supervision take effect. The Digital Omnibus on AI has postponed the high-risk obligations — for Annex III systems to 2 December 2027.
11 September 2026
CRA reporting obligations
Manufacturers report actively exploited vulnerabilities and severe incidents within 24 and 72 hours — those who know their product architecture and SBOM are faster.
2 December 2027
High-risk AI under Annex III
From this date, risk management, data quality, logging and human oversight apply to high-risk AI systems under Annex III — obligations that an architecture model with an AI inventory makes easier to meet.
11 December 2027
CRA fully applicable
All obligations of the Cyber Resilience Act apply to products with digital elements newly placed on the market — security by design becomes an architecture requirement.
Nine key statements on integrating TOGAF and GRC
Click a card to read the key statement in detail — or expand them all at once.
The TOGAF Standard, 10th Edition — since May 2025 with Technical Corrigendum 1 — is a framework for architecture work: Architecture Development Method (ADM), Enterprise Metamodel, Architecture Repository, governance and techniques. It is not a management system standard, offers no certification for organisations and does not automatically make anyone compliant. ISO/IEC 27001 and the other management system standards remain the certifiable ones; TOGAF certifications apply to individuals.
ISO management system standards such as ISO/IEC 27001, ISO 9001, ISO 22301, ISO/IEC 42001 and ISO/IEC 27701 share the same clause structure, from context and leadership through planning, support and operation to evaluation and improvement. This Harmonized Structure is the central pillar of an integrated management system — and the docking point for the ADM: every phase delivers outputs that a clause of the structure needs.
The ISMS asset inventory, the DORA register of information, the AI inventory as the basis for classification under the EU AI Act, the GDPR records of processing activities and the SBOM under the Cyber Resilience Act largely describe the same objects. In the integrated management system they are views of one architecture model with GRC attributes — maintained in one place, linked through relationships, analysable by capability.
The Preliminary Phase and Phase A clarify context, leadership, objectives and initial risks; Phases B to D assess risks against capabilities, applications, data and technology; E and F turn risk treatment into a roadmap; G generates evidence through Architecture Contracts and architecture compliance reviews; H monitors and improves. Requirements Management at the centre becomes the obligations register.
The Architecture Board and the GRC steering committee decide on the same initiatives, exceptions and risks. Merged, they become one board with one set of principles, one exception process — every approved deviation is also a risk acceptance with an expiry date — and one management report that shows the target state, risk posture and compliance status together.
Architecture compliance reviews, Architecture Contracts, change requests and board decisions become audit evidence as soon as they are linked to the control and the architecture element. An organisation can then show the chain from requirement via control and building block to evidence on demand — instead of searching for weeks before every audit.
A structured model is the prerequisite for agentic GRC: AI agents evaluate new requirements, analyse the impact of changes, map controls, collect evidence and draft reports. Write actions appear as proposals, the people responsible approve them, and low-risk routines run autonomously with logging. The agents themselves are subject to the management system's AI governance.
Nobody has to model the entire organisation before the integration delivers value. Start with one scope, a core metamodel and the most urgent register — for DORA or NIS2, for example. Then merge the boards and exception processes and expand the model and the use of agents along real obligations.
Four pillars and agentic operation: what holds the integrated management system together
What connects TOGAF and GRC — for each tab, the core idea, the key work steps and the building blocks from the TOGAF Standard and the ISO standards.
One repositoryPillar 1
- Extend the architecture model based on the TOGAF Standard's Enterprise Metamodel with requirement, risk, control and evidence
- Inventories and registers as filtered views instead of parallel lists
- Define the system of record for each object type — EA tool or GRC platform
Enterprise MetamodelArchitecture RepositoryArchiMateISO/IEC 27001 A.5.9
ADM × PDCAPillar 2
- Preliminary Phase and Phase A: context, leadership, objectives and initial risks
- Phases B to F: risk assessment on the model, treatment as a roadmap
- Phases G and H: evidence, monitoring, improvement — Requirements Management as the obligations register
ADMISO-HS 4–10Requirements ManagementRisk treatment
One boardPillar 3
- Merge the Architecture Board and the GRC steering committee
- One set of principles for architecture, security, data protection and compliance
- One exception process: dispensation equals risk acceptance with an expiry date
Architecture BoardArchitecture PrinciplesDispensationISO-HS 5, 9.3
One chainPillar 4
- Architecture Contracts with security and compliance requirements
- Architecture compliance reviews as audit evidence linked to the control
- Chain of requirement → control → building block → evidence available at any time
Architecture ContractCompliance ReviewGovernance RepositoryISO-HS 9.1–9.2
Humans decideOperation
- Agents read and edit the model through defined tools
- Preview before every change, approval by the people responsible, a complete log
- AI governance for your own agents: inventory, risk assessment, oversight
MCPHuman-in-the-LoopISO/IEC 42001EU AI Act
Interactive
Which integration path is right for you?
Up to three questions establish your starting point — from an organisation with an established architecture practice but no management system to a certified ISMS that wants to bring AI agents into operations. The recommendation is a VamiSec assessment, not an audit.
Your path
- 1?
1: Does your organisation have an established enterprise architecture practice — a maintained architecture model (in ArchiMate, for example), a repository and a board that makes architecture decisions?
1
Does your organisation have an established enterprise architecture practice — a maintained architecture model (in ArchiMate, for example), a repository and a board that makes architecture decisions?
This means more than a folder of diagrams: capabilities, applications, data and technology are modelled, owners maintain the model, and initiatives are checked against principles and the target state. Whether you follow TOGAF to the letter does not matter.
Build the management system on the architecture model
You already have what many ISMS projects lack: a reliable model of capabilities, applications, data and dependencies. Use it as the foundation. Context, scope and asset inventory are created as views of the repository, the Architecture Board takes on management review tasks, and the risk assessment starts from the architecture elements from the outset.
- Extend the metamodel with requirement, risk, control and evidence — with clear relationships to the existing elements
- Derive and justify the scope of the management system from the model
- Carry out the risk assessment per capability and application, plan treatment as roadmap work packages
- Extend the Architecture Board with risk and compliance roles and run it as the steering committee of the management system
- Plan internal audits and architecture compliance reviews together from the start
ISO-HS 4.3ISO-HS 6.1Architecture RepositoryArchitecture Board
A lean architecture model as the backbone of the management system
Your management system works, but inventories, risk analysis and supplier list live in separate spreadsheets. You do not need a full EA roll-out to change this. Start with a minimal model following TOGAF logic: capabilities, processes, applications, data objects, technology and service providers — exactly as deep as the risk assessment, the Statement of Applicability and regulatory requirements demand.
- Transfer the asset inventory into a model with relationships: which capability depends on which application, which service provider, which location
- Use the Preliminary Phase once for architecture and management system, and Phase A per initiative: define principles, stakeholders and scope together
- Add an architecture and compliance review for each major initiative to change management
- Only then decide whether an EA tool is needed or the GRC platform holds the model
ISO/IEC 27001 A.5.9TOGAF Phase ACapability MapMinimal model
Integration project: one model, one cycle, one governance
Both worlds exist — and with them duplicate inventories, two boards and two risk languages. The greatest lever lies not in new content but in bringing things together: aligning metamodels, feeding registers from one source, interlocking the ADM phases with the management system cycle and handling exceptions through one joint process.
- Metamodel alignment: which objects in the EA tool and in the GRC platform are the same, and which system is the system of record
- Agree on a common risk language — scales, risk appetite, acceptance rules
- Merge dispensations and risk acceptances into one exception process with expiry dates
- Link the Architecture Board and the management review: one report, one decision list
- Integrate first, then automate — agents require a clean model
Metamodel mappingADM × PDCAException processISO-HS 9.3
Integrate and run agentically — with approvals and a log
You have the foundations not only to connect GRC and architecture but to have them operated by AI agents: agents evaluate new requirements, analyse the impact of changes on risks and controls, collect evidence and draft reports. The framework is what matters: defined tools instead of unrestricted system access, a preview before every change, approval by the people responsible and a complete log.
- Complete the integration steps from the “Integration project” path first — agents amplify model errors
- Define a task catalogue with autonomy levels: read and propose, execute after approval, low-risk routines autonomously with logging
- Connect agents only through defined interfaces, such as an MCP server of the GRC platform, with minimal permissions
- Apply AI governance to your own agents: inventory, risk assessment, human oversight, logging
- Start with one use case — such as impact analysis of new requirements — and measure effectiveness
Human-in-the-LoopMCPISO/IEC 42001EU AI Act
Build along your obligations: registers first, the model as a by-product
When deadlines are pressing, start where regulation demands architecture knowledge: critical functions and their dependencies, the register of information for service providers, the AI inventory, the records of processing activities. Set up these registers as views of one shared model from the outset — the architecture model then emerges as a by-product of meeting your obligations, and the management system grows around this core.
- Set up an obligations register: which requirements apply, by when, and to which areas
- Record critical functions and their dependencies on applications, data, technology and service providers
- Generate the registers for service providers, AI systems and processing activities from the same model
- Set up the management system core based on the Harmonized Structure in parallel: policy, roles, risk process
- Base reporting channels and incident impact analysis on the model
NIS2DORAEU AI ActCRA
Starting together from scratch: Preliminary Phase and Harmonized Structure in one
Without existing structures and without acute regulatory pressure, you can take the clean route: architecture capability and management system are set up as one discipline from the start. The Preliminary Phase of the ADM and clauses 4 and 5 of the Harmonized Structure answer the same questions — context, scope, leadership, principles, roles.
- Determine context, stakeholders and scope once for both architecture and the management system
- Formulate a set of principles that unites architecture, security and compliance principles
- Define a minimal metamodel and model one value chain as a pilot
- Anchor a risk process based on ISO 31000 in architecture elements
- Plan the expansion along future obligations instead of modelling everything at once
Preliminary PhaseISO-HS 4–5ISO 31000Pilot
- Does your organisation have an established enterprise architecture practice — a maintained architecture model (in ArchiMate, for example), a repository and a board that makes architecture decisions?
- Do you already operate a management system based on ISO/IEC 27001 or another standard with the Harmonized Structure — certified or in active use?
- Do you operate a management system based on ISO/IEC 27001 or another ISO standard with the Harmonized Structure?
- Do you want AI agents with human approval to support recurring work — mapping, evidence collection, impact analyses, draft reports?
- Are you subject to NIS2, DORA, the EU AI Act or the Cyber Resilience Act — with obligations that take effect within the next twelve months or already apply?
Interactive
The integrated cycle: ADM phases with GRC tasks
Select a phase in the ring or in the list to see its goal, typical pitfalls, anchors in TOGAF, standards and regulation, work steps, guiding question and evidence. At the centre — as in the ADM cycle of the TOGAF Standard — sits Requirements Management, read here as the obligations register; around the outside wraps the agentic operating layer, an addition by VamiSec.
ADM phases
Cross-cutting
Preliminary Phase · ISO-HS 4 and 5 · Context, leadership, principles
Preliminary: setting up the architecture capability and the management system together
In the Preliminary Phase, the TOGAF Standard establishes how an enterprise carries out architecture work: organisation, principles, tailored approach, tools. The Harmonized Structure of the ISO management system standards poses exactly these questions in clauses 4 and 5 — context, scope, leadership, policy, roles. If you settle both in a single pass, you end up with one set of principles, one board and one scope instead of two of each.
BasisTOGAF Standard, 10th Edition: ADM, Preliminary Phase; Architecture Principles; Enterprise Architecture Capability and Governance; Series Guide “Integrating Risk and Security within a TOGAF Enterprise Architecture” (G152). ISO/IEC 27001:2022, clauses 4.1–4.4 and 5.1–5.3 (Harmonized Structure).
Typical pitfalls
- Two sets of principles, two boards, two scopes — the silos are locked in right from the start (critical)
- Management delegates the mandate instead of issuing it — without a mandate, the board decides nothing (critical)
- The framework is adopted unchanged instead of tailored: many artefacts, little value (medium)
- Tool decision before metamodel — the tool dictates the terminology instead of the other way round (medium)
Anchors in TOGAF, standards and regulation
TOGAF Preliminary PhaseTOGAF Architecture PrinciplesG152 · Risk Appetite, Security PrinciplesISO-HS 4.1–4.4ISO-HS 5.1–5.3NIS2 · Accountability of management bodies
Work steps
- Obtain a mandate from management for an integrated management system combining architecture and GRC
- Determine context and interested parties once — including supervisory authorities, auditors and customers
- Formulate a joint set of principles: architecture, security, data protection and compliance principles with rationale and implications
- Define risk appetite and key risk areas — as the TOGAF Series Guide on risk and security provides for the Preliminary Phase
- Tailor TOGAF: which phases, artefacts and level of detail are appropriate for your size
- Set up a joint board with rules of procedure — Architecture Board and GRC steering committee in one
- Define the core metamodel and systems of record before procuring tools
Guiding question for management and CISO
Do we have one scope, one set of principles and one board — or are we maintaining the same fundamental decisions twice?
Deliverables & evidence
- Management mandate and rules of procedure of the joint board
- Context analysis with interested parties and their requirements
- Approved set of principles
- Tailored process model
- Scope description
Phase A · ISO-HS 4.2, 6.1, 6.2 · Statement of Architecture Work
Architecture Vision: objectives, stakeholders, obligations and risks of the initiative
Phase A sets the frame for an iteration: stakeholders and their concerns, business goals, scope, constraints and an initial target vision. In the integrated management system, obligations and risks are included from the outset: which requirements from NIS2, DORA, the EU AI Act, the CRA or contracts affect the initiative, what risks and opportunities does it hold, and against which objectives does management want to measure it?
BasisTOGAF Standard, 10th Edition: ADM, Phase A; ADM Techniques (Stakeholder Management, Business Transformation Readiness Assessment, Risk Management). ISO/IEC 27001:2022, clauses 4.2, 6.1 and 6.2.
Typical pitfalls
- Regulatory requirements only surface at acceptance instead of in the vision (critical)
- Stakeholder analysis without supervisory authorities, auditors and data protection — their concerns are later missing as requirements (medium)
- Objectives without a metric: the management review cannot assess progress (medium)
- The scope of the initiative deviates from the scope of the management system without anyone noticing (medium)
Anchors in TOGAF, standards and regulation
TOGAF Phase AStatement of Architecture WorkStakeholder MapISO-HS 4.2ISO-HS 6.1ISO-HS 6.2
Work steps
- Extend the stakeholder map to include supervisory authorities, auditors, data protection and employee representation, and capture their concerns as requirements
- Assign relevant obligations from the obligations register to the initiative
- Identify transformation risks and mitigation activities — a fixed step in Phase A — and add an initial risk and opportunity assessment of the affected business capabilities
- Set measurable objectives for business value, risk reduction and compliance
- Statement of Architecture Work with scope, schedule and approval by the joint board
- Assess the organisation's readiness for change
Guiding question for management and CISO
At the start of the initiative, do we know the obligations, risks and objectives against which it will be measured?
Deliverables & evidence
- Architecture Vision with objectives and metrics
- Stakeholder map with concerns
- Initial risk and opportunity assessment
- Approved Statement of Architecture Work
Phase B · ISO-HS 6.1 · ISO 22301 · DORA critical or important functions
Business Architecture: capabilities, value streams, processes and their criticality
The Business Architecture describes what the enterprise can do and how it creates value: capabilities, value streams, processes, organisational units. For GRC, this is where criticality originates. If you assess protection needs, business impact and critical or important functions here, you obtain the basis for risk assessment, business continuity and supervisory reporting in a single step.
BasisTOGAF Standard, 10th Edition: ADM, Phase B; TOGAF Series Guides on Business Capabilities and Value Streams; G152 (Business Risk Model, Applicable Law and Regulation Register). ISO/IEC 27001:2022, clause 6.1; ISO 22301:2019 (business impact analysis); DORA.
Typical pitfalls
- Criticality is assessed three times, and differently each time, in the risk, BCM and DORA projects (critical)
- Capability map without owners — nobody feels responsible for assessment and maintenance (medium)
- Processing of personal data is not mapped to the processes — data protection is left out (medium)
- Overly granular process modelling ties up capacity without improving risk decisions (low)
Anchors in TOGAF, standards and regulation
TOGAF Phase BBusiness Capability MapG152 · Applicable Law and Regulation RegisterISO-HS 6.1ISO 22301 business impact analysisDORA · Critical or important functions
Work steps
- Create a two-level capability map and name an owner for each capability
- Assess criticality and protection needs once per capability — for risk, business continuity and supervision
- Flag critical or important functions within the meaning of DORA, or the services relevant to NIS2
- Map processing of personal data to the processes
- Maintain registers of applicable laws, regulations and control frameworks — the TOGAF Series Guide on risk and security places them in Phase B
- Pass on gaps between baseline and target capabilities as requirements to Phases C and D
Guiding question for management and CISO
Do we know which capabilities are critical for customers, supervisors and the survival of the business — and do we assess this in one place?
Deliverables & evidence
- Capability map with criticality and owners
- Business impact per capability
- List of critical or important functions
- Gap analysis from baseline to target (business)
Phase C · ISO/IEC 27001 Annex A 5.9, 5.12 · GDPR · EU AI Act
Data and Application Architecture: where information resides and where it flows
Phase C models data objects, applications and their interfaces. This produces exactly the information that the asset inventory, classification, records of processing activities and AI inventory need. In the integrated management system, these registers are no longer separate lists but filtered views of the model — with classification, owner, data flows and links to risks.
BasisTOGAF Standard, 10th Edition: ADM, Phase C (Data and Application Architecture); Architecture Content (catalogues and matrices). ISO/IEC 27001:2022, Annex A 5.9 and 5.12; GDPR; EU AI Act.
Typical pitfalls
- Asset inventory, application portfolio and AI inventory are maintained in parallel and contradict each other (critical)
- Data flows to service providers and AI models are missing from the model — precisely where data protection and data leakage risks arise (critical)
- Classification only at document level instead of on data objects (medium)
- Shadow IT and shadow AI go undetected because the model only captures projects (medium)
Anchors in TOGAF, standards and regulation
TOGAF Phase CArchitecture Definition DocumentG152 · Security ClassificationISO/IEC 27001 Annex A 5.9, 5.12GDPR · Records of processing activitiesEU AI Act · classification of AI systems
Work steps
- Model data objects with classification and owner
- Capture applications with interfaces and data flows — including SaaS, service providers and AI models
- Define the asset inventory, records of processing activities and AI inventory as views of the model
- Label AI systems and agents as application components with purpose, risk classification and data sources
- Assess risks per application and data flow, and formulate controls as requirements for building blocks
Guiding question for management and CISO
Can we show, for every critical data object, where it resides, who uses it, where it flows and which controls protect it?
Deliverables & evidence
- Application and data model with classification
- Asset inventory generated from the model
- Records of processing activities linked to the model
- AI inventory with risk classification
Phase D · ISO/IEC 27001 Annex A 5.19–5.23 · DORA · NIS2
Technology Architecture: platforms, locations, service providers and dependencies
The Technology Architecture describes platforms, networks, locations and cloud services — and with them the dependencies that NIS2 and DORA want to see. If you model service providers, data centres and concentration risks here, you generate the DORA register of information from the model, derive outage scenarios for business continuity and, in an incident, know quickly which functions are affected.
BasisTOGAF Standard, 10th Edition: ADM, Phase D; Architecture Content. ISO/IEC 27001:2022, Annex A 5.19–5.23; DORA (ICT third-party risk, register of information); NIS2 (supply chain security).
Typical pitfalls
- Dependency chains end at the data centre — subcontractors and concentration risks remain invisible (critical)
- Exit and fallback options are only discussed once a service provider fails (critical)
- Cloud resources change faster than the model is maintained (medium)
- Technical standards are not linked to controls — deviations have no consequences (medium)
Anchors in TOGAF, standards and regulation
TOGAF Phase DArchitecture Definition DocumentStandards LibraryISO/IEC 27001 Annex A 5.19–5.23DORA · Register of informationNIS2 · Supply chain security
Work steps
- Link platforms, locations and cloud services to the applications running on them
- Create service providers, contracts and subcontractors in the model and analyse concentration risks
- Maintain technical standards in the Standards Library with assigned controls
- Represent network segmentation and the zone concept in the model
- Import cloud and CMDB data automatically to keep the model up to date
Guiding question for management and CISO
If a data centre or service provider fails, can we say immediately which critical functions are affected?
Deliverables & evidence
- Technology model with locations and service providers
- Service provider register generated from the model
- Concentration risk analysis
- Catalogue of technical standards with controls
Phase E · ISO-HS 6.1 · ISO/IEC 27001 6.1.3 · Statement of Applicability
Opportunities and Solutions: work packages, building blocks and risk treatment
Phase E consolidates the gaps from Phases B to D into work packages and selects solution building blocks. In the integrated management system, this is also the risk treatment: which controls are implemented as building blocks, which risks are accepted, which requirements can a single building block meet at once? The Statement of Applicability thus results from architecture decisions rather than from a spreadsheet exercise.
BasisTOGAF Standard, 10th Edition: ADM, Phase E; Building Blocks; Transition Architectures; G152 (Risk Mitigation Plan). ISO/IEC 27001:2022, clause 6.1.3 (risk treatment, Statement of Applicability).
Typical pitfalls
- Risk treatment plan and project portfolio run separately — measures without a budget, budget without a link to risk (critical)
- Controls are implemented separately for each standard instead of once as a building block for several requirements (medium)
- Statement of Applicability with no link to building blocks and owners (medium)
- Transition Architectures without a risk assessment — intermediate states in particular are often the most vulnerable (medium)
Anchors in TOGAF, standards and regulation
TOGAF Phase EArchitecture Building BlocksSolution Building BlocksG152 · Risk Mitigation PlanISO/IEC 27001 6.1.3Statement of Applicability
Work steps
- Consolidate gaps from Phases B to D and bundle them into work packages
- Describe controls as reusable building blocks and map them to several requirements
- Define the treatment for each risk — mitigate, accept, transfer, avoid — and assign it to the work package
- Derive the Statement of Applicability from the building block decisions
- Check Transition Architectures for interim risks
Guiding question for management and CISO
Is every risk treatment a planned work package with a budget — and is every major work package linked to its risks?
Deliverables & evidence
- Consolidated gap list and work packages
- Control building blocks with multiple mappings
- Risk treatment plan linked to work packages
- Statement of Applicability with references to building blocks
Phase F · ISO-HS 6.2, 6.3 · Deadlines under NIS2, DORA, the EU AI Act and the CRA
Migration Planning: roadmap, priorities and regulatory deadlines
In Phase F, work packages are prioritised by value, risk, dependencies and cost and consolidated into an Implementation and Migration Plan. For GRC, this means that regulatory deadlines, risk level and audit dates become prioritisation criteria for the roadmap — and the roadmap becomes the risk treatment plan that management approves.
BasisTOGAF Standard, 10th Edition: ADM, Phase F; Architecture Roadmap; Implementation and Migration Plan. ISO/IEC 27001:2022, clauses 6.2 and 6.3.
Typical pitfalls
- Regulatory and certification deadlines are missing as a prioritisation criterion (critical)
- Roadmap and risk treatment plan drift apart (medium)
- Dependencies between work packages are underestimated — controls depend on platforms that only arrive later (medium)
- Nobody explicitly accepts the residual risks of the intermediate states (medium)
Anchors in TOGAF, standards and regulation
TOGAF Phase FImplementation and Migration PlanArchitecture RoadmapISO-HS 6.2ISO-HS 6.3Regulatory deadlines
Work steps
- Extend prioritisation with criteria for risk level, regulatory deadlines and audit dates
- Have management approve the roadmap as the risk treatment plan
- Identify residual risks per Transition Architecture and have them accepted
- Attach metrics for the management review to milestones
- Plan resources and competences for implementing and operating the controls
Guiding question for management and CISO
Does our roadmap show by when each obligation will be met and each risk reduced — and has management accepted the residual risk in between?
Deliverables & evidence
- Approved Architecture Roadmap linked to risks and deadlines
- Implementation and Migration Plan
- Residual risk acceptances per transition state
- Milestone metrics
Phase G · ISO-HS 8.1, 9.2 · ISO/IEC 27001 Annex A 5.8, 8.25–8.29
Implementation Governance: Architecture Contracts, compliance reviews and evidence
Phase G ensures that initiatives actually implement the target architecture: Architecture Contracts set down the requirements, and architecture compliance reviews check the implementation. In the integrated management system, these contracts contain the security and compliance requirements, and every review produces evidence that is attached directly to the control and the architecture element — the basis for internal audit and certification.
BasisTOGAF Standard, 10th Edition: ADM, Phase G; Architecture Contracts; Architecture Compliance. ISO/IEC 27001:2022, clauses 8.1 and 9.2; Annex A 5.8 and 8.25–8.29.
Typical pitfalls
- Architecture Contracts without security and compliance requirements — acceptance only tests functionality (critical)
- Evidence ends up in project folders and cannot be found once the project ends (critical)
- Architecture compliance reviews and internal audit check the same things twice — with different results (medium)
- Deviations are tacitly tolerated instead of being approved through the exception process (medium)
Anchors in TOGAF, standards and regulation
TOGAF Phase GArchitecture ContractArchitecture Compliance ReviewISO-HS 8.1ISO-HS 9.2ISO/IEC 27001 Annex A 5.8
Work steps
- Add security, data protection and compliance requirements to Architecture Contracts
- Conduct architecture compliance reviews with levels of conformance and store the results as evidence attached to the control
- Align the review and audit plans and consolidate findings into a joint list
- Approve deviations only through the joint exception process, with an expiry date
- Link acceptance criteria for building blocks to security tests such as code analysis or penetration testing
Guiding question for management and CISO
Does every initiative produce, as a by-product, the evidence we need for the next audit?
Deliverables & evidence
- Architecture Contracts with security and compliance requirements
- Architecture compliance review reports with level of conformance
- Joint findings list
- Approved exceptions with expiry date
Phase H · ISO-HS 9.1, 9.3, 10 · ISO/IEC 27001 Annex A 8.32
Architecture Change Management: monitoring, changes and improvement
Phase H monitors whether the architecture still fulfils its purpose and decides on changes — from minor adjustments to a new ADM cycle. This is the evaluation and improvement part of the management system: metrics, incidents, audit findings, new technologies and new obligations feed in as change requests and are decided in the joint management review.
BasisTOGAF Standard, 10th Edition: ADM, Phase H; Change Requests; Requirements Impact Assessment. ISO/IEC 27001:2022, clauses 9.1, 9.3 and 10; Annex A 8.32.
Typical pitfalls
- Lessons from incidents and tests fizzle out because they are not passed to the architecture as change requests (critical)
- Two change processes — IT change and architecture change — without a joint risk assessment (medium)
- Metrics measure project progress, but not the risk situation and control effectiveness (medium)
- Management review and architecture report run separately — management decides on the basis of two different data sets (medium)
Anchors in TOGAF, standards and regulation
TOGAF Phase HChange RequestRequirements Impact AssessmentISO-HS 9.1ISO-HS 9.3ISO-HS 10
Work steps
- Define metrics per capability for the risk situation, control effectiveness and progress towards the target architecture
- Record incidents, test results and audit findings as change requests to the architecture
- Classify changes by scope of impact — simplified procedure, partial revision or new ADM cycle
- Merge the management review and architecture report into a single management report
- Track corrective actions and improvements in the model
Guiding question for management and CISO
Do we notice when the target architecture no longer holds up — and does management decide on changes based on a shared data set?
Deliverables & evidence
- Metrics report per capability
- Change requests with assessment
- Joint management report with decisions
- Tracked corrective actions
Centre of the ADM · ISO-HS 4.2, 6.3 · ISO/IEC 27001 Annex A 5.31
Requirements Management: the obligations register at the centre
Requirements Management sits at the centre of the ADM cycle: requirements are captured, assessed and passed on in every phase. In the integrated management system, this becomes the obligations register — legal, regulatory, contractual and internal requirements with source, applicability, affected elements and evidence of fulfilment. Every new obligation triggers an impact analysis on the model.
BasisTOGAF Standard, 10th Edition: ADM, Requirements Management; Architecture Requirements Specification; Requirements Impact Assessment. ISO/IEC 27001:2022, clauses 4.2 and 6.3; Annex A 5.31.
Typical pitfalls
- Legal register, architecture requirements and customer requirements are kept in three places (critical)
- New obligations are identified but not translated into affected elements and work packages (critical)
- Requirements without a source or effective date — nobody knows whether they still apply (medium)
- Impact analyses take weeks because dependencies are determined manually (medium)
Anchors in TOGAF, standards and regulation
TOGAF Requirements ManagementArchitecture Requirements SpecificationRequirements Impact AssessmentISO-HS 4.2ISO-HS 6.3ISO/IEC 27001 Annex A 5.31
Work steps
- Set up one obligations register for legal, regulatory, contractual and internal requirements
- Link each requirement to its source, effective date, owner and affected elements
- Define the intake process: assessment, impact analysis, decision, scheduling
- Keep requirements machine-readable — for example as an OSCAL catalogue — so that mappings can be reused
- Continuously monitor regulatory changes and feed them into the register
Guiding question for management and CISO
How long does it take us to get from a new obligation to a scheduled measure — and do we know immediately which systems it affects?
Deliverables & evidence
- Obligations register with sources and mappings
- Impact analyses for new requirements
- Scheduling decisions
- Traceability requirement → control → evidence
Cross-cutting · EU AI Act (human oversight as a guiding principle) · ISO/IEC 42001 · OWASP Top 10 for Agentic Applications
Agentic operation: agents work on the model, humans decide
The agentic operating layer wraps around the cycle: AI agents read the shared model through defined tools, analyse the impact of new requirements and changes, map controls, collect evidence and draft reports. Write actions first appear as proposals, an accountable person approves them, low-risk routines run autonomously with logging — and the agents themselves are subject to the AI governance of the management system.
BasisEU AI Act (human oversight, logging — obligations for high-risk AI, used here as a guiding principle); ISO/IEC 42001:2023; ISO/IEC 27001:2022, Annex A 5.15 and 8.15; Model Context Protocol; OWASP Top 10 for Agentic Applications; VamiSec's interpretation.
Typical pitfalls
- Agents are granted broad system privileges through shared accounts instead of narrowly scoped tools (critical)
- Proposals are adopted without review — efficiency turns into a false sense of security (critical)
- Prompt injection via ingested documents or supplier responses alters agent behaviour (critical)
- Agent results without source references are worthless to auditors (medium)
- Licence infringement: texts of the TOGAF Standard are loaded into AI tools without permission from The Open Group (medium)
Anchors in TOGAF, standards and regulation
EU AI Act · Human oversightISO/IEC 42001ISO/IEC 27001 Annex A 5.15, 8.15Model Context Protocol (MCP)OWASP Top 10 for Agentic ApplicationsOSCAL
Work steps
- Define a task catalogue with autonomy levels: read and propose, execute after approval, low-risk routines autonomously with logging
- Connect agents through defined interfaces, with their own identities and minimal privileges
- Make the preview-and-approval principle mandatory for every write action
- Log inputs, sources, proposals, approvals and changes
- Add agents to the AI inventory and assess their risks
- Let agents work on your model, not on the text of the TOGAF Standard — its licence prohibits processing with generative AI without permission
- Measure effectiveness: processing time, error rate, share of rejected proposals
Guiding question for management and CISO
For every change in the model, do we know whether a human or an agent proposed it — and who approved it?
Deliverables & evidence
- Task catalogue with autonomy levels
- Authorisation concept for agents
- Logs with approval records
- Agents' entries in the AI inventory with risk assessment
Preliminary: setting up the architecture capability and the management system together
Mapping
Integration navigator: standards and regulation × TOGAF
Each row links a reference from the Harmonized Structure of the ISO management system standards, from ISO/IEC 27001 Annex A, from ISO/IEC 42001 or from NIS2, DORA, the EU AI Act, the CRA and the GDPR to the integration measure, the architecture contribution and the ADM phase in which that contribution is made. Filter by framework or topic and copy the selection as a checklist.
54Rows in the navigator: requirements from seven frameworks, each linked to the ADM
18Rows on the Harmonized Structure — the common core of the ISO management system standards
7Frameworks from ISO/IEC 27001 to the GDPR in one mapping
10ADM elements as the target column: nine phases plus Requirements Management — complemented by the agentic operating layer as a VamiSec extension
Framework
Topic
54 of 54 entries
ReferenceIntegration measureArchitecture contributionADM phase
ISO-HS 4.1 — Understanding the organization and its contextISO-HS clauses 4–10One context analysis for architecture and the management systemBusiness drivers, goals and constraints from the Preliminary Phase and Phase A are the standard’s internal and external issues — one analysis, two uses.Preliminary · AContext & scope
ISO-HS 4.2 — Understanding the needs and expectations of interested partiesISO-HS clauses 4–10Stakeholder map with requirementsThe TOGAF Standard’s stakeholder analysis is extended to include supervisory authorities, auditors, customers and service providers; their requirements go directly into the obligations register.A · Requirements Mgmt.Context & scope
ISO-HS 4.3 — Determining the scope of the management systemISO-HS clauses 4–10Derive the scope from the modelOrganisational units, processes, applications, locations and interfaces are captured in the architecture model; the scope is justified on this basis rather than described free-form.Preliminary · AContext & scope
ISO-HS 4.4 — Management systemISO-HS clauses 4–10Tailored approach as part of the IMS process mapThe ADM, tailored to the organisation, describes how architecture and management system processes interlock — the ADM phases become part of the process map of the integrated management system.PreliminaryGovernance & roles
ISO-HS 5.1 — Leadership and commitmentISO-HS clauses 4–10Mandate for the joint boardThe Architecture Board receives its mandate from management and takes on tasks of the GRC steering committee; responsibility remains with management.PreliminaryGovernance & roles
ISO-HS 5.2 — PolicyISO-HS clauses 4–10Set of principles that makes the policy concreteArchitecture principles with rationale and implications put the policy into concrete terms; security, data protection and compliance principles are part of the same set.PreliminaryGovernance & roles
ISO-HS 5.3 — Roles, responsibilities and authoritiesISO-HS clauses 4–10Owners on the model elementOwners of capabilities, applications, data objects, risks and controls are maintained on the element — the roles matrix is a view of the repository.Preliminary · B–DGovernance & roles
ISO-HS 6.1 — Actions to address risks and opportunitiesISO-HS clauses 4–10Risk assessment on architecture elementsRisks are attached to capabilities, applications, data flows and service providers; the TOGAF Standard’s risk management technique, which mainly considers risks to initiatives, and the management system’s methodology merge into a single methodology.A · B–D · ERisk & controls
ISO-HS 6.2 — Objectives and planning to achieve themISO-HS clauses 4–10Architecture Vision goals as management system objectivesMeasurable goals from Phase A and milestones from Phase F feed the planning of objectives — with owners, resources and deadlines.A · FRisk & controlsChange & projects
ISO-HS 6.3 — Planning of changesISO-HS clauses 4–10Planned changes via the roadmap and change requestsChanges to the management system and the architecture are planned via Transition Architectures and change requests, and their impact is assessed.F · HChange & projects
ISO-HS 7.1–7.3 — Resources, competence, awarenessISO-HS clauses 4–10Plan architecture capability and GRC competence togetherThe TOGAF part Enterprise Architecture Capability and Governance and the Series Guide Architecture Roles and Skills describe roles and competences; adding risk, compliance and AI competences produces a competence model for the integrated management system.PreliminaryGovernance & roles
ISO-HS 7.4 — CommunicationISO-HS clauses 4–10Communication plan from stakeholder managementWho is informed about what, and when, follows from the stakeholder map and concerns; supervisory and reporting channels are added.AGovernance & roles
ISO-HS 7.5 — Documented informationISO-HS clauses 4–10Architecture Repository and Governance Repository as controlled documentationVersioned architecture content, decisions and compliance assessments in the repository meet the requirements for controlling documented information — provided approval, versioning and retention are governed.all phasesEvidence & monitoringModel & inventories
ISO-HS 8.1 — Operational planning and controlISO-HS clauses 4–10Architecture Contracts with security and compliance requirementsPhase G governs implementation through contracts and reviews; this makes it possible to demonstrate that planned measures are actually implemented.GChange & projects
ISO-HS 9.1 — Monitoring, measurement, analysis and evaluationISO-HS clauses 4–10Metrics per capability and controlArchitecture metrics and control effectiveness are measured on the same elements — risk posture and progress towards the target architecture in one evaluation.HEvidence & monitoring
ISO-HS 9.2 — Internal auditISO-HS clauses 4–10Align compliance reviews and internal auditArchitecture compliance reviews deliver review results per initiative; the audit plan builds on them and avoids duplicate audits.GEvidence & monitoring
ISO-HS 9.3 — Management reviewISO-HS clauses 4–10One management report for architecture, risk and complianceThe architecture report and the management review are combined: target architecture, risk posture per capability, compliance status, open exceptions and decisions.HGovernance & rolesEvidence & monitoring
ISO-HS 10.1–10.2 — Continual improvement, nonconformity and corrective actionISO-HS clauses 4–10Findings as change requestsNonconformities from audits, reviews and incidents are raised as change requests to the architecture and tracked until their effectiveness has been demonstrated.HChange & projectsEvidence & monitoring
ISO/IEC 27001 Annex A 5.8 — Information security in project managementISO/IEC 27001 Annex ASecurity requirements in the Architecture ContractThe joint gate with an Architecture Contract embeds security requirements in every initiative and checks them at acceptance.GChange & projects
ISO/IEC 27001 Annex A 5.9 — Inventory of information and other associated assetsISO/IEC 27001 Annex AAsset inventory as a view of the modelApplications, data objects, technology and service providers from Phases C and D form the inventory — with owners and relationships instead of a flat list.C · DModel & inventories
ISO/IEC 27001 Annex A 5.12 — Classification of informationISO/IEC 27001 Annex AClassification on data objectsThe data architecture holds the classification of each data object; protection requirements carry over to applications and data flows.CModel & inventories
ISO/IEC 27001 Annex A 5.19–5.22 — Information security in supplier relationshipsISO/IEC 27001 Annex AService providers in the technology modelService providers, contracts and services are linked to the applications and capabilities that depend on them; supplier evidence is held on the element.DService providers & supply chain
ISO/IEC 27001 Annex A 5.23 — Information security for use of cloud servicesISO/IEC 27001 Annex ACloud services as modelled platformsCloud services are modelled with the division of responsibilities, region and exit option; configuration data flows into the model automatically.DService providers & supply chainModel & inventories
ISO/IEC 27001 Annex A 5.30 — ICT readiness for business continuityISO/IEC 27001 Annex AOutage scenarios from dependenciesDependencies of capabilities on applications, technology and locations provide the basis for recovery objectives and exercise scenarios.B · DRisk & controls
ISO/IEC 27001 Annex A 5.31 — Legal, statutory, regulatory and contractual requirementsISO/IEC 27001 Annex AObligations register in Requirements ManagementObligations are maintained at the centre of the ADM with their source, applicability and affected elements and tracked through to evidence; for this purpose, the TOGAF Series Guide on risk and security provides for a register of applicable laws and regulations in Phase B.Requirements Mgmt.Context & scope
ISO/IEC 27001 Annex A 5.35 — Independent review of information securityISO/IEC 27001 Annex AIndependent architecture compliance reviewsReviews by a party independent of the initiative provide part of the required independent review — coordinated with internal audit.GEvidence & monitoring
ISO/IEC 27001 Annex A 8.27 — Secure system architecture and engineering principlesISO/IEC 27001 Annex ASecurity principles and reference building blocksSecurity principles are part of the set of principles, and reference architectures and building blocks implement them; compliance reviews check their application.Preliminary · ERisk & controlsChange & projects
ISO/IEC 27001 Annex A 8.25–8.29 — Secure development and security testingISO/IEC 27001 Annex ASecurity requirements as acceptance criteria for building blocksSolution building blocks carry security requirements and test criteria; Phase G checks code analysis, testing and acceptance.E · GChange & projects
ISO/IEC 27001 Annex A 8.32 — Change managementISO/IEC 27001 Annex ALink IT change and architecture changeChanges with architectural impact are assessed as change requests — with a view to risks, controls and evidence.HChange & projects
NIS2 Art. 20 · § 38 BSIG — Governance, duties of executive managementNIS2 / BSIGExecutive management implements, oversees and undergoes trainingNIS2 requires management to approve the risk management measures and oversee their implementation; the German BSI Act refers to executive management’s duty to implement, oversee and undergo training. The management report and the joint board’s decision logs make this demonstrable.Preliminary · HGovernance & roles
NIS2 Art. 21 · § 30 BSIG — Cybersecurity risk-management measuresNIS2 / BSIGAreas of measures as control building blocksThe ten areas of measures are mapped to control building blocks and assigned to the affected elements; reviews and metrics demonstrate their effectiveness.E · GRisk & controls
NIS2 Art. 21(2)(d) — Supply chain securityNIS2 / BSIGService provider dependencies down to the service deliveredDependencies on service providers are visible in the technology model down to the services delivered; assessments and contract clauses are held on the element.DService providers & supply chain
NIS2 Art. 21(2)(i) — Human resources security, access control, asset managementNIS2 / BSIGAsset management from the modelThe architecture model provides the inventory and the mapping of roles to applications as the basis for access control concepts.C · DModel & inventories
NIS2 Implementing Regulation (EU) 2024/2690, Annex 5.2 and 12.4 — Supplier register, asset inventoryNIS2 / BSIGRegisters with change history from the versioned modelFor entities in digital infrastructure and providers of digital services, the Implementing Regulation requires an up-to-date register of direct suppliers and a complete asset inventory with a traceable change history — both are produced as views of the versioned model.C · DModel & inventoriesService providers & supply chain
NIS2 Art. 23 · § 32 BSIG — Reporting obligationsNIS2 / BSIGImpact analysis for reports within hoursEarly warning within 24 hours, incident notification within 72 hours, final report no later than one month after the notification: dependencies in the model quickly show which services and service recipients are affected.D · HEvidence & monitoring
DORA Art. 5 — Governance and organisationDORAThe management body is responsible for the ICT risk management frameworkThe joint board prepares decisions; roles, policies and budget are traceable in the model and in the management report.Preliminary · HGovernance & roles
DORA Art. 6 — ICT risk management frameworkDORAThe framework as part of the integrated management systemThe framework’s strategies, policies, procedures and tools are part of the IMS; the digital operational resilience strategy is managed as an Architecture Vision with a roadmap.A · FRisk & controlsGovernance & roles
DORA Art. 8 — IdentificationDORABusiness functions, assets and dependencies in the modelDORA requires ICT-supported business functions, information assets and ICT assets, and their dependencies, to be identified, classified and documented — exactly what the capability map and the application and technology models deliver.B · C · DModel & inventories
DORA Art. 11–12 — Response and recovery, backupDORARecovery from the dependency modelRecovery objectives and contingency plans are derived from criticality and dependencies; Transition Architectures describe fallback operation.B · D · ERisk & controls
DORA Art. 17–19 — Management, classification and reporting of ICT-related incidentsDORAClassification based on affected functionsAffected services, clients and critical functions are what matter for the classification and reporting of major incidents; the model provides this view without manual research.D · HEvidence & monitoring
DORA Art. 28(3) — Register of informationDORAThe register as a view of service providers, contracts and functionsContractual arrangements, services and supported functions are linked in the model; the register is generated rather than compiled.DService providers & supply chain
DORA Art. 28(8) — Exit strategiesDORAExit paths as Transition ArchitecturesFor services supporting critical or important functions, Transition Architectures describe the exit; Phase F plans it with deadlines.E · FService providers & supply chainChange & projects
EU AI Act Art. 4 — AI literacyAI Act & ISO/IEC 42001Extend the competence model to include AIProviders and deployers take measures to support the development of their staff’s AI literacy; the IMS competence model includes AI roles — including for employees who approve agent proposals.PreliminaryAI & agentsGovernance & roles
EU AI Act Art. 6 and Annex III — Classification as a high-risk AI systemAI Act & ISO/IEC 42001Risk classification in the AI inventoryAI systems are modelled as application components with their purpose and context of use; the classification is justified and recorded on the element. The high-risk obligations for Annex III apply from 2 December 2027.CAI & agentsModel & inventories
EU AI Act Art. 14 and 26 — Human oversightAI Act & ISO/IEC 42001Approval points in agent operationsHuman oversight as an architecture principle: a preview before every change, approval by those responsible, and the option to stop at any time. Recommended for internal GRC agents, even if they are not high-risk systems.agentic layerAI & agents
EU AI Act Art. 50 — Transparency obligationsAI Act & ISO/IEC 42001Label AI interactions and AI-generated contentThe transparency obligations have applied since 2 August 2026. Anyone who lets people interact with AI or uses AI to generate content checks the labelling — including for agent-generated reports and communications.G · agentic layerAI & agents
ISO/IEC 42001 — AI management system and AI system impact assessmentAI Act & ISO/IEC 42001AIMS as part of the integrated management systemISO/IEC 42001 follows the Harmonized Structure and fits into the IMS; the impact assessment for AI systems uses architecture views of data, purpose and affected persons.B · CAI & agentsRisk & controls
ISO/IEC 42001 Annex A.6.2.6, A.6.2.8 and A.9 — Operation, event logs, responsible useAI Act & ISO/IEC 42001Monitor and log agent operationsOperation and monitoring, event logs and rules for responsible use also apply to in-house GRC agents: defined purposes, logs including approvals, monitored error rates.agentic layer · HAI & agentsEvidence & monitoring
CRA Art. 13 and Annex I Part I — Essential cybersecurity requirementsCRARequirements as building blocks of the product architectureSecurity by Design and by Default are managed as requirements for product building blocks and checked in release approvals.E · GChange & projects
CRA Annex I Part II — Vulnerability handling, SBOMCRASBOM and vulnerability process on the product modelA product’s components and dependencies are maintained as an SBOM for each release; vulnerability handling and updates are processes on the model.D · HChange & projectsEvidence & monitoring
CRA Art. 14 — Reporting obligations of manufacturersCRAReporting channels since 11 September 2026Actively exploited vulnerabilities and severe incidents must be reported: early warning within 24 hours, notification within 72 hours, final report no later than 14 days after a corrective measure is available, or within one month for incidents.HEvidence & monitoring
GDPR Art. 25 — Data protection by design and by defaultGDPRData protection principles in the set of principles and in building blocksData minimisation, purpose limitation and privacy-friendly default settings are managed as architecture principles and building block requirements and checked in reviews.Preliminary · E · GRisk & controlsChange & projects
GDPR Art. 30 — Records of processing activitiesGDPRRecords as a view of processes, data and applicationsEach processing activity refers to the process, data objects, applications, recipients and deletion rules in the model; changes to applications trigger a review.B · CModel & inventories
GDPR Art. 35 — Data protection impact assessmentGDPRImpact assessment using architecture viewsData flows, recipients and storage locations from the model provide the systematic description of the processing — the assessment becomes faster and more complete.CRisk & controls
Mapping and phase assignment: VamiSec, as of 11/2026, not legal advice. Clause numbers of the Harmonized Structure follow ISO/IEC 27001:2022; ISO 9001, ISO 22301, ISO/IEC 42001 and ISO/IEC 27701 use the same clause structure. The TOGAF Standard contains no mapping to standards or laws — the “ADM phase” column shows where, in our interpretation, the contribution is made. EU AI Act deadlines as amended by Regulation (EU) 2026/1744; the CRA reporting obligations have applied since 11 September 2026.
Guide
The approach in detail: from integration principle to agentic operation
Eleven chapters: starting point, TOGAF in brief, management system, the four pillars (model, cycle, governance and evidence), regulation, agentic operation, tools and roadmap — with tables, step sequences and metrics.
Two worlds, one enterprise: why architecture and GRC belong together
Enterprise Architecture and GRC talk about the same things — capabilities, processes, applications, data, technology, service providers — but ask different questions. Architecture asks how the enterprise is structured and how it should change. GRC asks what must apply in the process, which risks are tolerable and how to prove it.
In many organisations, the two disciplines have grown up separately over the years. Architecture works with an EA tool, capability maps and an Architecture Board. The CISO office and the compliance function work with a GRC tool or spreadsheets, a risk register and a steering committee for the management system. Both sides do good work — but they do it twice, and they contradict each other in the process.
Typical symptoms of separate worlds
- The ISMS asset inventory and the architecture’s application portfolio count different numbers of systems — and nobody knows which figure is right.
- Criticality is assessed anew each time: in risk management, in the business impact analysis and in the DORA or NIS2 project.
- The Architecture Board and the GRC steering committee decide on the same initiatives, but one after the other and with different criteria.
- An approved deviation from the target architecture never shows up in the risk register as a risk acceptance.
- Before every audit, evidence is hunted down in project folders, tickets and mailboxes.
- Obligations such as the DORA register of information or the records of processing activities, and initiatives such as an AI inventory, are set up as special projects with their own spreadsheets.
| Question | Enterprise Architecture | GRC | Integrated |
|---|---|---|---|
| What do we have? | Capability map, application and technology portfolio | Asset inventory, service provider list, AI inventory | One model, inventories as views |
| What must apply? | Architecture principles, standards | Laws, standards, contracts, policies | One obligations register, one set of principles |
| What may change? | Target architecture, roadmap, Transition Architectures | Risk treatment plan, measures | Roadmap as the risk treatment plan |
| Who decides? | Architecture Board | GRC steering committee, management | One board with a mandate from management |
| How do we prove it? | Architecture compliance reviews, Governance Repository | Audits, evidence repository | One evidence chain attached to controls and elements |
Then there is speed. Regulation such as NIS2, DORA, the EU AI Act and the Cyber Resilience Act demands answers that only an up-to-date architecture model can provide: Which functions depend on which service provider? Which systems process which data? Which services are affected by an incident — and all of that within hours, not weeks.
The TOGAF® Standard, 10th Edition — read through a GRC lens
The Open Group published the 10th Edition of the TOGAF Standard on 25 April 2022 and updated it with Technical Corrigendum 1 in May 2025; the revised volumes appeared in June 2025 as the “2025 Update”. The hallmark of the 10th Edition is its modular structure: a stable Fundamental Content and TOGAF Series Guides that evolve independently.
| Fundamental Content document | Content | Relevance for GRC |
|---|---|---|
| Introduction and Core Concepts | Terms, architecture services, levels of abstraction, agility, risk management as a core concept | Common vocabulary for architecture and GRC |
| Architecture Development Method | Preliminary Phase, Phases A to H, Requirements Management | Carries the management system cycle |
| ADM Techniques | Architecture Principles, Stakeholder Management, Architecture Patterns, Gap Analysis, Interoperability Requirements, Business Transformation Readiness Assessment, Risk Management, Architecture Alternatives and Trade-Offs | Principles, stakeholders and risk as shared tools |
| Applying the ADM | Iteration, architecture styles, architecture landscape, partitioning | Strategic, segment and capability iterations for the annual cycle and for initiatives |
| Architecture Content | Content Framework and Enterprise Metamodel, artefacts, deliverables, building blocks, Enterprise Continuum, Architecture Repository | The shared model and its repository |
| Enterprise Architecture Capability and Governance | Establishing the architecture function, governance framework, Architecture Board, Architecture Contracts, Architecture Compliance | Board, contracts and reviews as part of the management system |
Structure based on the 10th Edition as published in the “2025 Update”. Among other topics, the Series Guides cover Business Capabilities, Value Streams, agile approaches, Architecture Roles and Skills and the integration of risk and security.
The Architecture Development Method
The ADM describes a cycle: the Preliminary Phase prepares the organisation, principles and approach; Phase A sets the frame for an iteration with the Architecture Vision and the Statement of Architecture Work; Phases B to D develop the business, data, application and technology architectures in the Architecture Definition Document; E and F consolidate gaps into work packages, Transition Architectures, the Architecture Roadmap and the Implementation and Migration Plan; G governs implementation through Architecture Contracts and architecture compliance reviews; H monitors and decides on changes. Requirements Management sits at the centre and runs through all phases. The standard explicitly regards the ADM as iterative and adaptable.
Security and risk: cross-cutting, with a guide of its own
There is no separate security phase — security is a cross-cutting topic in all architecture domains. The Risk Management chapter of the ADM Techniques describes classification, identification, assessment before and after mitigation, and monitoring in Phase G; it is aimed primarily at the risks of architecture initiatives. For enterprise and information risks, there is the Series Guide “Integrating Risk and Security within a TOGAF Enterprise Architecture” (G152), developed by The Open Group Security Forum together with The SABSA Institute. It links information security management based on ISO/IEC 27001 and enterprise risk management based on ISO 31000 to all ADM phases.
| Phase | Artefacts from G152 (selection) | Link to the management system |
|---|---|---|
| Preliminary | Security Principles, Risk Appetite, Key Risk Areas and Business Impact Analysis, Security Resource Plan | Policy, risk criteria, resources |
| B Business | Security Policy Architecture, Security Domain Model, Trust Framework, Risk Assessment, Business Risk Model/Risk Register, Applicable Law and Regulation Register, Applicable Control Framework Register | Risk assessment, obligations and control registers |
| C Information Systems | Security Services Catalog, Security Classification | Classification, controls as security services |
| E Solutions | Risk Mitigation Plan | Risk treatment plan |
| G Implementation | Security Audit, Security Training and Awareness | Audit, competence and awareness |
| Requirements Management | Business Attribute Profile, Control Objectives/Security Objectives, Security Standards | Objectives and requirements |
Artefact names as per G152 (first edition January 2016, listed among the Series Guides of the 10th Edition). G152 refers to ISO/IEC 27001:2013 and ISO 31000:2009; the current editions date from 2022 and 2018.
For integration, it is notable how close G152 comes to the management system: a register of applicable laws and regulations and a register of applicable control frameworks belong to the business architecture there, and controls are bundled into security services and managed as building blocks. The guide itself stresses that security is not a matter of picking items from a checklist.
What TOGAF is not
- Not a management system standard: the standard neither requires a management system nor replaces one.
- No certificate for organisations: The Open Group certifies individuals, with credentials such as TOGAF Enterprise Architecture Foundation and Practitioner.
- Not a catalogue of measures: which controls are needed follows from the risk assessment, standards and laws.
- Not a tool and not a rigid waterfall model: the ADM is tailored and iterated, including in agile sprints.
- Not free for every use: organisations use the standard under a free, non-commercial licence for their own architecture work; consulting, training and tools for third parties require a commercial licence. The licences also prohibit processing the texts with generative AI without written permission.
TOGAF® and ArchiMate® are registered trademarks of The Open Group. This page is an independent presentation by VamiSec GmbH and is not authorised by The Open Group.
The backbone: Harmonized Structure and integrated management system
An integrated management system needs a common structure. The ISO management system standards provide it with the Harmonized Structure: the same clauses, core terms and core requirements for information security, quality, business continuity, AI and data protection.
The Harmonized Structure — set out as Appendix 2 to Annex SL in the Consolidated ISO Supplement until October 2026 and part of the joint ISO/IEC Directives since then — forms the common framework of ISO/IEC 27001, ISO 9001:2026, ISO 22301, ISO/IEC 42001, ISO/IEC 27701:2025 and other standards. Clauses 4 to 10 follow the cycle of planning, implementing, checking and improving. Anyone operating several management systems maintains these clauses once and adds only the discipline-specific requirements.
| Clause | Content | Counterpart in the TOGAF Standard |
|---|---|---|
| 4 Context | Organisation and its context, interested parties, scope, management system | Preliminary Phase, Phase A, Stakeholder Management |
| 5 Leadership | Leadership and commitment, policy, roles and authorities | Architecture Board, architecture principles, EA Capability and Governance |
| 6 Planning | Risks and opportunities, objectives, planning of changes | Risk Management technique, Phases A to F, Transition Architectures |
| 7 Support | Resources, competence, awareness, communication, documented information | Architecture Roles and Skills, Architecture Repository |
| 8 Operation | Operational planning and control | Phase G with Architecture Contracts |
| 9 Performance evaluation | Monitoring and measurement, internal audit, management review | Architecture compliance reviews, Phase H, Architecture Board |
| 10 Improvement | Continual improvement, nonconformity, corrective actions | Phase H, change requests |
Mapping: VamiSec. The TOGAF Standard and the Harmonized Structure do not refer to each other.
What belongs in the management system besides the structure
- ISO 31000 as the guideline for risk management — not certifiable, but the common language for risk assessment and treatment.
- ISO 37301 for certifiable compliance management systems, where the management of obligations is to be governed beyond information security.
- COBIT by ISACA for the governance of enterprise IT — in version 7 since November 2026; COBIT 2019 already includes a dedicated objective, “Managed Enterprise Architecture”.
- The Three Lines Model of the Institute of Internal Auditors — introduced in 2020 and updated in July 2026 by a position paper, with the core structure unchanged — for the division of roles between the governing body, management and internal audit.
- The GRC Capability Model by OCEG, which describes GRC as capabilities for Principled Performance®: reliably achieving objectives, addressing uncertainty and acting with integrity.
Since March 2026, ISO has had a dedicated practical guide to the integrated management system that describes how several management systems become one — in three steps: prepare, connect, integrate. For the “connect” step, TOGAF supplies the piece that the standards deliberately leave open: a model in which the management systems meet.
TOGAF thus adds to the framework of the standards a method for describing, changing and governing the enterprise as a whole. The standards require a scope, a risk assessment and an inventory — they do not say how to build the model behind them. That is precisely where the value of integration lies.
The shared metamodel: one model instead of many inventories
The heart of integration is a shared metamodel: the definition of which object types the model knows and how they relate to one another. With its Enterprise Metamodel, the TOGAF Standard provides the architecture side; with its motivation elements, ArchiMate provides the bridge to goals, principles and requirements. GRC adds risk, control and evidence.
| Object type | Origin | Example | Benefit for GRC |
|---|---|---|---|
| Obligation | GRC | Maintain the DORA register of information | Source, applicability, owners |
| Requirement | TOGAF, ArchiMate | Service provider contracts with exit clauses | Translates obligations into architecture specifications |
| Principle | TOGAF | Data has a named owner | Puts the policy into concrete terms |
| Business capability | TOGAF | Process payments | Criticality, protection requirements, critical function |
| Process, value stream | TOGAF | Loan application to disbursement | Records of processing activities, business impact analysis |
| Data object | TOGAF | Customer master data | Classification, data protection |
| Application, AI system | TOGAF | Core banking system, AI assistant | Asset inventory, AI inventory |
| Technology, location | TOGAF | Cloud region, data centre | Outage scenarios, concentration risk |
| Service provider, contract | TOGAF, GRC | Cloud provider, framework agreement | Register of information, supply chain |
| Risk | GRC | Outage of the payment service provider | Assessment, treatment, acceptance |
| Control, building block | GRC, TOGAF | Recovery tested every quarter | Statement of Applicability, multiple mapping |
| Evidence | GRC | Record of the recovery test | Audit, supervision, certification |
| Exception | TOGAF, GRC | Time-limited deviation with risk acceptance | Dispensation and risk acceptance in one |
Core metamodel based on VamiSec practice. Terms from the TOGAF Enterprise Metamodel and from ArchiMate are adopted in substance; ten to fifteen object types are usually enough to start with.
The TOGAF Series Guide on integrating risk and security recommends exactly this approach: extending existing metamodel entities with attributes for information security and risk management instead of building a second model. ArchiMate 4, current since April 2026, drops the former Constraint element — constraints are modelled as requirements.
The compliance chain in ArchiMate
| Concept | ArchiMate element | Example |
|---|---|---|
| Regulation, supervisory authority | Driver, Stakeholder | DORA, financial supervisor |
| Risk, vulnerability, gap | Assessment | Concentration of critical functions on one cloud provider |
| Control objective | Goal or Outcome | Compensate for a service provider outage within hours |
| Control measure | Requirement | Exit plan for each critical service provider |
| Policy | Principle | No critical function without a fallback option |
| Implemented control | Core elements that realise the Requirement | Secondary provider, tested recovery |
Pattern based on The Open Group white paper W172 on modelling risk and security with ArchiMate. ArchiMate 4 no longer has a separate Constraint element — constraints are modelled as Requirements — and a gap is modelled as an Assessment.
Registers as views of the model
As soon as the objects are linked, the registers required by regulation become filtered views instead of separate lists. This does more than save maintenance effort: the views no longer contradict each other, because they are generated from the same objects.
| Register | Framework | View of |
|---|---|---|
| Asset inventory | ISO/IEC 27001 | Applications, data objects, technology, service providers with owners |
| Register of information | DORA | Service providers, contracts, services and supported functions |
| AI inventory | EU AI Act (classification), ISO/IEC 42001 | Applications with AI characteristics, purpose, classification, data sources |
| Records of processing activities | GDPR | Processes, data objects, applications, recipients |
| SBOM | Cyber Resilience Act | Components and dependencies of a product per release |
| Overview of service providers and dependencies | NIS2, German BSI Act | Service providers and their services, through to the services provided |
One cycle: how the ADM phases carry the management system cycle
The ADM and the cycle of the management system standards are both designed as cycles. If you interlock them, every ADM phase delivers outputs that a management system clause needs — and every iteration generates the evidence along the way.
| ADM phase | Harmonized Structure clause | Output in the integrated system | Evidence |
|---|---|---|---|
| Preliminary | 4, 5, 7.1–7.3 | Mandate, set of principles, board, tailored approach | Rules of procedure, principles |
| A Vision | 4.2, 6.1, 6.2 | Objectives, stakeholders, obligations, initial risks | Statement of Architecture Work |
| B Business | 6.1 | Capabilities with criticality, critical functions | Capability map with assessment |
| C Data and Applications | 6.1, 7.5 | Inventories as views, data flows, AI inventory | Registers generated from the model |
| D Technology | 6.1 | Platforms, locations, service providers, dependencies | Service provider register, concentration analysis |
| E Solutions | 6.1, 6.2 | Controls as building blocks, risk treatment | Statement of Applicability |
| F Migration | 6.2, 6.3 | Roadmap linked to risks and deadlines | Approved treatment plan |
| G Implementation | 8.1, 9.2 | Architecture Contracts, architecture compliance reviews | Review reports, list of findings |
| H Change | 9.1, 9.3, 10 | Metrics, management report, improvements | Management review, corrective actions |
| Requirements Management | 4.2, 6.3 | Obligations register with impact analysis | Traceability through to the evidence |
Mapping: VamiSec. Clause numbers as per ISO/IEC 27001:2022.
The TOGAF Standard emphasises that the ADM is adapted and iterated: an enterprise can run several iterations in parallel — strategic ones for the overall picture, others for individual segments or individual capabilities. For the integrated management system, this is an advantage: a strategic iteration carries the annual cycle of objective and risk planning, while segment and capability iterations accompany initiatives and regulatory projects.
One iteration in practice
- 1TriggerNew obligation or new initiative
Requirements Management records the trigger, maps it to the affected elements and starts an impact analysis.
- 2Phase AVision with obligations and risks
Objectives, stakeholders, scope and initial risk assessment; the board approves the Statement of Architecture Work.
- 3Phases B–DRisk assessment on the model
Assess the affected capabilities, applications, data, technology and service providers; record gaps as requirements.
- 4Phases E–FTreatment as a roadmap
Select controls as building blocks, plan work packages, have the residual risks of the transition states accepted.
- 5Phase GImplement with evidence
Architecture Contracts with security and compliance requirements, reviews with a level of conformance, evidence filed against the control.
- 6Phase HMonitor and decide
Metrics and findings feed into the joint management report; changes start the next iteration.
One board, one set of principles, one exception process
Architecture governance and management system governance answer the same questions: who decides on the target architecture and exceptions, according to which principles, and how is compliance checked? Brought together, coordination effort falls and decisions become consistent.
The joint board
- Mandate and rules of procedure from management — including authority for exceptions and risk acceptances up to a defined threshold.
- Members: architecture, information security, the risk and compliance function, data protection, business units and IT operations; internal audit attends in an advisory capacity and remains independent.
- Tasks: approve the target architecture and roadmap, adopt the Statement of Architecture Work, decide on exceptions, evaluate architecture compliance reviews, prepare the management review.
- Rhythm: regular meetings plus a fast-track procedure for incidents and deadlines.
One set of principles
The TOGAF Standard describes principles in terms of name, statement, rationale and implications, and its example set already includes a business principle on compliance with the law. For the integrated management system, a joint set that combines architecture, security, data protection and compliance principles is worthwhile.
| Principle | Statement | Rationale | Implication |
|---|---|---|---|
| Compliance by Design | Obligations are addressed during design, not at acceptance | Corrections after the fact cost many times as much | Every initiative maps its obligations in Phase A |
| One model, one truth | Inventories and registers are views of one model | Contradictions between lists create audit risks | No register without a link to the model |
| Data has owners | Every data object has a named owner and a classification | Protection and data protection require accountability | No go-live without an owner |
| People decide on risks | Risk acceptances and exceptions are made by an authorised person | Accountability cannot be delegated to tools | Agents prepare, people decide |
Example principles in the format of the TOGAF Standard: name, statement, rationale, implications.
One exception process
The TOGAF Standard provides for the dispensation: a time-limited authorisation by the Architecture Board to deviate from architecture specifications subject to conditions. The management system provides for risk acceptance by the risk owner. In practice, both describe the same thing. A joint exception request records the deviation, affected elements, risk assessment, compensating measures, authority and expiry date — and an expired request automatically creates a task.
Evidence in the process, risk in the architecture context
The fourth pillar connects what auditors want to see with what architecture work produces anyway: contracts, reviews, decisions and change requests. And it gives risk a fixed place — on the architecture element.
Evidence produced along the way
| Output of architecture work | Evidence for | Storage |
|---|---|---|
| Statement of Architecture Work with obligations and risk objectives | Objectives and planning (ISO-HS 6.2) | Governance Repository, attached to the initiative |
| Architecture Contract with security and compliance requirements | Operational control (8.1), security in projects (Annex A 5.8) | Attached to the initiative and the controls |
| Compliance Assessment from a review | Monitoring and internal audit (9.1, 9.2) | Attached to the control and the element |
| Dispensation with risk acceptance | Risk treatment (6.1.3) | Exception register |
| Change Request with impact analysis | Planning of changes (6.3), change management (Annex A 8.32) | Attached to the element |
| Minutes of the joint board | Management review (9.3), management accountability under NIS2 and DORA | Governance Repository |
Clause references as per ISO/IEC 27001:2022; mapping by VamiSec.
For architecture compliance reviews, the TOGAF Standard has its own conformance terminology, used since TOGAF 9: six levels — Irrelevant, Consistent, Compliant, Conformant, Fully Conformant and Non-conformant. “Non-conformant” applies as soon as an implemented feature deviates from the specification. In the integrated management system, the level determined is stored with the control and the element, feeds into metrics and, in the event of deviations, triggers the exception or corrective action process.
Risk on the architecture element
The Risk Management technique of the TOGAF Standard describes classification, identification, assessment before and after mitigation, and monitoring — with a focus on architecture initiatives. In the integrated management system, a single methodology based on ISO 31000 or ISO/IEC 27005 applies to all risks; TOGAF provides the structure to which risks are attached and against which they are reassessed. Those who want to compare risks per capability in monetary terms add Open FAIR from The Open Group, available since May 2025 in the versions Risk Taxonomy 3.1 and Risk Analysis 2.1.
- Phase A: identify transformation risks and mitigation measures, initial assessment of the affected capabilities.
- Phases B to D: assess risks to capabilities, applications, data flows, technology and service providers.
- Phase E: confirm transformation readiness and risk, define the treatment for each risk.
- Phase F: prioritise work packages by cost, benefit and risk, have the residual risks of the transition states accepted.
- Phases G and H: monitor risks, trigger a new iteration if the situation or the risk appetite changes.
Implementing regulation with the architecture model: NIS2, DORA, EU AI Act, CRA and GDPR
The major EU regulations demand knowledge that resides in the architecture model — and set deadlines that can only be met with an up-to-date model. The overview shows what is required and what the model contributes.
| Framework | What is required | What the model provides | Status |
|---|---|---|---|
| NIS2 and German BSI Act | Risk management measures from asset management to the supply chain, executive management’s duty to implement, oversee and attend training, notifications within 24 and 72 hours | Asset and service provider views, dependencies for impact analyses, management report | In Germany since 6 December 2025 |
| DORA | ICT risk management framework, identification of business functions, assets and dependencies, register of information, exit strategies, incident reports | Capability map with critical functions, application and technology model, register as a view, Transition Architectures | Applicable since 17 January 2025 |
| EU AI Act | AI literacy, transparency; for high-risk systems: risk management, data governance, logging and human oversight | AI inventory with classification, data flows, human oversight as an architecture principle | Transparency obligations since 2 August 2026, high-risk under Annex III from 2 December 2027 |
| Cyber Resilience Act | Security by design, vulnerability handling, SBOM, reporting of exploited vulnerabilities and severe incidents | Product architecture with building blocks, SBOM per release, reporting channels | Reporting obligations since 11 September 2026, fully applicable from 11 December 2027 |
| GDPR | Records of processing activities, data protection by design, data protection impact assessment | Processes, data objects, applications and recipients as a view; principles and building blocks | Applicable since 25 May 2018 |
EU AI Act deadlines as amended by Regulation (EU) 2026/1744. VamiSec assessment, not legal advice.
24 hEarly warning for significant incidents under NIS2 and for actively exploited vulnerabilities under the CRA
72 hNotification of significant incidents under NIS2 and vulnerability notification under the CRA
1 modelSource for the asset inventory, register of information, AI inventory, records of processing activities and SBOM
The benefit is clearest in an emergency. Anyone who, in the event of an incident, has to submit an early warning within 24 hours needs immediate answers to three questions: Which services are affected, which customers and functions depend on them, and which service providers are involved? A well-maintained model answers them with a query; without a model, the research only begins once the clock is already ticking.
Agentic operation: agents work on the model, people decide
An integrated management system with a structured model is the prerequisite for AI agents to contribute meaningfully. Without a model, agents remain text generators; with a model, they analyse impacts, create mappings, collect evidence and prepare decisions — under rules set by the management system itself.
| Agent task | ADM link | Recommended level | Approval by |
|---|---|---|---|
| Evaluate a new obligation and map it to the affected elements | Requirements Management | Proposal with approval | Obligation owners |
| Analyse the impact of a change on risks, controls and evidence | Phase H | Proposal with approval | Element owners, board |
| Map controls to multiple frameworks | Phase E, Requirements Management | Execution after approval | Control owners |
| Collect evidence from connected systems and map it | Phase G | Execution after approval, later autonomous with logging | Control owners by sampling |
| Report discrepancies between model and operations | Phase H | Autonomous with logging | Element owners |
| Monitor deadlines, certificates and expiry dates | Phase H | Autonomous with logging | — |
| Draft the management report and management review | Phase H | Proposal with approval | CISO, board |
| Risk acceptance, exception, target architecture decision | Phases A, F, G | None — preparation only | Authorised people |
VamiSec recommendation. Levels in essence: read and propose, execute after approval, autonomous with logging.
Guardrails for agents in the management system
- A separate identity and minimal permissions for each agent — no shared accounts, no administrator rights.
- Access only through defined tools, such as the GRC platform’s MCP server, rather than unrestricted system access.
- A preview before every write action, approval recorded with person and timestamp.
- A complete log of inputs, sources, proposals, approvals and actual changes.
- Sources required: every statement backed by evidence; unsupported answers are refused rather than guessed.
- Protection against prompt injection: supplier responses, documents and web pages are data, never instructions.
- Security of the AI systems themselves in line with ISO/IEC 27090, published in October 2026: the guidance describes AI-specific compromises — from data poisoning to output injection — together with their detection and defence.
- AI governance for your own agents: entry in the AI inventory, risk assessment, human oversight, measurement of error rates — ISO/IEC 42001 provides the framework.
- Respect the licence: do not use texts of the TOGAF Standard with generative AI without written permission from The Open Group; check the licence terms of ArchiMate and other standards — agents work on your model and your data.
International guidance points in the same direction. Singapore’s Model AI Governance Framework for Agentic AI of January 2026 recommends limiting agents’ autonomy and tool access up front and securing accountability through defined approval checkpoints; the MCP specification of July 2026 allows servers to ask the user for input in the middle of a call — technically exactly the right place for a confirmation.
How VamiGRC implements the pattern
VamiGRC sees itself as an agentic integrated management system: five management systems — information security, data protection, AI, product security and business continuity — share one data set. The platform’s AI assistant answers questions with sources and refuses unsupported answers, translates questions into queries on the GRC Graph and displays the query, carries out tasks — destructive actions only after explicit confirmation — and delegates to specialised agents. The autonomy levels range from L0 (manual) through L1 (AI advises) and L2 (AI executes, a human approves) to L3 (autonomous, information only, logged) and are set per task category; a four-eyes principle applies to critical changes, and L3 steps can be paused and reversed at any time. Every input, every tool call, every decision and every write operation is logged with timestamp, model version and rationale.
Via the Claude connector, Claude also works with this data: Claude sees only what the user is allowed to see, every change first appears as a preview, nothing is written without approval, and approvals remain in VamiGRC. For the connector, this technically implements the principle of this page — AI proposes, people decide.
The direction is also visible at The Open Group: a case study from November 2025 describes how the ADM, ArchiMate and an EA tool with AI-assisted search underpin an integrated quality management system. There is no TOGAF Series Guide on AI agents yet — the guardrails therefore come from the EU AI Act, ISO/IEC 42001 and the security guidance for agentic applications.
Tool landscape and exchange formats
Integration is first a question of model and governance, and only then of tools. Nevertheless, interfaces and formats determine whether inventories stay in sync and agents work securely.
| Component | Role in the integrated system | Standard or format |
|---|---|---|
| EA tool | Architecture model, views, roadmaps, Transition Architectures | ArchiMate; Open Group Exchange Format (v3.1, for ArchiMate 3.1/3.2) |
| GRC platform | Obligations, risks, controls, evidence, approvals, reports | OSCAL for catalogues, profiles and assessment results |
| CMDB and cloud interfaces | Reconciliation of model and operations | Vendor interfaces, synchronisation |
| Ticketing and project systems | Work packages, changes, findings, corrective actions | Two-way synchronisation |
| Agent interface | Access for AI assistants and agents with permissions, preview and log | Model Context Protocol (MCP) |
| Policy as code | Automated checking of technical specifications and configurations | For example Open Policy Agent |
A simple pattern has proven effective: the EA tool is the system of record for the architecture objects, the GRC platform for obligations, risks, controls and evidence; both use the same identifiers and synchronise via interfaces. Agents gain access through a defined interface that enforces permissions, preview and logging. Where no EA tool exists, the GRC platform initially also holds the core model.
Roadmap: the core in 100 days, the integrated system in twelve months
Integration is not a big bang. A staged approach has proven effective: first the mandate, the model core and one pressing register, then governance and the evidence chain, and finally agentic operation.
- 1Day 1–15Mandate and starting point
Mandate from management, Integration check, initial scope and a core team from architecture, the CISO office, compliance and a business unit.
- 2Day 15–45Core metamodel and systems of record
Define ten to fifteen object types, relationships, identifiers and the system of record for each object type.
- 3Day 30–75One inventory from one source
Merge the asset inventory and the application portfolio, name owners, generate the most pressing register — for DORA or NIS2, for example — as a view.
- 4Day 45–100Obligations register and board
Obligations register with an intake process, a joint board with rules of procedure and a joint exception process.
- 5Month 4–6Interlock the cycle
Initiative gate with an Architecture Contract, risks on the model, the roadmap as the risk treatment plan; align reviews and internal audit.
- 6Month 6–9Evidence chain and management report
Evidence attached to controls and elements, continuous monitoring of the first controls, a joint report to management.
- 7Month 9–12Agentic operation
First agent tasks with autonomy levels, approvals and logging; measure effectiveness, then expand step by step.
| Metric | What it shows | Direction |
|---|---|---|
| Duplicate rate between inventories | Whether the model is the single source | Falls towards zero |
| Share of risks linked to an element | Whether risks are anchored in the model | Rises |
| Lead time from new obligation → scheduled measure | Speed of Requirements Management | Falls |
| Share of initiatives with an architecture and compliance gate | Reach of governance | Rises |
| Open and expired exceptions | Discipline in the exception process | Falls |
| Time for an audit sample from requirement to evidence | End-to-end continuity of the evidence chain | Falls |
| Share of rejected agent proposals | Quality of agents and approvals | Monitored |
Self-assessment
Integration check: how close are your architecture and GRC to being one system?
Up to 32 questions across eight areas, each referenced to the TOGAF Standard, to the Harmonized Structure of the ISO management system standards or to regulation. Your profile determines the target level and the questions; the evaluation shows maturity by area, your biggest gaps, a roadmap for 30, 90 and 180 days and the evidence you should prepare.
0 / 32 questions answered
Your evaluation
Not all questions answered yet — the evaluation is provisional.
Your biggest gaps
Not all questions answered yet — the evaluation is provisional.
The button takes you to the form, where you can optionally include your result.
Your answers stay in your browser. Nothing is stored or transmitted unless you send it yourself via the form.
Free whitepaper · German & English
TOGAF & GRC for CISOs — combining architecture and GRC into one integrated management system and running it agentically
The guide for decision-makers: how the TOGAF Standard and the Harmonized Structure of the ISO management system standards fit together, which metamodel connects architecture and GRC objects, how the ADM phases carry the management system cycle, how the architecture model makes it easier to implement NIS2, DORA, the EU AI Act and CRA — and how AI agents support operations with approvals and a log.

27 pages (DE) / 27 pages (EN)PDF, free of chargeGerman & EnglishAs of 11/2026
- Ten key statements and an executive board briefing: why separate architecture and GRC silos cost money, speed and audit certainty
- The shared metamodel with object types and relationships — from obligation via control and building block to evidence
- The integrated cycle: every ADM phase with GRC tasks, outputs and references to the standards, plus governance and the exception process
- Agentic operation with autonomy levels, approvals and guardrails — plus a 100-day plan, metrics and the tool landscape
The CISO whitepaper: TOGAF & GRC for CISOs
Part I · Understand
Management summary and ten key statements, the TOGAF Standard from a CISO perspective — what it does and does not deliver — the Harmonized Structure as the backbone of the integrated management system, and the cost of separate architecture and GRC silos.
Part II · Integrate
The four pillars of model, cycle, governance and evidence: the shared metamodel with object types and relationships, ADM phases with GRC tasks, one board and one exception process, and risk in the architecture context with a common risk language.
Part III · Regulation
Implementing NIS2, DORA, the EU AI Act, CRA and GDPR on the basis of the architecture: which registers and evidence the model produces, how deadlines shape the roadmap and how incident impact analyses become faster.
Part IV · Run agentically
Agent roles from obligations analysis to draft reports, autonomy levels and approvals, guardrails based on the EU AI Act, ISO/IEC 42001 and OWASP — plus the tool landscape, a 100-day plan and metrics for management and auditors.
Agentic operation with VamiGRC
From the shared model to agentic operation: how the integrated management system works in VamiGRC
The integration described on this page needs a platform on which architecture and GRC objects are connected and agents can work in a controlled way. VamiGRC, the GRC platform of VamiSec GmbH, is designed as an agentic integrated management system: ISMS, privacy, AI, product security and business continuity management share one data set in the GRC Graph, in which business processes, information, assets, service providers, risks, controls and evidence are linked. A business process is maintained once and read as a processing activity, AI use case, asset, product and business impact analysis. Specialised AI agents handle routine work along autonomy levels L0 to L3, which you set for each task category: at L2 no task is closed without human approval; L3 runs autonomously with notification and logging and can be paused, reviewed and reversed at any time.
L0–L3autonomy levels per task category — from manual through AI-assisted and AI-executed with approval to autonomous with logging
GRC Graphprocesses, information, assets, service providers, risks, controls and evidence in one data set for five management systems
OSCALover 50 standards, your own frameworks as OSCAL catalogues, two to six frameworks combinable in the Framework Composer
- Requirements Management: frameworks as OSCAL catalogues that can be combined in the Framework Composer — the basis for a joint gap analysis, audits and the Statement of Applicability.
- Phases B to D: business processes, information, assets and service providers as linked inventories instead of parallel lists; the GRC Graph answers questions in natural language and shows the query.
- Phases G and H: evidence linked to risks and controls in the GRC Graph, tasks with approval and a log of every prompt, tool call, decision and write operation with timestamp, model version and rationale.
- Claude connector: Claude only sees what you are allowed to see; every change appears as a preview, nothing is written without your OK, and approvals stay in VamiGRC.
vamigrc.com — agentic GRC platform of VamiSec GmbH. Platform data on T Cloud Public in German data centres (BSI C5 attestation of T Cloud Public); the agent layer is provider-agnostic and configurable per tenant. Mapping the ADM phases to these functions is VamiSec's interpretation, not a product feature; vamigrc.com does not describe a TOGAF approach.
VamiGRC
Cómo implementarlo con VamiGRC
VamiGRC integra SGSI, privacidad, IA, seguridad de producto y continuidad de negocio en un sistema de gestión integrado con datos compartidos: un proceso de negocio se mantiene una sola vez y se lee como actividad de tratamiento, caso de uso de IA, activo, producto y análisis de impacto. Los agentes de IA se encargan de la rutina según los niveles de autonomía L0 a L3, con sus aprobaciones.
Glossary
Glossary: TOGAF, GRC and agentic operation
30 terms from the TOGAF Standard, the ISO management system standards, regulation and agentic operation, briefly defined in our own words; the technical term in the other language is given as an alternative.
30 of 30 terms
- ADMArchitecture Development Method
- The architecture development method of the TOGAF Standard: an iterative cycle comprising the Preliminary Phase, Phases A to H and Requirements Management at the centre. In the integrated management system, the ADM also carries the cycle of planning, implementing, checking and improving.
- AI inventoryKI-Inventar
- Inventory of AI systems and AI agents with purpose, classification under the EU AI Act, data sources and owners. In the integrated model, they are managed as application components with AI attributes.
- ArchiMateArchiMate-Modellierungssprache
- Modelling language from The Open Group for enterprise architectures, in version 4 since April 2026. Its motivation elements such as Stakeholder, Driver, Goal, Principle and Requirement are well suited to linking obligations and controls with architecture elements.
- Architecture BoardArchitekturgremium
- Board that makes architecture decisions, approves deviations and monitors compliance with the target state. In the integrated variant, it takes on tasks of the GRC steering committee and prepares the management review.
- Architecture Building BlockABB · Architekturbaustein
- Vendor-neutral description of a required capability in the TOGAF Standard; the concrete implementation is called a Solution Building Block. Controls can be managed as reusable building blocks that meet several requirements at once.
- Architecture Compliance ReviewArchitektur-Compliance-Review
- Review of whether an initiative complies with the target state and the agreed requirements; the TOGAF Standard classifies the result into levels of conformance. Extended with security and compliance criteria, the review provides evidence for internal audit and certification.
- Architecture ContractArchitekturvertrag
- Agreement between the architecture function and the implementing project on requirements, deliverables and quality. In the integrated management system, it contains the project's security, data protection and compliance requirements.
- Architecture PrinciplesArchitekturprinzipien
- Principles for architecture decisions, described in the TOGAF Standard with Name, Statement, Rationale and Implications. A joint set of principles unites architecture, security, data protection and compliance principles.
- Architecture RepositoryArchitektur-Repository
- Store for all architecture content in the TOGAF Standard — with the Architecture Landscape, Reference Library, Standards Library, Governance Repository, Architecture Requirements Repository and Solutions Landscape. In the integrated management system, it is controlled documentation and the source of all registers.
- Autonomy levelsAutonomiestufen · L0–L3
- Graduated scale of how much an AI agent may execute on its own — from manual work through proposals and execution with approval to autonomous, logged execution. VamiGRC uses four levels from L0 to L3, set per task category.
- Capability MapFähigkeitslandkarte
- Structured overview of what an organisation must be able to do — independent of organisational structure and technology. Rated by criticality, it is the common basis for risk assessment, business impact analysis and the critical or important functions under DORA.
- DispensationAusnahmegenehmigung
- In the TOGAF Standard, the time-limited authorisation by the Architecture Board to deviate from architecture requirements subject to conditions. In the integrated management system, every dispensation is also a documented risk acceptance with authority and expiry date.
- Enterprise ContinuumUnternehmenskontinuum
- Classification framework of the TOGAF Standard that arranges architecture and solution building blocks from generic to organisation-specific. It helps to reuse reference architectures and control building blocks.
- Enterprise MetamodelUnternehmensmetamodell · until TOGAF 9.2 Content Metamodel
- Part of the TOGAF Content Framework that defines the entities, attributes and relationships of an architecture model. For the integrated management system, it is extended with obligation, risk, control and evidence — Series Guide G152 itself recommends adding attributes for information security and risk management to the entities.
- Governance Repositoryuntil TOGAF 9.2 Governance Log
- Part of the Architecture Repository in which decisions, compliance assessments and approved exceptions are recorded. Linked to controls, it becomes a source of evidence for audits.
- GRC GraphGRC-Graph in VamiGRC
- Data model in VamiGRC that links business processes, information, assets, service providers, risks, controls and evidence as a graph. An example of the shared model on which an integrated management system and its agents work.
- Harmonized StructureHS · Harmonisierte Struktur · until October 2026 Appendix 2 to Annex SL
- Common clause structure of the ISO management system standards, since October 2026 part of the joint ISO/IEC Directives: context, leadership, planning, support, operation, performance evaluation and improvement. It is the backbone of every integrated management system.
- Human-in-the-LoopMensch in der Entscheidungsschleife
- Operating principle in which a human reviews and approves an AI system's proposals before they take effect. For GRC agents, this means: preview, approval, log.
- Integrated management systemIMS · Integriertes Managementsystem
- Management system that governs several standards and obligations — such as information security, data protection, AI, business continuity and quality — with shared processes, roles and evidence. TOGAF adds the architecture model as a shared data foundation.
- Model Context ProtocolMCP
- Open protocol through which AI assistants and agents use defined tools and data of other systems; part of the Linux Foundation's Agentic AI Foundation since December 2025. For agentic GRC, this means: agents do not access systems freely but through approved tools with permissions and logging.
- Obligations registerPflichtenregister
- Register of legal, regulatory, contractual and internal requirements with source, applicability, owners and affected elements. In the integrated management system, it is the concrete form of Requirements Management.
- Open FAIRFactor Analysis of Information Risk
- Risk standard from The Open Group with a taxonomy and analysis method for quantifying information risks in monetary terms, since May 2025 as Risk Taxonomy 3.1 and Risk Analysis 2.1. Complements the risk management technique of the TOGAF Standard when risks are to be quantified per capability.
- OSCALOpen Security Controls Assessment Language
- Machine-readable NIST formats for catalogues, profiles, system descriptions and assessment results, with a mapping model for mappings between catalogues since version 1.2. This makes obligations and control mappings reusable — for people, tools and agents.
- Register of informationInformationsregister (DORA)
- Register of all contractual arrangements of a financial entity with ICT third-party service providers, including the functions they support. In the integrated model, it is generated from service providers, contracts and functions.
- Requirements ManagementAnforderungsmanagement
- Central process of the ADM: requirements are captured, assessed, maintained and passed on in all phases. In the integrated model, it becomes the obligations register with impact analysis.
- Statement of ApplicabilitySoA · Erklärung zur Anwendbarkeit
- Document required by ISO/IEC 27001 listing the necessary controls, their justification, their implementation status and the justified exclusions. In the integrated model, it is derived from the building block decisions of Phase E.
- Statement of Architecture WorkArchitekturauftrag
- Agreement at the start of an ADM cycle on scope, approach, deliverables and schedule. Extended with obligations and risk objectives, it is the starting point for an initiative's GRC planning.
- Three Lines ModelModell der drei Linien
- Model published by the Institute of Internal Auditors in 2020 and updated by a statement of position in July 2026 (core structure unchanged), covering the roles of the governing body, management and internal audit. It helps to assign the architecture function and GRC roles clearly.
- TOGAF Series GuidesTOGAF-Leitfäden
- Supplementary guides to the TOGAF Standard that are developed independently of the Fundamental Content — for example on business capabilities, value streams, agile approaches or the integration of risk and security (G152).
- Transition ArchitectureÜbergangsarchitektur
- Intermediate state between baseline and target architecture. Important for GRC because intermediate states carry their own risks and exit strategies under DORA can be described as Transition Architectures.
FAQ
Frequently asked questions on TOGAF, GRC and the integrated management system
Short answers to typical questions from executive management, the CISO office, enterprise architecture, compliance and internal audit.
The TOGAF Standard from The Open Group is a framework for enterprise architecture. Its 10th Edition — since May 2025 with Technical Corrigendum 1 — consists of the Fundamental Content in six documents covering the Architecture Development Method (ADM), techniques, Enterprise Metamodel, repository and governance, plus the TOGAF Series Guides for deeper topics. TOGAF is neither a law nor a management system standard and does not prescribe any security controls. It describes how to plan, decide on, implement and govern architecture — and that is exactly what makes it the ideal partner for GRC.
Not for organisations. The Open Group certifies individuals, for example in the TOGAF Enterprise Architecture programme with the Foundation and Practitioner levels. A company cannot be certified to TOGAF. Anyone who needs a certificate for their management system still has the ISMS audited against ISO/IEC 27001, or other management systems against ISO standards — architecture work based on TOGAF provides the structures and evidence for this.
Organisations can use the standard for their own architecture work under a free, non-commercial licence; consulting, training or tools for third parties require a paid commercial licence from The Open Group. Important for agentic operation: the licence terms prohibit using the texts of the standard to train generative AI, or using such tools to generate content from them, without written permission. Agents therefore work on your model and your data, not on the text of the standard. Not legal advice.
Because both talk about the same objects: business capabilities, processes, applications, data, technology and service providers. Kept separate, they produce duplicate inventories, contradictory criticality ratings, two boards and evidence that has to be searched for before every audit. Combined, every risk is linked to an architecture element, every control to a building block and every piece of evidence to a control and an element — the effect of changes on risks and obligations becomes visible immediately.
Very well, because both are designed as cycles. The Preliminary Phase and Phase A correspond to context, leadership and planning; Phases B to D deliver the risk assessment on the model; E and F plan risk treatment as a roadmap; G governs implementation and generates evidence; H monitors, evaluates and improves. Requirements Management at the centre corresponds to the ongoing handling of the requirements of interested parties. The integration navigator on this page shows the mapping for all clauses of the Harmonized Structure.
Not necessarily. What matters is a shared model with one system of record per object type. Organisations with an established EA practice keep their EA tool and connect it to the GRC platform via interfaces. Organisations without an EA practice often start with a lean model directly in the GRC platform — capabilities, processes, applications, data, technology, service providers — and decide later whether an EA tool is needed. What is important is that terms and identifiers are the same in both worlds.
Both frameworks demand knowledge that sits in the architecture model. DORA requires the identification and documentation of ICT-supported business functions, information and ICT assets and their dependencies, as well as a register of information on ICT third-party service providers. NIS2 requires risk management measures ranging from asset management to supply chain security, as well as reports within 24 and 72 hours. With a maintained model, you generate registers as views instead of compiling them, and in an incident you quickly know which services are affected.
Nothing in the requirements — a lot in the way you work. Scope, asset inventory, risk assessment, Statement of Applicability, internal audit and management review are based on the shared model and the outputs of the ADM phases. For auditors, the ISMS becomes easier to follow because the chain from requirement via control and building block to evidence is continuous. Important: documentation in the repository must meet the standard's requirements for document control — approval, versioning, retention.
Management decides, and both variants work. More important than who chairs it are the mandate, composition and rules of procedure: architecture, information security, the risk and compliance functions, data protection and the business units belong on it, while internal audit remains independent. The board decides on the target state, exceptions and risk acceptances within its authority and reports to management, which bears overall responsibility under NIS2 and DORA.
AI agents take on clearly defined tasks on the shared model: evaluating new obligations and mapping them to affected elements, analysing the impact of changes on risks and controls, mapping controls to multiple frameworks, collecting evidence from connected systems, reporting discrepancies between model and operations, and drafting reports. They work through defined tools with their own minimal permissions. Write actions appear as proposals that a responsible person approves; only low-risk routines such as monitoring deadlines run autonomously — and everything is logged.
We recommend against it. Risk acceptances, exceptions and decisions on the target state are management tasks involving authority and accountability — the standards require risk owners and management to decide. Agents prepare such decisions: they compile facts, dependencies, options and sources. Only low-risk routines such as monitoring, deadlines and data reconciliation may run autonomously — logged and able to be paused at any time.
Internal GRC agents are generally not high-risk AI systems under the EU AI Act. Nevertheless, obligations apply, such as promoting AI literacy and, since 2 August 2026, transparency obligations, for example when people interact with AI or AI generates content. Regardless of this, we recommend treating the agents like any other AI system: add them to the AI inventory, assess their risks, define human oversight and logging — ISO/IEC 42001 provides the framework for this. Not legal advice.
VamiGRC is designed as an agentic integrated management system: five management systems share one data set in the GRC Graph, in which processes, information, assets, service providers, risks, controls and evidence are linked. Specialised AI agents work along autonomy levels L0 to L3, which are set per task category; at level L2 no task closes without human approval, while at L3 agents work autonomously, logged and pausable at any time. Via the Claude connector, Claude works with the data; nothing is written without your OK. vamigrc.com does not describe a TOGAF approach — mapping the ADM phases to these functions is VamiSec's interpretation and part of our consulting.
That depends on the starting point. In our experience, first results — core metamodel, joint board, an inventory from a single source and an obligations register for one scope — can be achieved in around 100 days. A fully integrated management system with an exception process, coordinated audits, a joint management report and the first agentic use cases takes closer to twelve months. Organisations that already have both make faster progress; those building from scratch should prioritise along the most pressing obligations.
With the integration check on this page to see gaps per area, and with the decision aid for your path. Then three steps: a mandate from management, a core metamodel with systems of record and a first scope with the most urgent register, for DORA or NIS2, for example. Boards and the exception process follow; agents only come in once the model is clean.
They complement each other. TOGAF describes the approach and governance of architecture work. ArchiMate, also from The Open Group and in version 4 since April 2026, is the language in which the model is drawn and exchanged — including motivation elements for goals, principles and requirements. OSCAL from NIST makes catalogues of requirements and controls machine-readable and reusable. Open FAIR, again from The Open Group, provides a method for assessing risks quantitatively. Together, they produce a model that people and agents can read alike.
Estándares y fuentes
Los contenidos de esta página se basan en las siguientes guías y estudios disponibles públicamente.
The Open Group · 2025
The TOGAF® Standard, 10th Edition (C220) ↗
Fundamental Content in six documents plus TOGAF Series Guides; current version including Technical Corrigendum 1 of May 2025. The online version can only be read after signing in.
The Open Group · 2022
The Open Group Announces Launch of the TOGAF® Standard, 10th Edition ↗
Published on 25 April 2022: modular structure of Fundamental Content and Series Guides, more guidance for agile and digital initiatives.
The Open Group Security Forum, The SABSA Institute · 2016
TOGAF® Series Guide: Integrating Risk and Security within a TOGAF® Enterprise Architecture (G152) ↗
Security and risk artefacts per ADM phase, including registers of applicable laws and control frameworks; listed among the Series Guides of the 10th Edition.
The Open Group · 2026
TOGAF® Series Guides — Overview ↗
Guides to the 10th Edition, for example on Business Capabilities, Value Streams, agile approaches and Architecture Roles and Skills; as of November 2026, no guide on AI agents.
The Open Group · 2019
How to Model Enterprise Risk Management and Security with the ArchiMate® Language (W172) ↗
Modelling of risks, controls and security requirements with ArchiMate.
The Open Group · 2026
ArchiMate® 4 Specification (C260) ↗
Current version of the modelling language since 27 April 2026; the motivation elements no longer include the former Constraint.
The Open Group · 2025
Open FAIR™ Risk Taxonomy (O-RT), Version 3.1, and Risk Analysis (O-RA), Version 2.1 ↗
Quantitative assessment of information risks in monetary terms; versions dated 22 May 2025.
The Open Group · 2026
TOGAF® Standard, 10th Edition — Downloads and Licences ↗
Free non-commercial licence for organisations, commercial licence for consulting, training and tools; prohibition on processing the texts with generative AI without permission.
The Open Group · 2025
Designing the Future of Quality with the TOGAF® Standard and AI (Y25A) ↗
Case study dated 19 November 2025: ADM, ArchiMate and AI-assisted search for an integrated quality management system.
The Open Group · 2026
TOGAF® Certification Portfolio ↗
Certifications for individuals, such as TOGAF Enterprise Architecture Foundation and Practitioner; no certification of organisations.
ISO/IEC · 2022
ISO/IEC 27001:2022 — Information security, cybersecurity and privacy protection — Information security management systems — Requirements ↗
Clauses 4 to 10 following the Harmonized Structure and Annex A with 93 controls; source of the clause references on this page.
ISO/IEC · 2026
Harmonized Structure with guidance for use — joint document to the ISO/IEC Directives, Part 1 (formerly Annex SL, Appendix 2) ↗
Common clause structure of the ISO management system standards; part of the joint ISO/IEC Directives since 5 October 2026.
ISO · 2026
Integrated Management System — A practical guide (IMS-PG) ↗
Practical guide from ISO, dated 17 March 2026, for an integrated management system based on several standards: prepare, connect, integrate.
ISO · 2018
ISO 31000:2018 — Risk management — Guidelines ↗
Guidelines for risk management, not certifiable; a common language for risk assessment and risk treatment.
ISO/IEC · 2023
ISO/IEC 42001:2023 — Information technology — Artificial intelligence — Management system ↗
AI management system following the Harmonized Structure; framework for governing the organisation's own AI agents.
ISO/IEC · 2026
ISO/IEC 27090:2026 — Cybersecurity — Artificial intelligence (AI) — Addressing security threats and compromises to AI systems ↗
Guidance on the security of AI systems, published in October 2026; supplements ISO/IEC 27001 and 27002.
European Parliament and Council · 2022
Directive (EU) 2022/2555 (NIS2) ↗
Governance, risk management measures and reporting obligations for essential and important entities.
Federal Republic of Germany · 2025
German BSI Act (BSIG) as amended by the NIS2 Implementation and Cybersecurity Strengthening Act ↗
German transposition of NIS2, in force since 6 December 2025.
BSI · 2026
BSI Standard 300-1 — Methodik Grundschutz++ (Grundschutz++ Methodology), Version 1.0 ↗
The information domain as assets with their dependencies, from the business process down to the room; CMDBs and service maps are permitted.
European Parliament and Council · 2022
Regulation (EU) 2022/2554 (DORA) ↗
ICT risk management, register of information, incident reporting and testing; applicable since 17 January 2025.
European Parliament and Council · 2024
Regulation (EU) 2024/1689 (EU AI Act) ↗
AI literacy, transparency, obligations for high-risk AI systems including human oversight and logging.
European Parliament and Council · 2026
Regulation (EU) 2026/1744 (Digital Omnibus on the EU AI Act) ↗
Postpones the high-risk obligations: Annex III from 2 December 2027, Annex I from 2 August 2028.
European Parliament and Council · 2024
Regulation (EU) 2024/2847 (Cyber Resilience Act) ↗
Cybersecurity requirements for products with digital elements; reporting obligations since 11 September 2026, full application from 11 December 2027.
European Parliament and Council · 2016
Regulation (EU) 2016/679 (GDPR) ↗
Records of processing activities, data protection by design, data protection impact assessment.
NIST · 2026
NIST Open Security Controls Assessment Language (OSCAL) ↗
Machine-readable catalogues, profiles, system descriptions and assessment results; with a dedicated mapping model since version 1.2.
Agentic AI Foundation (Linux Foundation) · 2026
Model Context Protocol — Specification 2026-07-28 ↗
Open protocol for tool access by AI agents; since July 2026 it supports follow-up questions to the user mid-call, for example for confirmations.
OWASP GenAI Security Project · 2025
OWASP Top 10 for Agentic Applications for 2026 ↗
Published on 9 December 2025: typical risks of agentic applications, such as goal hijacking, tool misuse, and identity and privilege abuse.
IMDA Singapore · 2026
Model AI Governance Framework for Agentic AI ↗
Limit agents' autonomy and tool access in advance; secure accountability through defined approval points.
The Institute of Internal Auditors · 2026
The IIA's Three Lines Model — Statement of Position ↗
Position paper of 8 July 2026 that updates the 2020 model; the core structure of the three lines is retained.
Software & Systems Modeling 18(3) · 2019
Mayer, N. et al.: An integrated conceptual model for information system security risk management supported by enterprise architecture management ↗
Academic model for integrating architecture management and security risk management, based on TOGAF and ArchiMate.
VamiSec GmbH · 2026
VamiGRC — agentic integrated management system ↗
Autonomy levels L0 to L3, GRC Graph, Claude connector with a preview before every change; information according to vamigrc.com, as of 21 November 2026.
Combine architecture and GRC into one system?
We support you from the integration check through the metamodel, joint board and registers to agentic operation with VamiGRC — pragmatic, designed for auditability and without promises that no standard can back up.