ISO 27001 Statement of Applicability template, all 93 controls.
Every ISO/IEC 27001:2022 Annex A control, by number and title in its four themes, with the columns clause 6.1.3(d) asks for. Copy it into a spreadsheet and fill it from your risk assessment.
What does a Statement of Applicability have to contain?
Under ISO/IEC 27001:2022 clause 6.1.3(d), the Statement of Applicability must contain the necessary controls, the justification for including them, whether they are implemented, and the justification for excluding any Annex A control. Every one of the 93 Annex A controls has to appear, included or not.
The SoA is not a checklist to complete for its own sake. It comes after the risk assessment: you decide how to treat each risk, choose the controls, then compare them with Annex A to confirm nothing necessary was missed. That order is why the template has a “Linked risks” column. The standard itself is available from ISO; Annex A titles below follow the 2022 edition, which the 2024 amendment on climate change did not alter.
How to use this template
- Do the risk assessment first. Use the risk register template, then mark each control applicable where it treats a risk, meets a legal or contractual requirement, or supports the ISMS itself.
- Write a real justification for every row. Inclusion: the risk or requirement it answers. Exclusion: why the risk does not arise in your scope.
- Record implementation status honestly. Partial is a valid answer, with the plan in your risk treatment plan.
- Point at evidence. The implementation column should name the policy, configuration or record an auditor can inspect.
- Version it. The SoA is a controlled document; auditors will ask which version was current on a given date.
The template (all 93 controls, tab-separated)
Paste into cell A1 of a blank sheet. The first two columns are filled; the rest are yours.
Control Title Applicable (Yes/No) Justification for inclusion or exclusion Implemented (Yes/Partial/No) How it is implemented / evidence reference Owner Linked risks A.5.1 Policies for information security A.5.2 Information security roles and responsibilities A.5.3 Segregation of duties A.5.4 Management responsibilities A.5.5 Contact with authorities A.5.6 Contact with special interest groups A.5.7 Threat intelligence A.5.8 Information security in project management A.5.9 Inventory of information and other associated assets A.5.10 Acceptable use of information and other associated assets A.5.11 Return of assets A.5.12 Classification of information A.5.13 Labelling of information A.5.14 Information transfer A.5.15 Access control A.5.16 Identity management A.5.17 Authentication information A.5.18 Access rights A.5.19 Information security in supplier relationships A.5.20 Addressing information security within supplier agreements A.5.21 Managing information security in the ICT supply chain A.5.22 Monitoring, review and change management of supplier services A.5.23 Information security for use of cloud services A.5.24 Information security incident management planning and preparation A.5.25 Assessment and decision on information security events A.5.26 Response to information security incidents A.5.27 Learning from information security incidents A.5.28 Collection of evidence A.5.29 Information security during disruption A.5.30 ICT readiness for business continuity A.5.31 Legal, statutory, regulatory and contractual requirements A.5.32 Intellectual property rights A.5.33 Protection of records A.5.34 Privacy and protection of PII A.5.35 Independent review of information security A.5.36 Compliance with policies, rules and standards for information security A.5.37 Documented operating procedures A.6.1 Screening A.6.2 Terms and conditions of employment A.6.3 Information security awareness, education and training A.6.4 Disciplinary process A.6.5 Responsibilities after termination or change of employment A.6.6 Confidentiality or non-disclosure agreements A.6.7 Remote working A.6.8 Information security event reporting A.7.1 Physical security perimeters A.7.2 Physical entry A.7.3 Securing offices, rooms and facilities A.7.4 Physical security monitoring A.7.5 Protecting against physical and environmental threats A.7.6 Working in secure areas A.7.7 Clear desk and clear screen A.7.8 Equipment siting and protection A.7.9 Security of assets off-premises A.7.10 Storage media A.7.11 Supporting utilities A.7.12 Cabling security A.7.13 Equipment maintenance A.7.14 Secure disposal or re-use of equipment A.8.1 User end point devices A.8.2 Privileged access rights A.8.3 Information access restriction A.8.4 Access to source code A.8.5 Secure authentication A.8.6 Capacity management A.8.7 Protection against malware A.8.8 Management of technical vulnerabilities A.8.9 Configuration management A.8.10 Information deletion A.8.11 Data masking A.8.12 Data leakage prevention A.8.13 Information backup A.8.14 Redundancy of information processing facilities A.8.15 Logging A.8.16 Monitoring activities A.8.17 Clock synchronization A.8.18 Use of privileged utility programs A.8.19 Installation of software on operational systems A.8.20 Networks security A.8.21 Security of network services A.8.22 Segregation of networks A.8.23 Web filtering A.8.24 Use of cryptography A.8.25 Secure development life cycle A.8.26 Application security requirements A.8.27 Secure system architecture and engineering principles A.8.28 Secure coding A.8.29 Security testing in development and acceptance A.8.30 Outsourced development A.8.31 Separation of development, test and production environments A.8.32 Change management A.8.33 Test information A.8.34 Protection of information systems during audit testing
ISO 27001:2022 Annex A controls by theme
The same 93 controls, grouped as the standard groups them. The eleven controls new in the 2022 edition are marked.
Organisational controls (5.1–5.37)
| Control | Title | Applicable | Justification | Implemented |
|---|---|---|---|---|
| 5.1 | Policies for information security | |||
| 5.2 | Information security roles and responsibilities | |||
| 5.3 | Segregation of duties | |||
| 5.4 | Management responsibilities | |||
| 5.5 | Contact with authorities | |||
| 5.6 | Contact with special interest groups | |||
| 5.7 new in 2022 | Threat intelligence | |||
| 5.8 | Information security in project management | |||
| 5.9 | Inventory of information and other associated assets | |||
| 5.10 | Acceptable use of information and other associated assets | |||
| 5.11 | Return of assets | |||
| 5.12 | Classification of information | |||
| 5.13 | Labelling of information | |||
| 5.14 | Information transfer | |||
| 5.15 | Access control | |||
| 5.16 | Identity management | |||
| 5.17 | Authentication information | |||
| 5.18 | Access rights | |||
| 5.19 | Information security in supplier relationships | |||
| 5.20 | Addressing information security within supplier agreements | |||
| 5.21 | Managing information security in the ICT supply chain | |||
| 5.22 | Monitoring, review and change management of supplier services | |||
| 5.23 new in 2022 | Information security for use of cloud services | |||
| 5.24 | Information security incident management planning and preparation | |||
| 5.25 | Assessment and decision on information security events | |||
| 5.26 | Response to information security incidents | |||
| 5.27 | Learning from information security incidents | |||
| 5.28 | Collection of evidence | |||
| 5.29 | Information security during disruption | |||
| 5.30 new in 2022 | ICT readiness for business continuity | |||
| 5.31 | Legal, statutory, regulatory and contractual requirements | |||
| 5.32 | Intellectual property rights | |||
| 5.33 | Protection of records | |||
| 5.34 | Privacy and protection of PII | |||
| 5.35 | Independent review of information security | |||
| 5.36 | Compliance with policies, rules and standards for information security | |||
| 5.37 | Documented operating procedures |
People controls (6.1–6.8)
| Control | Title | Applicable | Justification | Implemented |
|---|---|---|---|---|
| 6.1 | Screening | |||
| 6.2 | Terms and conditions of employment | |||
| 6.3 | Information security awareness, education and training | |||
| 6.4 | Disciplinary process | |||
| 6.5 | Responsibilities after termination or change of employment | |||
| 6.6 | Confidentiality or non-disclosure agreements | |||
| 6.7 | Remote working | |||
| 6.8 | Information security event reporting |
Physical controls (7.1–7.14)
| Control | Title | Applicable | Justification | Implemented |
|---|---|---|---|---|
| 7.1 | Physical security perimeters | |||
| 7.2 | Physical entry | |||
| 7.3 | Securing offices, rooms and facilities | |||
| 7.4 new in 2022 | Physical security monitoring | |||
| 7.5 | Protecting against physical and environmental threats | |||
| 7.6 | Working in secure areas | |||
| 7.7 | Clear desk and clear screen | |||
| 7.8 | Equipment siting and protection | |||
| 7.9 | Security of assets off-premises | |||
| 7.10 | Storage media | |||
| 7.11 | Supporting utilities | |||
| 7.12 | Cabling security | |||
| 7.13 | Equipment maintenance | |||
| 7.14 | Secure disposal or re-use of equipment |
Technological controls (8.1–8.34)
| Control | Title | Applicable | Justification | Implemented |
|---|---|---|---|---|
| 8.1 | User end point devices | |||
| 8.2 | Privileged access rights | |||
| 8.3 | Information access restriction | |||
| 8.4 | Access to source code | |||
| 8.5 | Secure authentication | |||
| 8.6 | Capacity management | |||
| 8.7 | Protection against malware | |||
| 8.8 | Management of technical vulnerabilities | |||
| 8.9 new in 2022 | Configuration management | |||
| 8.10 new in 2022 | Information deletion | |||
| 8.11 new in 2022 | Data masking | |||
| 8.12 new in 2022 | Data leakage prevention | |||
| 8.13 | Information backup | |||
| 8.14 | Redundancy of information processing facilities | |||
| 8.15 | Logging | |||
| 8.16 new in 2022 | Monitoring activities | |||
| 8.17 | Clock synchronization | |||
| 8.18 | Use of privileged utility programs | |||
| 8.19 | Installation of software on operational systems | |||
| 8.20 | Networks security | |||
| 8.21 | Security of network services | |||
| 8.22 | Segregation of networks | |||
| 8.23 new in 2022 | Web filtering | |||
| 8.24 | Use of cryptography | |||
| 8.25 | Secure development life cycle | |||
| 8.26 | Application security requirements | |||
| 8.27 | Secure system architecture and engineering principles | |||
| 8.28 new in 2022 | Secure coding | |||
| 8.29 | Security testing in development and acceptance | |||
| 8.30 | Outsourced development | |||
| 8.31 | Separation of development, test and production environments | |||
| 8.32 | Change management | |||
| 8.33 | Test information | |||
| 8.34 | Protection of information systems during audit testing |
What do auditors check in the Statement of Applicability?
Auditors check that every Annex A control appears, that each inclusion and exclusion has a justification traceable to the risk assessment or a requirement, that implementation status matches what they find, and that the SoA version agrees with the risk treatment plan. Mismatches between the three documents are the commonest finding.
Keeping the SoA, risk register and evidence consistent by hand is where most of the effort in an ISMS goes. The ISO 27001 solution holds the controls once on a shared library, attaches evidence as it is collected, and uses cross-framework mapping to carry the same control results to SOC 2 and the DPDP Act. The coverage page lists every regime mapped.
More free templates: the full template library, including a 5×5 risk register, a record of processing activities, a vendor security questionnaire and a DPDP consent notice.
The things people ask us
What is a Statement of Applicability in ISO 27001?
A Statement of Applicability (SoA) is the document ISO/IEC 27001 clause 6.1.3(d) requires, listing the controls you need to treat your information security risks, why each is included, whether it is implemented, and why any Annex A control is excluded. Certification auditors use it as the map of your ISMS.
How many controls are in ISO 27001:2022 Annex A?
93, in four themes: 37 organisational controls (5.1 to 5.37), 8 people controls (6.1 to 6.8), 14 physical controls (7.1 to 7.14) and 34 technological controls (8.1 to 8.34). The 2013 edition had 114 controls in 14 domains. The 2022 edition merged many of them and added 11 new ones.
Can we exclude Annex A controls?
Yes, if you justify the exclusion. The standard requires the justification to be recorded in the SoA. A sound exclusion follows from your risk assessment and scope, for example 7.12 cabling security for a fully remote company with no premises in scope. 'Not relevant' with no reason is the answer auditors challenge.
Which controls were new in ISO 27001:2022?
Eleven: 5.7 threat intelligence, 5.23 information security for use of cloud services, 5.30 ICT readiness for business continuity, 7.4 physical security monitoring, 8.9 configuration management, 8.10 information deletion, 8.11 data masking, 8.12 data leakage prevention, 8.16 monitoring activities, 8.23 web filtering and 8.28 secure coding.
Does the Statement of Applicability have to use Annex A?
You compare your necessary controls against Annex A to check nothing has been overlooked, and the SoA must cover every Annex A control, included or excluded. You may also add controls from other sources, such as ISO/IEC 27017 for cloud or ISO/IEC 27701 for privacy, and they belong in the same document.
How does the SoA relate to the risk register?
They are two views of the same decisions. The risk register records each risk and the controls chosen to treat it; the SoA lists each control and the risks or requirements that justify it. The 'Linked risks' column in this template makes the connection explicit, which is the first thing an auditor traces.
See your Statement of Applicability fill itself.
We connect one cloud account live and show Annex A controls picking up evidence and status before the call ends.