Glossary · Information security
What is a Statement of Applicability?
The document in an ISO/IEC 27001 information security management system that lists the reference controls, states which are included and which are excluded, and justifies each decision. It shows how the organisation has chosen to treat its information security risks, and auditors read it first.
Prepared by the Sterling expert panel · How our courses are made
Why does Statement of Applicability matter at work?
The Statement of Applicability is one of the first documents a certification body auditor asks for, because it connects the risk assessment to the controls the organisation actually operates. If a control is marked as included but no one can show it working, or excluded without a sound reason, the auditor will raise a finding.
It also helps the organisation itself. A clear Statement of Applicability tells managers which controls they own, gives internal auditors a map of what to test, and makes it easy to show clients and regulators how information is protected.
What does it contain?
- Every reference control the standard lists, with a decision: included or excluded
- The justification for including each control, usually linked to a risk or a legal, contractual or business requirement
- The justification for excluding each control
- Whether each included control is already in place or still being put in place
- A version, an owner and an approval date, so it can be controlled like any other document
What mistakes do auditors find most often?
- Copying a template without linking each decision to the organisation's own risks
- Excluding a control because it is inconvenient rather than because it does not apply
- Leaving the Statement of Applicability unchanged after the risk assessment, the scope or the systems change
- Marking controls as in place with no evidence behind them
Frequently asked questions
Questions about Statement of Applicability
Is the Statement of Applicability mandatory?
Yes, for an information security management system certified to ISO/IEC 27001. The standard requires the organisation to produce one as part of its risk treatment.
How often should the Statement of Applicability be updated?
Whenever the risk assessment, the scope or the controls change, and at least whenever the risk assessment is reviewed. Each version should be approved and kept.
Can a control be excluded?
Yes, if it does not apply to the organisation's risks or requirements, and the reason is recorded. An auditor will test whether the reason holds.
Who should own the Statement of Applicability?
Usually the information security manager or the person leading the management system, with approval by top management, because it records how the organisation has chosen to treat its risks.
Related terms