ISO 27001
The ISO 27001 Statement of Applicability Explained
21 June 2026 · Updated 21 June 2026
The Statement of Applicability is the ISO 27001 document that lists every Annex A control, states whether it applies, and gives a reason for each inclusion and exclusion. Clause 6.1.3 makes it mandatory. It connects the risk treatment to the controls, and it is the master checklist the certification auditor works from.
What is the Statement of Applicability in ISO 27001?
The Statement of Applicability, or SoA, is the document required by clause 6.1.3 of ISO 27001. It records the controls an organisation has judged necessary to treat its information security risks, why each one is included, whether it is implemented, and why any Annex A control has been left out.
Most teams first meet the SoA as a spreadsheet of 93 Annex A controls and assume the work is ticking the columns, but the sequence runs the other way. The controls come from the risk treatment first, and only then is that set compared against Annex A so nothing necessary is missed, with the comparison written down. The SoA is that record. Because it ties the risk assessment to controls an auditor can test, it is the centrepiece of an ISO 27001 certification, and a sensible place to start once the basics of what ISO 27001 is are clear.
What must the ISO 27001 Statement of Applicability contain?
Clause 6.1.3 d sets four things the SoA must hold, and a document missing any one of them is incomplete.
| What the SoA records | What it means |
|---|---|
| The necessary controls | Every control your risk treatment needs, drawn from Annex A and any additional controls of your own |
| Justification for inclusion | The risk or requirement each included control addresses |
| Implementation status | Whether each control is implemented, in progress, or not yet in place |
| Justification for exclusion | The reason any Annex A control does not apply to your scope |
In practice the SoA accounts for all 93 Annex A controls, so every one is marked applicable or not, together with any additional controls the risk treatment introduced that Annex A does not cover. Annex A is a reference set rather than a fixed checklist. The readiness checklist covers the documents around it.
Why does the ISO 27001 auditor care so much about the SoA?
The SoA is the master checklist for the whole audit, which is why the auditor returns to it constantly. At Stage 1 the auditor reads the SoA against the risk assessment and Annex A and checks that the exclusions are reasoned. At Stage 2 they sample the controls marked implemented and ask for the evidence behind them.
The quickest way to stall a Stage 1 is an SoA that does not yet exist, or one whose exclusions read “not applicable” with no reason given. The document has to be finished before Stage 1, not assembled during it. In practice, an assessor who reads “A.8.23 web filtering excluded, not applicable” on a cloud platform will stop and ask why, and a blank answer becomes a finding. Because this plays out across both stages, it helps to understand how the two audit stages run.
How is the ISO 27001 SoA different from the risk treatment plan?
These two documents are regularly confused, so it is worth separating them clearly. The risk treatment plan is the action plan: which risks, which treatment option, who owns the work and by when. The SoA is the standing control register: the full control set, each marked applicable or not, with status and justification. One is the plan of work, while the other is the record of which controls govern the system. Both come out of the same risk treatment under clause 6.1.3, and the SoA must be approved before Stage 1.
What are the common ISO 27001 SoA mistakes?
Four mistakes show up again and again in the SoAs we review. The first is building it control first, straight from Annex A, so that no control traces back to an actual risk, and an auditor will pull on that thread. The second is excluding controls with no justification, or excluding ones that plainly apply, such as access control or logging on a system that clearly needs them. The third is marking a control implemented when it is only written down, because documented is not the same as implemented and Stage 2 is where that gap surfaces. The fourth is letting the SoA go stale the day after certification, when it is living documented information: as the risk picture or the controls change, the SoA should change with them.
The SoA works best as the spine of the ISMS rather than a form filled in at the end. Get it right and the rest of the audit has something solid to stand on.
Frequently asked questions
Is the Statement of Applicability mandatory in ISO 27001?
Yes. Clause 6.1.3 d requires it as documented information, and it must be in place before the Stage 1 audit. It is one of the few documents the standard names explicitly.
What is the difference between the ISO 27001 SoA and the risk treatment plan?
The risk treatment plan is the action plan for treating specific risks, with owners and dates. The SoA is the standing register of all controls, marked applicable or not, with justification and implementation status. Both derive from the same risk treatment.
Do you have to include all 93 ISO 27001 Annex A controls in the SoA?
You account for all 93, marking each applicable or not with a reason, and you add any controls your risk treatment needs that Annex A does not list. Annex A is a reference set, so controls can be excluded where justified.
Can you exclude ISO 27001 Annex A controls from the SoA?
Yes, where the control does not apply to your scope and you record the reason. An exclusion with no justification, or excluding a control that clearly applies, is a common audit finding.
Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.
Sources:
- ISO/IEC 27001:2022, clause 6.1.3 (Statement of Applicability), 2022
- ISO/IEC 27002:2022 (control implementation guidance for Annex A), 2022
Last updated: 21 June, 2026
