Statement of Applicability (SoA)
You'll learn how to create and maintain the formal SoA document that justifies every control decision in your ISO 27001 ISMS.
What Is the Statement of Applicability?
After performing Risk Assessment and Treatment (Clause 6) and selecting controls from Annex A, you must document why each of the 93 Annex A controls is included, excluded, or partially implemented. The Statement of Applicability (SoA) is this formal, auditable record.
Think of the SoA as your ISMS's "control manifest" — a complete inventory with justifications. If Annex A is a menu of security controls, your SoA is your order slip showing what you chose, what you declined, and why.
Core Components of the SoA
Each control entry in your SoA must include:
- Control reference (e.g., A.5.1 "Information security policies")
- Inclusion decision (included, excluded, or not applicable)
- Justification — Why is it included/excluded based on your specific risk assessment?
- Implementation status (planned, partially implemented, fully implemented)
- Owner/responsible party
Creating and Maintaining the SoA
Start with all 93 Annex A controls. For each:
- If included: Link to risk treatment decisions and describe implementation approach
- If excluded: Provide clear, risk-based justification (e.g., "A.8.21 security of network services — excluded because we operate no on-premises network infrastructure; all services cloud-hosted")
- Document implementation status honestly — auditors will verify
The SoA is a living document. Update it when risks change, new controls are deployed, or business context shifts. Version control is essential.
Key Takeaway: The Statement of Applicability transforms your Annex A control selection into a traceable, justifiable compliance record that demonstrates due diligence and supports audit evidence collection.