Skip to content

ISO 27001:2022 SoA: The Evidence Checklist

The ISO 27001:2022 edition finalized its transition window at the end of 2025, which makes the 2022 structure the only live version for certificate holders now — and its most asked-about artifact is the Statement of Applicability (SoA). The SoA is the declaration that turns risk assessment into a control plan: which of the 93 Annex A controls you apply, which you explicitly exclude, and why. In 2026, buyer reviews at banks, insurers, and large B2B customers sample the SoA because it is the honest map of your physical cybersecurity posture — more honest, historically, than a certificate alone.

Key facts

The Statement of Applicability is the anchor document of an ISO 27001 review, mapping all 93 Annex A controls to a live risk register.

  • The Statement of Applicability (SoA) is the anchor document of an ISO 27001 review.
  • It must map to your live risk register and cover all 93 Annex A controls with exclusion justifications.
  • Keep it current whenever the risk assessment changes, incidents occur, or controls are updated.
  • It is also the data source behind most trust-center and buyer questionnaires.

Whether you held the 2013 certificate through the transition or are certifying for the first time, the 2022 SoA has exactly the failure modes this guide shows how to avoid: exclusions without justification, controls marked applicable with no evidence behind them, and staleness after the risk register moves.

The Required Asset: A Current, Justified, Published SoA

  • Asset: Statement of Applicability mapped against your live risk register — plus the control evidence index buyers need
  • Issued by: you (the ISMS owner) — certification bodies audit it, and it is the anchor document of every ISO 27001 review
  • Deadline: continuous — the SoA re-tied whenever the risk assessment changes, major incidents occur, or the control landscape updates
  • Mandatory elements: 93-control applicability table, exclusion justifications, implementation status, evidence references, risk-assessment linkage
  • Enforcement: certification findings, failed buyer reviews; the SoA is also the data source consumer of every trust-center questionnaire you answer
  • Publish yours: Publish your ISO 27001 evidence pack →

The 93 Controls, Grouped

The 2022 edition reorganized Annex A controls out of 14 domains into four themes, with 93 controls total and a newly explicit cloud-security control family:

  • Organizational controls (37) — policies, roles, asset inventories (including cloud-service use), threat intelligence, project security, ICT readiness.
  • People controls (8) — screening, terms of employment, training, remote-working discipline, reporting channels.
  • Physical controls (14) — entry management, working-in-secure-areas, equipment siting and lifecycle, utilities, cabling, environmental controls.
  • Technological controls (34) — the technical spine: user access management, privilege control, secure authentication, data handling (encryption, information deletion, data leakage prevention), network protection, secure development, logging, backup, cloud services security.

Also new at the standard level: guidance-series attributes (control types, infosec properties, cybersecurity concepts) that run through the table and give auditors a consistent language — practical value is real for gap analysis but heavy for "we engineered a spreadsheet" so keep the attribute set small.

What the SoA Must State Per Control

For each of the 93 controls, the SoA row answers applicability, meaning it does not just say "yes":

  • Applicable or not applicable. Inapplicable statements require justification: typically because the control addresses a risk your context cannot create (no physical facility, no software development, no in-house cloud assets...)
  • Implementation status — absent on greenfield lines, but expected in audit cycles on operating systems
  • Evidence reference. The work product that demonstrates the control: policy document, procedure, system configuration screenshot, scan report, training log, attestation. This column is precisely what auditors sample and what serious buyer reviews ask you to make available.
  • Risk linkage. Which assessed risk(s) the control answers. The 2022 SoA is risk-assessment-tied: controls that map to no identified assessed risk are the finding recursion auditors use to probe whether risk assessment was real.

The exclusion discipline is the metric of a grown-up ISMS: exclusions are (1) risk-based, (2) written with the reasoning, and (3) survive the auditor asking "can this risk really not materialize at your company?" A control excluded to reduce workload, without those three, is the classic certification finding — and the reason SoAs get revisited in buyer post-review questionnaires.

Transition Notes If You Just Came From the 2013 Edition

If your transition completed by the end of the window, the SoA you filed at transition is the operative one. Post-transition care items, in audit-sampling order:

  • Re-verify exclusions justified under the older structure (the 11 old cloud-related points fold into technological controls; the justification language usually needs rework)
  • Update the control-evidence references that pointed to the old clause numbering anywhere (policies, internal audit checklists, buyer questionnaires) — cross-references drifting out of sync is the most common post-transition audit noise
  • Confirm current implementation status for all marked-in-scope-but-new controls (the 11 newly introduced controls, most visibly the cloud-security family) — these are where auditors first look for "transitioned on paper"

