An ISO 27001 Statement of Applicability (SoA) is a formal document that lists all the security controls from Annex A of the ISO 27001 standard, states whether each control applies to your organisation, and explains the reasoning behind every inclusion or exclusion. It is one of the mandatory documents required for ISO 27001 certification and sits at the heart of your information security management system. The sections below answer the most common questions organisations have when building or reviewing their SoA.
What controls does an ISO 27001 Statement of Applicability include?
The ISO 27001 SoA covers all 93 controls listed in Annex A of the ISO 27001:2022 standard, organised across four themes: Organisational controls, People controls, Physical controls, and Technological controls. For each control, the SoA records whether it is applicable, whether it has been implemented, and a brief justification for that decision.
The four control themes break down as follows:
- Organisational controls (37 controls): Policies, roles, supplier relationships, incident management, and business continuity planning.
- People controls (8 controls): Screening, training, disciplinary processes, and responsibilities after employment ends.
- Physical controls (14 controls): Secure areas, equipment protection, clean desk policies, and physical media handling.
- Technological controls (34 controls): Access management, encryption, malware protection, logging, vulnerability management, and secure development.
Beyond the yes/no applicability decision, a well-written SoA also notes the implementation status of each control. This gives auditors and internal stakeholders a live view of where the organisation stands, not just what it intends to do. If you are working toward ISO 27001 certification, building this register early saves significant time later in the process.
Why do some Annex A controls get excluded from the SoA?
Controls are excluded from the SoA when they are genuinely not relevant to the organisation’s context, activities, or risk profile. The standard allows exclusions, but every exclusion must be documented with a clear justification. You cannot simply remove a control because it is inconvenient or costly to implement.
Common legitimate reasons for excluding a control include:
- The control addresses a risk that does not exist in your environment. For example, a fully remote digital company with no physical office may exclude controls related to secure physical areas.
- The activity covered by the control is not part of your business. A company that does not develop software can reasonably exclude secure coding controls.
- Another control already addresses the same risk through a different mechanism, and the overlap is documented.
What is never acceptable is excluding a control simply to reduce workload without a risk-based rationale. Auditors scrutinise exclusions carefully, and unjustified omissions are a common reason for non-conformities during certification audits. The exclusion justification in the SoA must be specific and traceable back to your risk assessment.
How does the SoA connect to the ISO 27001 risk treatment plan?
The SoA and the risk treatment plan are two sides of the same decision. The risk treatment plan identifies the risks your organisation faces and decides how to treat each one. The SoA then confirms which Annex A controls have been selected to address those risks. Together, they form a closed loop: every included control in the SoA should trace back to at least one risk in the treatment plan.
In practice, the process works in this order:
- Complete a risk assessment to identify information security risks.
- Decide how to treat each risk: accept it, avoid it, transfer it, or mitigate it.
- Select the relevant Annex A controls to support your mitigation decisions.
- Record those selections in the SoA, along with their implementation status and justification.
- Document any Annex A controls not selected and explain why they are not applicable.
This traceability is what gives the SoA its value. It is not a standalone checklist. It is the documented evidence that your control selection is driven by actual risk, not by guesswork or a generic template. Auditors will cross-reference the SoA against the risk treatment plan to verify this connection.
Who is responsible for creating and maintaining the SoA?
Responsibility for the SoA typically sits with the person who owns the information security management system, most commonly the Information Security Manager, the CISO, or a designated compliance lead. In smaller organisations without a dedicated security role, this responsibility often falls to a senior manager or the business owner. What matters is that the person responsible has the authority to make risk-based decisions and access to input from across the business.
Creating the SoA is rarely a solo task. The person responsible needs input from department heads to understand which controls are relevant to specific business areas, from IT to assess the technical controls, and from HR and facilities for people and physical controls. In digital companies, the technical and organisational controls tend to dominate, which means close collaboration between the security lead and the IT team is particularly important.
Maintaining the SoA is just as important as creating it. The document should be reviewed at least annually and updated whenever significant changes occur, such as a new product launch, a change in cloud infrastructure, or a new supplier relationship. An outdated SoA that no longer reflects the organisation’s actual control environment is a liability, not an asset.
What do ISO 27001 auditors look for in the SoA?
ISO 27001 auditors use the SoA as a primary reference document during the certification audit. They look for three things above all: completeness, traceability, and honesty. Every Annex A control must appear in the document, every inclusion must be justified, and every exclusion must be supported by a credible, risk-based rationale.
Specifically, auditors will check:
- Coverage: All 93 controls from Annex A are addressed, with no gaps or omissions.
- Justification quality: Inclusion and exclusion reasons are specific and tied to the organisation’s actual risk context, not copied from a generic template.
- Traceability: Included controls link back to identified risks in the risk treatment plan.
- Implementation status: The SoA accurately reflects what has actually been implemented, not just what is planned.
- Version control: The document is dated, version-controlled, and approved by an appropriate authority.
A common finding in first-time audits is an SoA that looks complete on paper but does not match the organisation’s real-world practices. For example, a control is marked as implemented, but no evidence exists to support it. Auditors will request evidence for key controls, so the SoA must reflect reality rather than aspiration.
How DICIS AG helps you build a compliant SoA
Building a Statement of Applicability from scratch is time-consuming, and getting the risk traceability right is where many organisations struggle. We built our platform specifically to remove that friction for small and digital businesses.
When you work with us toward your ISO 27001 certification, we help you:
- Work through all 93 Annex A controls with guided prompts that make the applicability decision straightforward.
- Generate justifications that are specific to your business context, not generic filler text.
- Connect your SoA directly to your risk treatment plan so the traceability auditors look for is built in from the start.
- Maintain and update the document as your business evolves, keeping your certification current.
- Complete the entire process online, with no need for external consultants or lengthy on-site visits.
If you are ready to move forward with your information security management system, explore our ISO 27001 certification process and see how quickly you can get your SoA and the rest of your documentation in order.

