Skip to main content
Talk to a human
AI Assistant

ISO 27001 Statement of Applicability: What It Must Contain, with an Example

The Statement of Applicability (SoA) is the ISO 27001 document that lists every Annex A control, says whether it applies to your organisation and why, and records whether it is implemented. It is mandatory under clause 6.1.3(d) of ISO/IEC 27001:2022, and it is usually the first document a certification auditor reads, because it tells them which controls to test.

At a glance

  • Required by: clause 6.1.3(d), information security risk treatment
  • Covers: all 93 Annex A controls (37 organisational, 8 people, 14 physical, 34 technological), plus any controls of your own
  • Must state for each control: whether it is included and why, whether it is implemented, and why any Annex A control is excluded
  • Must agree with: your risk assessment and risk treatment plan
  • Where it goes wrong: controls marked implemented with no evidence, and exclusions that do not hold up

What the standard requires

Clause 6.1.3(d) is short. The Statement of Applicability must contain:

That last point is the one people miss. Annex A is a checklist you must compare your controls against, so all 93 controls appear in the SoA, even the ones that do not apply to you.

The columns a usable SoA has

The standard does not prescribe a format. A spreadsheet with one row per control is the most common, and the columns below are what auditors and the people running the ISMS both find useful:

Column What goes in it
Control reference and nameThe Annex A number and title, for example 5.15 Access control
ApplicableIncluded or excluded
ReasonWhy it is included (the risk it treats, or the legal or contractual requirement) or why it is excluded
Implementation statusImplemented, partially implemented or not yet implemented
How it is implementedA short description of what you actually do, with a reference to the policy or procedure
EvidenceWhere the records are that prove it, for example access review logs or backup reports
OwnerThe person responsible for the control

Only the first four are strictly required. The last three are what make the SoA useful in practice, because they turn it into the map your team works from when the auditor asks for evidence.

A worked example

The rows below are an illustrative example for a fictional 25-person Singapore company that runs a customer-facing web application on a cloud platform, works from one office and on laptops, and builds its software in-house.

Control Applicable Reason Status How it is implemented
5.15 Access control Included Risk R-04: former staff keeping access to customer data Implemented Access granted by role in the identity provider; HR offboarding checklist removes access on the last day; quarterly review by the CTO (Access Control Policy v1.2)
5.23 Information security for use of cloud services Included Risk R-07: misconfigured cloud storage; customer contracts require it Partially implemented Approved cloud services list exists; configuration baseline for the production account due by Q1
6.3 Information security awareness, education and training Included Risk R-02: phishing leading to account takeover Implemented Induction briefing for new joiners and an annual refresher; attendance recorded by HR
8.13 Information backup Included Risk R-09: loss of the production database Implemented Daily automated database backups kept for 35 days; restore tested every six months and the result recorded
8.30 Outsourced development Excluded All software is developed in-house by employees; no development is outsourced N/A Revisit if a contractor or agency is engaged to write code

Notice what makes these rows credible. Each included control points to a specific risk or requirement, the implementation describes what this company really does, and the one partially implemented control is marked honestly, with a date. The exclusion is justified by the absence of the activity, not by convenience.

How to fill it in from how you actually work

  1. Start from the risk assessment, not from Annex A. Decide how to treat each risk first, then compare the controls you chose against Annex A to check nothing is missing. That is the order clause 6.1.3 sets out.
  2. For each control, describe what you do today. Ask the person who does the work, not the person writing the document. If nobody does it, the status is not “implemented”.
  3. Mark partial implementation honestly. An auditor will accept a control that is partially implemented with a plan and a date. They will not accept one marked implemented that turns out not to be.
  4. Justify exclusions by the absence of the activity. “We do not do X” is a justification. “X is not a priority” is not.
  5. Point every implemented control at its evidence. If you cannot say where the records are, you have found a gap before the auditor does.
  6. Give every control an owner. Controls without owners are the ones that stop running between audits.

Why template SoAs fail the Stage 2 audit

A pre-filled Statement of Applicability from a template pack looks complete, which is exactly the problem. The Stage 1 audit checks that the document exists. The Stage 2 audit checks that what it says is true, and these are the findings that come from template SoAs:

The fix is not a better template. It is an SoA written from how your business actually operates, with gaps marked honestly and evidence named for every implemented control. That is what lets an auditor confirm it rather than question it.

How the SoA fits with the other ISMS documents

Keeping it current

The SoA is a controlled document, not a one-off. Update it when you add a system, supplier, office or service, when a risk changes, and when a partially implemented control is finished. Review it at each management review. The certification body will look at it again at every surveillance audit, and a version history showing it has been maintained is good evidence that the ISMS is actually running.

Want your SoA written from how you actually work?

We map how your business operates, assess it against all 93 Annex A controls, and write the Statement of Applicability, risk treatment plan and policies around your real practice. Part of our ISO 27001 readiness work, from S$13,500.

Get an ISO 27001 Quote

Frequently asked questions

Is the Statement of Applicability mandatory for ISO 27001?

Yes. Clause 6.1.3(d) of ISO/IEC 27001:2022 requires every organisation seeking certification to produce a Statement of Applicability. It must list the necessary controls, the justification for including them, whether they are implemented, and the justification for excluding any Annex A control.

How many controls are in the ISO 27001:2022 Statement of Applicability?

Annex A of ISO/IEC 27001:2022 has 93 controls in four themes: 37 organisational, 8 people, 14 physical and 34 technological. Every one of them must appear in the Statement of Applicability, either included with a justification or excluded with a justification. You can also add controls of your own that are not in Annex A.

Can you exclude Annex A controls from the Statement of Applicability?

Yes, if the exclusion is justified. A good justification says the activity the control addresses does not happen inside your scope, for example excluding 8.30 Outsourced development because you do not outsource any software development. Exclusions that simply avoid work, such as dropping physical security because your systems are in the cloud while staff still work on laptops, are a common audit finding.

Do we have to implement all 93 Annex A controls?

No. You implement the controls your risk assessment shows are necessary, and justify excluding the rest. What you cannot do is leave a control out of the Statement of Applicability altogether: every Annex A control must be addressed, either included or excluded with a reason.

What is the difference between the Statement of Applicability and the risk treatment plan?

The risk treatment plan says how each risk will be treated and which controls address it. The Statement of Applicability lists every Annex A control and states whether it applies and whether it is implemented. They must agree: a control your risk treatment plan relies on has to appear in the Statement of Applicability as included, and an auditor will check that they match.

Useful resources

Disclaimer: This article is for general information only. The worked example is illustrative and describes a fictional company; your Statement of Applicability must reflect your own scope, risks and controls. Refer to ISO/IEC 27001:2022 for the authoritative requirements.