Home
Workspace TOGAF knowledge guide

FRAMEWORK KNOWLEDGE · BEGINNER TO PRACTITIONER

TOGAF — Common Book of Knowledge

Connect business change, architecture decisions, delivery, and security assurance.

By Harpreet Singh · Reviewed 18 November 2026

Executive summary

  • Who this is for: learners, security practitioners, service owners, architects, and GRC reviewers working with TOGAF.
  • What to do first: Agree the architecture capability, stakeholders, business outcomes, scope, and decision rights.
  • How to verify: Trace an important requirement through architecture decisions, delivery work, acceptance tests, and operational feedback.

This is an independent practical learning guide, organized from foundations through implementation and review. It is not an official standard, exhaustive reproduction, certification course, or assurance opinion. Use the current official publications and applicable contractual or regulatory requirements for formal decisions. Examples and suggested checklists below are CyberSphere guidance, not prescribed requirements.

Foundations and vocabulary

The TOGAF Standard provides a method and shared vocabulary for developing and governing enterprise architecture. Its Architecture Development Method (ADM) can be tailored to the organization and revisited as priorities change.

ADM
The Architecture Development Method.
Viewpoint
An approach for addressing a class of stakeholder concerns.
Transition architecture
An intermediate architecture state on the path to a target.
Building block
A reusable architecture capability or component at an appropriate level of detail.

A practical learning route

  1. 1 · Understand scope
  2. 2 · Identify risk
  3. 3 · Assign action
  4. 4 · Collect evidence
  5. 5 · Verify and improve

Beginners should read the vocabulary and core domains first. Practitioners can use the implementation and evidence sections to review a real service. Experienced reviewers should challenge scope, inheritance, exceptions, and evidence quality. The lifecycle shown is an editorial learning aid, not an official framework diagram.

Core domains at a glance

DomainPractical interpretation
Preliminary · Establish the capabilityAgree how architecture decisions are made. Define the scope of the architecture practice, decision rights, principles, repository structure, and escalation paths.
Phase A · Architecture VisionIdentify sponsors, stakeholders, concerns, business drivers, and the intended value. Agree on the scope and the work needed to develop the architecture.
Phase B · Business ArchitectureDescribe baseline and target capabilities, processes, roles, and information flows from the business perspective. Identify where service ownership or operating-model changes are needed.
Phase C · Information Systems ArchitecturesDevelop data and application views. Map data ownership and classification, lifecycle and integration requirements, and dependencies between applications.
Phase D · Technology ArchitectureDefine platform, infrastructure, integration, and technology services. Document trust boundaries, resilience requirements, constraints, and gaps from the baseline.
Phase E · Opportunities and SolutionsGroup gaps into work packages and evaluate options. Define transition architectures when the target cannot be reached in a single step.
Phase F · Migration PlanningSequence work packages by dependency, value, cost, and risk. Agree on milestones, funding, and decision gates with delivery stakeholders.
Phase G · Implementation GovernanceReview delivery against architecture requirements and agreed design constraints. Record deviations, owners, decisions, and the evidence needed for acceptance.
Phase H · Architecture Change ManagementTrack operational feedback and new business or risk drivers. Decide whether a change is handled within the current architecture or requires another ADM cycle.
Requirements Management · Throughout the ADMMaintain traceability from stakeholder concerns to requirements, design decisions, work packages, and acceptance evidence. Reassess affected decisions when requirements change.
Architecture content and repositoryUse stakeholder-specific viewpoints, reusable building blocks, reference models, decision records, and standards. Keep baseline, target, and transition views distinguishable and versioned.

Implementation playbook

1. Understand what architecture contributes

Enterprise architecture helps explain how business capabilities, data, applications, and technology fit together and how they need to change. TOGAF provides a method and supporting vocabulary that organizations can tailor. It is not a replacement for cybersecurity control standards, a vulnerability scanner, or a product selection checklist. Begin with the decision that must be made and the stakeholders who need evidence. Build views that answer their concerns rather than producing diagrams for their own sake.

2. Establish governance and viewpoints

Define the architecture sponsor, decision forums, escalation routes, principles, repository ownership, and review cadence. Identify stakeholder concerns such as cost, service continuity, privacy, security, delivery speed, and operational support. A viewpoint describes how to address a type of concern; a view applies that approach to the architecture being considered. Record assumptions, constraints, decisions, and unresolved issues with owners. Keep business and technical stakeholders involved when trade-offs change.

3. Connect baseline, target, and transition

Describe the current architecture sufficiently to understand the change. Define the desired target and identify gaps. If a single change cannot reach the target safely, describe transition states with their temporary risks and dependencies. For a migration, document identity, data movement, integration, monitoring, and recovery at every state. A target diagram without a funded, dependency-aware transition plan leaves delivery teams to invent important security decisions under time pressure.

