IMScollect
ISO 27001

ISO 27001, clause 6.1.3 d: Statement of Applicability (SoA)

Title in the standard: “Statement of Applicability”

Which Annex A controls do you need, why, and how far are they implemented? The Statement of Applicability under ISO/IEC 27001 from the audit’s point of view.

Philipp Kappe

Philipp Kappe

Founder of IMScollect

Updated 15 November 2026

What it is about

The Statement of Applicability, SoA for short, is one of the documents ISO/IEC 27001 explicitly requires. It is produced during risk treatment: once the risks have been assessed, the organisation determines which controls it needs to treat them and compares this selection with the catalogue in Annex A, so that no necessary control is overlooked.

The statement records the result: which controls are necessary and why they were included, whether they are implemented, and for every Annex A control that is not needed, the justification for its exclusion. Reasons for inclusion are usually a risk, a legal or contractual obligation or a decision of the organisation’s own. Anyone who also uses controls from other sources, such as an industry standard, includes them as well; Annex A is not exhaustive.

This makes the statement the bridge between the risk assessment, the risk treatment plan and day-to-day operations. Together with the scope, it is one of the documents almost every ISO 27001 audit starts with, and it has to match the current state of the risks. When the risk assessment changes, the statement is reviewed with it.

What the auditor checks

  • “Why have you excluded this control?”

    Whether the justification comes from your own scope or your own risks. “Not relevant” does not hold up; “no in-house software development, software is only bought in” does, if it is true. The auditor checks such statements against the site tour and the interviews.

  • “Where is this control implemented?”

    The trail from the row into practice: a policy with its version, a configuration, a log, a conversation with the person responsible. “Implemented” without evidence that can be shown is an assertion.

  • “Which risk does this control treat?”

    The link to the risk assessment and the treatment plan. A control backed by neither a risk nor an obligation nor a decision is on the list without a reason; a high risk with no control assigned to it stands out just as much.

  • “Which version applies, and who approved it?”

    Control as with any document: version, date and approval. The statement the auditor is given and the one on the intranet should be the same.

  • “What has changed in the statement since the last risk assessment?”

    Whether the two are maintained together. A new cloud service, a new site or a security incident should leave traces in the risk assessment and in the statement. A statement dated at initial certification next to a fresh risk assessment tells the opposite story.

Which evidence convinces

  • The statement itself, complete across all Annex A controls

    For each row: applicability, reason for inclusion or justification for exclusion, implementation status and owner. Complete means no Annex A control is missing, not even an excluded one.

  • The risk treatment plan approved by the risk owners

    It shows which controls treat which risks, what will be implemented by when, and that the risk owners have approved the plan and accepted the residual risks.

  • Evidence of implementation for each control

    Policies, configurations, logs, training records. A reference directly in the row is strongest, so that nobody has to search during the audit.

  • Version and approval

    Date, version and who approved it. This makes clear which state the audit refers to.

  • The link to the scope

    The statement matches what the scope says: sites, outsourced services, interfaces. An exclusion that contradicts the scope otherwise only comes to light during the site tour.

Typical nonconformities

  1. Exclusion without a sound justification

    “Not relevant” or “not applicable” with no reference to your own organisation, or a reason that does not hold up on the site tour: remote working is excluded, but half the workforce regularly works from home.

  2. Statement and treatment plan do not match

    The plan contains controls that are missing from the statement, or the statement lists controls as implemented that are still open in the plan.

  3. “Implemented” without evidence

    The row says “implemented”, but neither a document nor a configuration nor an interview can confirm it.

  4. The statement is missing or incomplete

    If the statement is missing altogether or whole parts are missing, such as the justifications for exclusions, a piece of explicitly required documented information does not exist; that is a major nonconformity. If individual details are missing in otherwise complete rows, it is usually a minor nonconformity.

  5. Outdated structure

    The statement still follows the 2013 edition with 114 controls, or it was merely renumbered during the transition without justifying each row afresh. The transition period to the 2022 edition ended in October 2025.

  6. Clauses excluded instead of controls

    Only Annex A controls can be excluded, never requirements of clauses 4 to 10. A statement that declares, say, risk assessment or internal audit not applicable misunderstands its purpose.

Differences by standard

ISO 27001ISO/IEC 27001

The Statement of Applicability exists only in ISO/IEC 27001. In the 2022 edition it is part of risk treatment in clause 6.1.3 (item d) and refers to the 93 Annex A controls in four themes; the 2013 edition had 114 controls in 14 sections. How the individual controls can be implemented is described in ISO/IEC 27002, which does not set requirements itself. The risk assessment is repeated at planned intervals and when significant changes occur (clause 8.2), the treatment is implemented (8.3), and the statement is updated along with both. ISO 9001 and ISO 14001 have no comparable document.

How IMScollect covers it

In IMScollect the Statement of Applicability is an overview of all Annex A controls, with key figures and filters for applicable, not applicable, not yet reviewed and open. For each control you open a panel with applicability, justification, implementation status, owner and a description of how you implement it. When a control is classified for the first time, an owner is mandatory.

Implementation actions become tasks, risks from the register can be linked, and you attach evidence directly: as a file, from document control or as a link. Anyone who excludes a control that still has actions or risks attached sees what follows before saving. Every change is recorded in the history, the statement is available as PDF and CSV, and the risk treatment plan with the acceptance of residual risks has a page of its own. The AI advisor Conni suggests justifications for controls not yet reviewed; only what you approve is adopted.

Try it yourself, no call needed.Prefer a walkthrough? Book a guided demo →

Frequently asked questions

Is the Statement of Applicability mandatory?▾

Yes. ISO/IEC 27001 explicitly requires it as documented information. Certification to ISO 27001 is not possible without a Statement of Applicability.

Does the statement have to cover all 93 Annex A controls?▾

Yes. Every Annex A control is addressed in it: included with a reason and implementation status, or excluded with a justification. Controls from other sources are added if you use any.

Can Annex A controls be excluded?▾

Yes, if they are not necessary according to your risk assessment and your scope and the exclusion is justified. Only Annex A controls can be excluded, not requirements from clauses 4 to 10.

How are the Statement of Applicability and the risk treatment plan related?▾

The statement says which controls apply and how far they are implemented. The treatment plan says which risk is treated with which actions by when and who approves it. Both are produced during risk treatment and have to be consistent with each other.

Further reading and viewing

Template for this clause

Philipp Kappe

Philipp Kappe

Founder of IMScollect

Philipp builds IMScollect. TÜV-certified auditor with a background in governance, risk and compliance, more than 200 audits conducted and supported.

This page explains in our own words and does not replace the text of the standard. You can obtain the standards from ISO(opens in a new window) or from your national standards body. Clause numbers and titles follow ISO 9001:2026, ISO 14001:2026 and ISO/IEC 27001:2022.