In brief
How to write an ISO 27001 Statement of Applicability: cover all 93 Annex A controls, justify exclusions and keep the SoA consistent with the risk register.
The ISO 27001 Statement of Applicability (SoA) is the mandatory document required by clause 6.1.3 d of ISO/IEC 27001:2022: a table of the necessary controls, why each is included, whether it is implemented, and the justification for excluding any Annex A control. Without an approved SoA a certification audit cannot pass, and it is the document auditors use to trace risks to controls and controls to evidence.
This guide is written for Vietnamese software and IT outsourcing companies preparing their first ISO 27001 audit, and for international clients who ask a vendor for its SoA to see which controls actually cover their data.
What is the SoA and why is it mandatory?
Clause 6.1.3 d requires a Statement of Applicability that contains the necessary controls (from Annex A or other sources), the justification for including them, whether they are implemented, and the justification for excluding any Annex A control. Because exclusions also need a justification, in practice the SoA lists all 93 Annex A controls.
The SoA is mandatory because it shows the organization considered the whole control set rather than picking the easy ones. Auditors use it as a map: from a risk in the risk register, to a control in the SoA, to evidence that the control operates. For clients of an outsourcing vendor, it is also the quickest way to see whether, say, secure development or supplier controls are in scope at all.
Which columns should an SoA have?
Each row is one Annex A control. Typical columns, with three example rows for a cloud-hosted software company:
| Control | Control name | Applicable? | Justification for inclusion or exclusion | Status | Document or evidence reference |
|---|---|---|---|---|---|
| 5.1 | Policies for information security | Yes | Foundational ISMS requirement; client contract requirement | Implemented | Information Security Policy v2.1 |
| 5.18 | Access rights | Yes | Risk R-03: leavers retain access | Implemented | Access review procedure; latest quarterly review record |
| 7.4 | Physical security monitoring | No | No office or physical facility in the ISMS scope; infrastructure runs in the cloud and data centre monitoring is the provider's responsibility (assessed under 5.23) | Not applicable | Cloud provider's certification report |
The justification column is the one auditors read most closely. An inclusion should point to a specific risk, legal requirement or contract; an exclusion should point to the ISMS scope.
How do the 93 Annex A controls usually apply to a software company?
ISO/IEC 27001:2022 Annex A has 93 controls in 4 themes. For a software company, exclusions tend to differ by theme:
- Organizational (5.1–5.37, 37 controls): policies, roles, assets, access, suppliers, incidents, continuity, legal. Almost always fully applicable.
- People (6.1–6.8, 8 controls): screening, employment terms, awareness and training, disciplinary process, responsibilities after termination, confidentiality agreements, remote working, event reporting. Almost always fully applicable, even in very small companies.
- Physical (7.1–7.14, 14 controls): the theme most likely to have exclusions when there is no office or server room in scope. Even then, 7.7 clear desk and clear screen, 7.9 security of assets off-premises and 7.14 secure disposal or re-use of equipment usually still apply to staff laptops.
- Technological (8.1–8.34, 34 controls): endpoints, access, vulnerabilities, logging, networks, cryptography, secure development, backup. Most apply to a software company, and this is the theme that takes the most implementation effort.
Each theme is explained in detail in the ISO 27001 Annex A controls guide.
What exclusion justifications do auditors accept?
An exclusion justification must be tied to scope and context, not to difficulty. Auditors do not accept:
- "Not relevant", which is too vague;
- "Not yet implemented", which is the status of an applicable control, not a reason to exclude it;
- a blank cell.
Examples of justifications that are commonly accepted:
- "No office or physical facility within the ISMS scope", to exclude some secure-area controls such as 7.1–7.4;
- "No software development within the ISMS scope", to exclude development controls such as 8.25–8.29;
- "Software development is not outsourced", to exclude 8.30 Outsourced development.
If a control is excluded but a risk in the register depends on it, that is a contradiction the auditor will find. An IT outsourcing company that builds software for clients will rarely be able to exclude 8.25–8.29.
How does the SoA link to the risk register?
The SoA does not stand alone. Auditors check consistency in two directions:
- Risk to control. Any control used to treat a risk must be marked applicable in the SoA. If the register treats "unauthorized access to production" with 8.2 Privileged access rights while the SoA marks 8.2 as not applicable, that is a contradiction.
- Control to evidence. Any control marked "implemented" needs evidence that it operates. An SoA claiming 8.15 Logging is implemented, with no logs collected or reviewed, is an unsupported statement.
How to build the register so both directions line up is covered in the ISO 27001 risk register example, and the method behind it in the ISO 27001 risk assessment guide.
What are the most common SoA mistakes?
- Marking every control applicable "to be safe". Every applicable control needs evidence; over-marking means over-proving.
- No document references. "We have a policy" without the document name and version gives the auditor nothing to check.
- An unapproved SoA. Clause 7.5 requires documented information to be reviewed and approved for suitability and adequacy; the SoA should be approved by someone with authority, such as the CEO or the person responsible for security.
- No version control. Several SoA copies with no clear current version make the auditor question document control as a whole.
- No update after change. When scope, risks or controls change, the SoA must change with them; an SoA untouched for two years rarely reflects reality.
How do you write the SoA step by step?
- Finish risk assessment and risk treatment first, so you know which controls each risk needs.
- Use the list of 93 Annex A controls as the frame.
- For each control, decide applicable or excluded based on scope, risks, legal and contractual requirements, not on how hard it is.
- For applicable controls, record implementation status and the document or evidence reference.
- Review the whole SoA with someone who understands both the technical and the business side.
- Approve it formally, give it a version number and set a review date.
How long the SoA takes depends mostly on whether the risk register and policies are complete. If they are not, start with the ISO 27001 implementation checklist for IT outsourcing companies.
Spreadsheet or software for the SoA?
As far as the standard is concerned, the SoA can be an Excel file. The practical difficulty is keeping it consistent with the register and the evidence: when the auditor asks "show me the evidence for control 8.15", finding the right file across many folders takes time.
In pTrackly, the ISO 27001:2022 framework comes with controls, policy templates and evidence tasks, including a dedicated evidence task for the Statement of Applicability so the SoA gets an owner and a review schedule like any other evidence. Controls are shared across frameworks, and treatment actions in the risk register can carry a control reference such as "ISO 27001 A.5.17". Applicability decisions, the justifications in the SoA and its approval stay with your team; the certification body does the assessment. See pTrackly for ISO 27001.
Frequently asked questions
Does the SoA have to list all 93 Annex A controls?
In practice, yes. Clause 6.1.3 d requires a justification for every excluded Annex A control, so the SoA must address all 93, plus any additional controls you use beyond Annex A.
Can you exclude the entire physical controls theme?
Rarely. A company with no office in scope can exclude some secure-area controls, but clear desk and clear screen (7.7), assets off-premises (7.9) and secure disposal or re-use of equipment (7.14) usually still apply to staff devices.
Is "applicable but not yet implemented" acceptable?
Yes, if that is the true status and a risk treatment plan with a due date covers it. A control needed for a high risk that is still not implemented at the Stage 2 audit may, however, lead to a nonconformity.
How often should the SoA be updated?
Whenever the ISMS scope, the risk assessment results or the controls change, and at least at each periodic risk review. Each update needs a new version and a new approval.
References:
- ISO/IEC 27001:2022, Information security management systems (iso.org/standard/82875.html)
- ISO/IEC 27002:2022, Information security controls (iso.org/standard/75652.html)