ISO Standards

ISO 27001 Statement of Applicability Explained

ISO 27001 Statement of Applicability Explained
In short

The ISO 27001 statement of applicability, or SoA, is a mandatory document that lists the Annex A controls, says whether each one applies, gives the reason, and states whether it is implemented. You build it from your risk assessment and treatment plan. Auditors use it as a map of your system, so it must match what you really do.

In this article
  1. What does the ISO 27001 statement of applicability contain?
  2. How do you build the statement of applicability step by step?
  3. How should you justify exclusions?
  4. What mistakes do auditors find in the SoA?
  5. Frequently asked questions

The ISO 27001 statement of applicability, usually called the SoA, is one of the most important documents in your system. Auditors read it early, and they use it as a map of what to test. Getting it right makes the audit smoother. Getting it wrong, for example by copying a list without thought, leads to findings.

ISO/IEC 27001:2022 requires the SoA as part of risk treatment. It brings together your risk assessment, the controls you have chosen and your reasons. This article explains what goes in it, how to build it and how to avoid the usual mistakes.

What does the ISO 27001 statement of applicability contain?#

The standard asks the SoA to contain the necessary controls, the justification for including them, whether they are implemented, and the justification for excluding any Annex A control. In practice, most SoAs are a table with one row per control. Check the exact wording in your copy of the standard.

ColumnWhat to write
ControlThe Annex A control number and name
Applicable?Yes or no for your scope
JustificationThe reason: a risk, a legal duty, a contract or good practice, or why it is excluded
Implemented?Implemented, partly implemented or planned
ReferenceThe policy, procedure or record that shows how you meet the control

The 2022 edition has 93 controls in four themes: organisational, people, physical and technological. The SoA should consider all of them, even if many are marked as not applicable.

Think of the SoA as the bridge between your risk work and your daily controls. The risk assessment says what could go wrong. The controls say what you do about it. The SoA ties the two together, so an auditor can follow a single line from a risk to a control to the evidence. If that line breaks anywhere, expect questions.

How do you build the statement of applicability step by step?#

  1. Finish your risk assessment and decide how each risk will be treated.
  2. Determine the controls needed to carry out that treatment, from Annex A or from other sources.
  3. Compare your list with Annex A to check that no necessary control was missed.
  4. Mark each Annex A control as applicable or not, with a short reason.
  5. Record the implementation status, and link applied controls to their documents or records.
  6. Have the risk owners approve the treatment plan and accept any residual risk.
  7. Get management approval and put the SoA under version control.

The order matters. The SoA comes from the risk assessment, not the other way round. If you fill it before assessing risk, you may end up with controls that do not match your real threats.

Be careful with the word implemented. It should mean the control is working and you have records to show it. If a control is only written on paper, call it partly implemented or planned, and say when it will be done. Auditors respond far better to an honest status and a dated plan than to an overstated claim that they can disprove in five minutes.

How should you justify exclusions?#

You may exclude a control if it is not needed in your scope, but you must say why. A good reason links to your context: for example, a company with no software development in scope can explain that a secure coding control does not apply. A poor reason is just "not required" with no explanation.

  • Link the reason to your scope, your risks or a legal or contract duty.
  • Keep the wording short and factual.
  • Revisit exclusions when your scope or business changes.
  • Do not exclude a control only because it is hard or costly.

Exclusions deserve a second look at each review. A company that did not use cloud services last year may use them now, and a control that was excluded may become necessary. Record the date and the person who reviewed each exclusion, so the history is clear.

What mistakes do auditors find in the SoA?#

  • Marking everything as implemented when evidence is missing.
  • Copying a template without checking the controls against the risk assessment.
  • Giving no justification, or the same sentence for every row.
  • Using the old 2013 control list instead of the 2022 Annex A.
  • Failing to update the SoA after a scope or risk change.
  • No link between the SoA and the policies or records behind each control.

The old control list point is worth checking. If your SoA still follows the 2013 edition, it must be moved to the 2022 structure. Read our complete guide to ISO 27001 for the wider picture.

Our ISO 27001 toolkit offers an editable SoA template alongside other documents, with one year of e-mail support and a free upgrade within 6 months. Use it as a starting point, then adapt every row to your own risks. If you would like an expert to review your SoA, see our ISO 27001 consulting in India. No one can promise an audit result, because the certification body decides.

Finally, keep the SoA readable. Many teams build a very large spreadsheet that only one person understands. Use clear columns, consistent wording and a short note at the top that explains how to read it. Share it with control owners, so each one can confirm the status of their own rows before the audit. A shared, accurate SoA makes the Stage 1 review quicker and gives the auditor confidence in the rest of your system.

Frequently asked questions#

Is the statement of applicability mandatory?#

Yes. It is a required document in ISO/IEC 27001. Certification bodies ask for it at the Stage 1 audit.

How often should we update it?#

Update it whenever your scope, risks or controls change, and review it at least once a year, for example at the management review.

Can we add controls that are not in Annex A?#

Yes. If your risk treatment needs a control from another source, add it to the SoA and record why. The Annex A list is a check, not a limit.

Need help with yours? Contact AdWiser and we will talk through your scope.

Found this useful?

Share it with your network, and follow AdWiser Enterprise Consulting on LinkedIn for more certification guides and compliance tips.

Share:

Leave a Comment

Comments are reviewed before they appear. Please keep them relevant and leave out web links.

Ready to put this into practice?

Start with the ISO 27001:2022 Toolkit and adapt it to your organisation, or talk to us about implementation support.

Chat on WhatsApp