Resources · Template
Statement of Applicability (SoA) template for ISO 27001
What is a Statement of Applicability?
The Statement of Applicability, or SoA, records which controls your organisation has decided are necessary, and why. ISO 27001 requires it, and requires a justification for every Annex A control you leave out.
It is not a risk assessment. The risk assessment decides which controls you need; the SoA records the result and checks it against Annex A so that nothing necessary is missed.
Each necessary control and why it is included: a risk, a law, a contract or a business need.
Whether the control is implemented.
A justification for every Annex A control that is excluded.
Statement of Applicability template
Ten columns. Three example rows are shown; the control names come from Annex A.
| Column | Example: included | Example: excluded |
|---|---|---|
| Control reference | A.5.15 | A.7.4 |
| Control name | Access control | Physical security monitoring |
| Applicable | Yes | No |
| Reason for inclusion | Risks R-04 and R-11; customer contracts | Not applicable |
| Justification for exclusion | Not applicable | No premises of our own; staff work remotely and hosting is with a cloud provider |
| Implemented | Yes | Not applicable |
| How it is implemented | Access control policy v3; role-based access in each system | Not applicable |
| Control owner | Head of IT | Not applicable |
| Evidence | Policy; quarterly access review records | Supplier's certificate for hosting |
| Last reviewed | 1 Oct 2026 | 1 Oct 2026 |
The example values are illustrative. Copying pastes the table as rows and columns into a spreadsheet or document.
How do you fill it in?
- Finish the risk treatment first
The SoA records decisions; it does not make them.
- List all 93 Annex A controls
Add any other controls you use.
- Decide each one
Included with a reason, or excluded with a justification.
- Record status and how
Point to the policy, procedure or system setting.
- Get it approved
By management, with risk owners.
- Review on change
And at least before each audit.
What goes wrong most often?
'Not applicable' with no reason
The auditor cannot assess the exclusion.
Instead: write a specific justification.
All 93 marked applicable by default
Controls are claimed that cannot operate in your context.
Instead: decide each on your risks.
No link to risks
Inclusions are justified only by 'best practice'.
Instead: refer to the risk, law or contract.
Do you need a template at all?
Controls arrive already mapped across frameworks, each with an owner and a status.
Statement of Applicability template: common questions
What must an SoA contain?
The necessary controls, the justification for including them, whether they are implemented, and the justification for excluding any Annex A controls.
Does the SoA need a version number?
It is documented information, so it should be controlled: versioned, dated and approved.
Can the SoA be a spreadsheet?
Yes. The standard does not prescribe a format.
Is this template free?
Yes. It is on this page, with no form to fill in. The Annex A control text itself is copyright of ISO and is not reproduced here.
Applicability, status and evidence for every control
The record lives with the audit, linked to its controls, findings and report.