Frameworks

What is a Statement of Applicability in ISO 27001?

Direct answer

The Statement of Applicability (SoA) is a mandatory document in ISO 27001 that lists all Annex A controls, states whether each is applicable or not applicable to the organisation's ISMS scope, provides justification for exclusions, and references the implementation status of each applicable control.

The SoA is a key audit artefact: auditors use it to verify that control selection is risk-based and that excluded controls have documented rationale.

Where does the Statement of Applicability come from?

The SoA is an output of risk treatment, not a standalone checklist. Clause 6.1.3 of ISO/IEC 27001:2022 sets the sequence:

  • Choose a treatment option for each risk found in the risk assessment.
  • Determine all the controls needed to carry out that treatment. They can be designed in-house or taken from any source.
  • Compare those controls with Annex A to check that no necessary control has been left out.
  • Produce the Statement of Applicability (clause 6.1.3 d).
  • Formulate the risk treatment plan (clause 6.1.3 e) and obtain the risk owners’ approval of the plan and their acceptance of the residual risks (clause 6.1.3 f).

Because of that sequence, auditors read the SoA next to the risk assessment and the risk treatment plan. A control marked applicable should trace back to a risk, a legal requirement or a contractual obligation.

What must the Statement of Applicability contain?

The 2022 edition asks for four things: the necessary controls, the justification for including them, whether each one is implemented, and the justification for excluding any Annex A control.

In practice most SoAs are a table with one row per control and these columns:

  • The control reference and name, for all 93 Annex A controls plus any controls you added from other sources.
  • Applicable or excluded.
  • The reason: risk treatment result, legal requirement, contractual obligation, or the rationale for exclusion.
  • Implementation status.
  • A reference to where the control lives: a policy, a procedure, a system or a record.

The SoA is one of the documents the standard names explicitly. The full list is in Which documents does ISO 27001 require?.

How do you keep a Statement of Applicability current?

The SoA is the primary document a Stage 1 auditor reviews before the on-site audit, and Stage 2 then tests whether the controls it lists actually operate. It is not a one-time deliverable. Keep it under version control, with approval dates, and update it whenever the ISMS scope changes, the risk assessment finds new risks, or a control changes status. Auditors look for that version history at surveillance audits.

Since certification bodies completed the move to ISO/IEC 27001:2022 by 31 October 2025, the SoA should use the 2022 Annex A structure: 93 controls in four themes, not the 114 controls of the 2013 edition.

What mistakes do auditors find in a Statement of Applicability?

  • Excluding controls without a documented, risk-based justification.
  • Listing controls as applicable with no evidence that they are implemented.
  • An SoA that does not match the risk assessment, often because it was copied from a template.
  • No update after the scope, the risks or the controls changed.
  • Control references still numbered to the 2013 edition.

An exclusion is not a nonconformity in itself; an unjustified exclusion is.

How Acuna GRC handles it

In Acuna GRC, you tick the requirements that apply in the Comply workspace and mark any that do not as Not applicable, with a justification, in Implement; each applicable requirement carries its compliance status, maturity and linked measures and controls.

Sources

  1. ISO/IEC 27001:2022, clause 6.1.3 and Annex A
  2. UKAS, transition arrangements for ISO/IEC 27001:2022

This page explains the rules in general terms and is not legal advice.

Frequently asked

Can you exclude Annex A controls?

Yes, if you justify the exclusion, for example because the control addresses a risk outside your scope. What you cannot exclude are the requirements of clauses 4 to 10.

Is the Statement of Applicability the same as the risk treatment plan?

No. The SoA records which controls apply and why. The risk treatment plan, required by clause 6.1.3 e, sets out how the risks will be treated. ISO 27001 requires both, and they should agree.

How often should the Statement of Applicability be updated?

The standard sets no fixed frequency. Update it whenever scope, risks or controls change, and keep the version history, because auditors check it at each surveillance audit.

See how Acuna GRC runs this.

Tell us your frameworks and your team. We show you how Acuna GRC runs the program.

Hosted in Switzerland, the EU or the US