4. Integrate security throughout the ADM

Include security and privacy requirements in business, data, application, and technology work. Map trust boundaries, data classification, identity flows, key ownership, supplier dependencies, and recovery expectations. Evaluate alternatives against explicit requirements and record the trade-offs. Use relevant security frameworks to support requirement selection and assessment. An architecture approval does not prove that every safeguard was implemented or that an external certification has been obtained.

5. Govern implementation without losing traceability

Connect requirements to architecture decisions, work packages, delivery acceptance criteria, and evidence. Review significant deviations with business and risk owners. Agree whether a deviation is a time-limited exception, a revised target, or an unacceptable outcome. During delivery, verify the actual deployment against the approved constraints. Retain operational ownership, telemetry, support, and recovery arrangements as acceptance evidence rather than stopping at a design review.

6. Manage architecture change

Collect service performance, incidents, supplier changes, emerging threats, technology obsolescence, and new business demands. Determine whether each change fits existing architecture or requires renewed architecture work. Keep reusable building blocks, standards, decisions, and reference models versioned and discoverable. Retire obsolete artifacts to prevent teams from applying outdated patterns. Professional certification demonstrates learning against a defined syllabus; it does not certify an organization’s security posture or architecture effectiveness.

Evidence and assessment

Architecture principles, Statement of Architecture Work, baseline and target views, requirements traceability, roadmap, implementation governance records, and a change log.

For each artifact, retain its owner, collection date, system boundary, relevant period, source, and access restrictions. A reviewer should be able to distinguish a policy, a deployed configuration, an activity record, and a test of effectiveness. Keep sensitive logs and personal data in the organization’s controlled evidence system rather than submitting them to this website.

Review questionUseful evidenceWhat to challenge
Does the scope match the service?Asset and dependency inventory, service owner approvalOmitted environments, suppliers, regions, or privileged paths
Is the activity implemented?Configuration exports, operating records, approvalsWritten intent without deployed behavior
Does it work?Authorized functional tests and sampled operating recordsIncomplete populations, stale screenshots, uncontrolled exceptions
Are deficiencies addressed?Action register, risk approval, corrective-action retestExpired exceptions or closure without verification

Hypothetical example: For an internet-facing WAF modernization, capture service owners and risk appetite in A and B, map application and data flows in C, design trust boundaries and failover in D, sequence migrations in E and F, then verify delivery and operational feedback in G and H.

Connect threat intelligence to framework work

Start with the vendor advisory and affected versions. Check your inventory, exposure, business impact, and existing safeguards before deciding which framework activity is relevant. Record the CVE, asset owner, treatment, due date, evidence, and residual risk. Use the CISA KEV dashboard for known-exploitation context and Global Cyber News to locate source-linked reporting.

For this chapter, ask: Trace an important requirement through architecture decisions, delivery work, acceptance tests, and operational feedback. This is a reasoning prompt, not an approved control mapping. A single vulnerability can reveal several weaknesses, and fixing it does not establish compliance with an entire framework. Have a competent reviewer validate any formal mapping and retain the framework version and rationale.

Practitioner cheat sheet

Use these prompts during a service review. Completion is a learning aid and does not calculate compliance.

  • Define the service, boundary, applicable version, and accountable owner.
  • Record business requirements, threats, dependencies, and risk decisions.
  • Select appropriate outcomes or controls and document why they apply.
  • Assign implementation, evidence ownership, cadence, and escalation.
  • Test behavior within authorized scope and preserve the result.
  • Document exceptions with approval, compensating safeguards, and expiry.
  • Track corrective actions, retest, and review after material change.

Common mistakes and review questions

  • Treating ADM phases as an inflexible waterfall.
  • Producing views without an audience or decision purpose.
  • Omitting transition-state security and operational ownership.
  • Confusing design approval with implemented control effectiveness.

Check your understanding

  1. What is inside the boundary, and which dependency could invalidate the conclusion?
  2. Which artifact demonstrates operation rather than only policy intent?
  3. Who accepts remaining risk, and what change would trigger reassessment?
What a strong answer includes

A named service and owner, a clearly bounded population, current evidence of operation, a repeatable verification step, and an approved treatment for unresolved risk. An answer that only names a framework or tool is incomplete.

Official references and further reading

Read the source owner’s current publication and licensing terms. This website is independent and is not endorsed by NIST, ISO, AICPA, CIS, or The Open Group.

Continue with the Governance & Risk Playbook · Suggest a correction or topic

Other framework chapters

Home · Framework knowledge library · Privacy