Skip to main content
ISO 27001

ISO 27001 Statement of Applicability: how to write one auditors accept

Published
Last updated
ISO 27001
A control table with applicable and excluded rows under a magnifying glass, next to icons for the organizational, people, physical and technological Annex A themes

What the SoA must contain

  • Clause 6.1.3 d) of ISO/IEC 27001:2022 requires the SoA to include:
  • the necessary controls
  • the justification for including them
  • whether they are implemented or not
  • the justification for excluding any Annex A control

The 93 Annex A controls at a glance

ThemeNumber of controlsExamples
Organizational37Policies, supplier security, incident management
People8Screening, awareness training, remote working
Physical14Secure areas, equipment protection, clear desk
Technological34Access control, logging, secure development, backups

How to write the SoA, step by step

  1. Finish your risk assessment and risk treatment plan first. The SoA comes from them, not the other way round.
  2. List all 93 controls in a table.
  3. For each control, mark Applicable or Not applicable.
  4. Write a short justification: the risk it treats, a legal or contractual requirement, or a business need.
  5. For excluded controls, explain why the risk doesn't exist in your scope (for example, no in-house software development).
  6. Record the implementation status: implemented, partially implemented or planned, with a reference to the policy or evidence.
  7. Version, approve and review it at least yearly, and whenever the scope or risks change.

Mistakes auditors flag most

  • Excluding controls just because they're hard to implement
  • Justifications copied from a template that don't match your business
  • Marking controls "implemented" with no evidence behind them
  • An SoA that doesn't match the risk treatment plan
  • Still using the 2013 list of 114 controls

Test the SoA in your internal audit, and check the rest of your documents against our ISO 27001 audit checklist.

Example SoA row

ControlApplicableJustificationStatusEvidence
8.13 Information backupYesRisk of data loss from ransomware and hardware failure (Risk R-07); customer contracts require recovery within 24 hoursImplementedBackup policy v2.1; monthly restore test records

Frequently asked questions

Yes. Clause 6.1.3 d) of ISO/IEC 27001:2022 requires it, and certification auditors review it early in the Stage 1 audit.

93 Annex A controls, grouped into four themes: organizational (37), people (8), physical (14) and technological (34).

Yes, if you justify the exclusion, usually because the risk doesn't exist in your scope. Excluding a control only because it's difficult isn't acceptable.

At least once a year during the management review, and whenever your scope, risks or controls change.
Hi! I'm your AI Assistant 💬