The Evidence Index Buyers Sample

Buyer reviews at regulated customers (and their DORA-grade counterparts — see the connection section) walk the SoA with a standard sample list. Prepare it once, publish it, and the review ends early:

  1. Access management — leaver process date stamps, privileged-access review logs, MFA coverage statements. The most-sampled control family everywhere in 2026.
  2. Backup and restoration — restore test records with dates, not just backup job success. "Backups exist" fails; "restore completed in X hours on date" passes.
  3. Incident and vulnerability management — incident log with triage outcomes, vulnerability scan schedule and remediation windows.
  4. Supplier security — the approved-supplier security register: onboarding gates, assessment record, review dates. This is where the SoA's evidence table peeks into your supply chain.
  5. Cryptographic material handling — key inventory, rotation evidence for the keys that encrypt customer data.
  6. Human layer — training completions and awareness refreshers by date, secured-delegation evidence for high-privilege roles.

Bit of posture advice: "current scan report" and "leaver removed same week" is what buyers remember — the certificate only set the appointment for those proofs.

Keeping the SoA Alive

The SoA drifts when organizations treat it as a certification-period document. Avoiding the drift is mostly a cadence choice:

  • Tie it to your risk-assessment cycle. Any risk register change re-validates affected control statuses — a workflow, not a document edit.
  • Automate the evidence references where you can. Log aggregation, access reviews, scan schedules, backup tests produce timestamped output on their own; the SoA table links to the living source instead of a stale artifact.
  • Change management connects. New system, new SaaS tool, new market: each triggers an applicability check for the relevant controls — usually organizational/access controls, sometimes cloud and physical.
  • Publish the summary. External reviews don't need your risk register detail; they need the control-status summary, evidence index, and certificate currency in one verifiable page.

Your SoA in the Buyer Context

For suppliers to finance-grade customers, the SoA is now the control posture that customer-facing regimes query directly — regulator-facing regimes (such as the financial-sector operational resilience rules) reach into ISO-certified control environments through their own required frameworks. The published-SoA posture gives you a compliance artifact that assures a verification of control status instead of a repeated questionnaire; this is the customer-facing part of the ISMS work your certificate audit already makes you maintain.

Frequently Asked Questions

Do we have to apply all 93 controls? No. The SoA documents applicability decisions risk by risk; non-applicability is legitimate when justified. But exclusions are where audits and buyer reviews probe first - a weak justification for excluding the cloud-security controls at a company running cloud services is an automatic flag.
Can the SoA and the risk register be merged into one document? Technically possible, operationally unwise. The risk register changes at a different cadence and contains sensitivity the external reviewers do not need - keeping SoA as the published summary of that register is both more auditable and a safer disclosure practice.
How often must we update the SoA? Whenever risk assessment, the control landscape, incidents, or business scope change materially. Operating the update as a trigger-based workflow avoids the certification-sprint model that produces stale evidence and audit findings.
Is SOC 2 an alternative to ISO 27001? They overlap heavily but serve different recognition markets. SOC 2 is the US attestation-style report; ISO 27001 is the management-system certificate that certifies scope across a defined organization. Many B2B suppliers maintain one primary and publish evidence pages that answer both sets of questionnaires.

Last updated: November 17, 2026

Global Digital Trust & Compliance

Sustalium is the digital-first platform for managing complex business certificates and sustainability declarations across global supply chains.

Environment & ESG
  • Digital Product Passport (DPP)
  • Carbon & Water Footprint
  • Circularity & Reuse (ISO 14021)
  • De-Forestation Free
Product & Food Safety
  • FSMA 204 (FDA Traceability)
  • REACH & RoHS Compliance
  • PFAS-Free & VOC Declarations
  • Prop 65 & TSCA Title VI
Social & Ethical
  • ISO 26000 Responsibility
  • Modern Slavery Statements
  • UFLPA Forced Labor Traceability
  • Ethical Labor Declarations
Governance & Trade
  • Swiss Made & Origin Claims
  • GDPR & AI Ethics (EU AI Act)
  • CE Marking & UKCA Conformity
  • Bill S-211 (Canada) Reporting

Have questions about a specific standard?
Contact our compliance team at compliance@sustalium.com