The Statement of Applicability (SoA) is the mandatory ISO 27001 document that lists the Annex A controls, states whether each applies, justifies inclusion or exclusion, and records implementation status. It links the risk assessment to the chosen controls and is the auditor’s central reference, which is why a weak SoA is a common source of findings.
If ISO 27001 has one document that ties everything together, it is the Statement of Applicability. Auditors start with it, and so should the organisation.
What is the SoA and why does it matter?
The Statement of Applicability, SoA, is a mandatory ISO 27001 document that lists the Annex A controls and, for each, states whether it applies to the organisation, gives the justification for including or excluding it, and records its implementation status. It is the document that connects the organisation’s risk assessment and risk treatment to the specific controls it has chosen to operate, and in doing so it acts as the central reference for the whole information security management system.
Its importance comes from being the single place that answers, for every control, whether the organisation performs it and why. Certification auditors use the SoA as their map: they start from it to verify that included controls are actually implemented and that any exclusions are properly justified. Because it exposes the logic of the entire management system in one document, a vague, inaccurate or poorly justified SoA is one of the most common sources of audit findings. Getting it right, accurate status, sound justifications, alignment with the risk assessment, is one of the highest-value things an organisation can do in an ISO 27001 program.
Exclusions and the link to risk
ISO 27001 allows controls to be excluded, but only where they are truly not applicable, and every exclusion must carry a valid justification in the SoA tied to the organisation’s context and risk assessment. Excluding a control because it is inconvenient or expensive is not acceptable and will draw a finding; the justification matters as much as the decision. This is where the SoA’s link to the risk assessment becomes clear: the organisation assesses its risks, decides how to treat them, and the SoA records which Annex A controls support that treatment and why each applies or does not. The risk assessment drives the SoA, and the SoA demonstrates that the selected controls actually address the identified risks. Kept accurate and current, the SoA is not audit paperwork but the working summary of how the organisation manages information security. Where an organisation wants help building a sound SoA and ISMS, Cybernion can help through ISO 27001 advisory.
Frequently asked questions
What is a Statement of Applicability?
The Statement of Applicability, or SoA, is a mandatory ISO 27001 document that lists the Annex A controls, states whether each one applies to the organisation, gives the justification for including or excluding it, and records its implementation status. It links the organisation’s risk assessment to the controls it has chosen, and it is the central reference that ties the whole information security management system together.
Why is the SoA so important in ISO 27001?
The SoA is important because it is the single document that shows what the organisation has decided to do about each control and why, making it the auditor’s map of the management system. Certification auditors use it as a starting point to check that included controls are actually implemented and that exclusions are justified. A weak or inaccurate SoA is one of the most common sources of audit findings, so it repays careful attention.
Can you exclude controls in the SoA?
Yes. ISO 27001 allows controls to be excluded where they are truly not applicable, but every exclusion must be justified in the SoA with a valid reason tied to the organisation’s context and risk assessment. Excluding a control simply because it is inconvenient is not acceptable and will draw an audit finding. The justification is as important as the decision itself.
How does the SoA relate to the risk assessment?
The SoA is the output that connects the risk assessment and risk treatment to the controls. The organisation assesses its risks, decides how to treat them, and the SoA then records which Annex A controls support that treatment, why each applies or does not, and its status. So the risk assessment drives the SoA, and the SoA demonstrates that the chosen controls address the identified risks.
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, International Organization for Standardization, 2026
Last updated: 30 August, 2026
