Skip to content
Knowledge base

ISO 27001 Statement of Applicability (SoA): how to write it so it passes the audit

The auditor opens the Statement of Applicability at a single row and asks why this control is in the system and where the evidence is that it works. The ISO 27001 Statement of Applicability is the bridge between risk assessment and what can be verified: every row has to lead back to a risk or requirement and forward to evidence.

The certification body’s auditor opens the Statement of Applicability at the row about backups and asks two questions: why is this control in the system, and where is the evidence that it works? The person responsible for the management system has the word “implemented” in the spreadsheet but does not know who owns the restore test or where the latest report is. A conversation that was supposed to take five minutes ends with a nonconformity.

The Statement of Applicability (SoA) is the ISO 27001 document that links risk assessment to controls, and controls to evidence. The auditor picks it up as one of the first documents, because it determines what in the company’s cybersecurity programme will be examined. A good Statement of Applicability lets you move from any row back to the risk and forward to the evidence. A weak one looks complete until someone asks about the justification.

What is the Statement of Applicability in ISO 27001?

The Statement of Applicability is a documented list of the controls an organisation has determined to be necessary in its information security management system (ISMS), together with the justification for each decision. ISO/IEC 27001:2022 requires it to be produced under clause 6.1.3 d), as noted in IAF MD 26:2023, the International Accreditation Forum (IAF) document of 15 February 2023 describing the transition to the new edition of the standard.

ISO published the current edition of the standard on 25 October 2022, and in February 2024 it added amendment Amd 1:2024, titled “Climate action changes”. The header of the document should therefore give the full designation: ISO/IEC 27001:2022 together with Amd 1:2024.

The SoA does not replace the security policy or the risk assessment. It is a condensed form of both that can be set against the reference catalogue, which is Annex A of the standard. You will find an overview of the standard and the certification cycle in the ISO 27001 guide, the requirements of the clauses from the context of the organisation to improvement are covered in the article on the key requirements of ISO 27001, and the remaining articles on the standard are collected in the ISO 27001 section.

Where do the entries in the Statement of Applicability come from?

The entries come from decisions about risk treatment, and Annex A is used to check them, not to invent them. IAF MD 26:2023 describes this step as a comparison between the controls determined by the organisation and those in Annex A (clause 6.1.3 c)), which lets the organisation confirm that no necessary control has been omitted by oversight. If the comparison reveals such an omission, the organisation must update its risk treatment plan and implement the missing control.

Annex A references the controls of ISO/IEC 27002:2022, which according to IAF MD 26:2023 contains 93 controls in four clauses instead of the former 114 in fourteen. The four groups are organisational, people, physical and technological controls.

In practice, the order of work is therefore as follows: first the risk assessment, then the choice of treatment for each significant risk, then the controls needed to carry out those decisions, and finally the comparison with Annex A. On top of that come controls required by law and contracts, even when no risk in the register forces them.

The reverse order, starting from the Annex A list and ticking off what the company “has”, produces a document that describes an inventory rather than a response to risk. The auditor will recognise it by the justifications, which read like descriptions of purchased tools rather than decisions.

What must the Statement of Applicability contain?

The standard requires four elements: the necessary controls, the justification for their inclusion, whether they are implemented, and the justification for excluding any Annex A control. IAF MD 26:2023 points out that the wording of clause 6.1.3 d) was reorganised in the 2022 edition to remove potential ambiguity.

Annex A is a reference set, not a closed list. If the organisation applies a control that is not in it, for example a requirement from a contract with a key customer, it can add that control to the Statement of Applicability as a separate row with the same kind of justification as the others.

The minimum required by the standard is enough for the document to conform. To make it useful during an audit, it is worth adding columns that save time for both sides:

  • control identifier and name in the numbering of the current edition,
  • applicability status: applied or excluded,
  • justification referring to a risk, regulation, contract or board decision,
  • implementation status: implemented or in progress with a deadline from the risk treatment plan,
  • owner, the person who will answer the auditor’s questions,
  • reference to evidence: procedure, register, report, configuration screenshot.

The last column turns the SoA from a document you “have” into a map of evidence. When the auditor asks about a row, the answer starts with pointing to a file, not with searching for someone who remembers something.

How do you justify including and excluding a control?

A justification for inclusion names the source of the need, and a justification for exclusion shows why that source does not exist in the organisation. There are four sources, and it is worth naming them explicitly: a risk in the register, a legal requirement, a contractual obligation or a management decision.

A good justification for inclusion is short and verifiable: “Applied because of risk R-14 (loss of customer data during an outage), the requirement in the contract with customer K and the board decision of 12 March”. The auditor can find each of these elements in another document and compare the dates.

A justification for exclusion has to say what the organisation lacks. “Not applicable” says nothing. “Not applied, because the organisation does not carry out the activity the control relates to, as confirmed by the ISMS scope description, version 3.1” says everything that is needed. For every exclusion, ask yourself a control question: does anything in the scope of the system contradict it?

External services deserve separate attention. Excluding a control only because a cloud provider delivers the service is a flaw in reasoning. The risk does not disappear; only the party operating the control changes, and the Statement of Applicability keeps a row about supplier oversight and about how the company verifies the supplier’s commitments.

A justification should not restate the control name in other words either. The sentence “applied because backups are important” sounds like a justification, but it does not lead to any document that could be checked.

How does the Statement of Applicability differ from the risk treatment plan?

The SoA says which controls the organisation applies and why, while the risk treatment plan says who will bring each risk to an acceptable level, by when and by what means. The first document is organised by control, the second by risk.

This difference has a practical consequence: one control can serve several risks, and one risk can require several controls. A row with the status “in progress” must have a deadline consistent with the plan, and every action in the plan should map to a row in the Statement of Applicability. A mismatch of dates between these documents is easy to spot by comparing them row by row.

The link between the two documents is also visible in the IAF requirements for the transition audit to the 2022 edition: IAF MD 26:2023 lists among its mandatory elements the updating of the SoA and, where applicable, the updating of the risk treatment plan. A change in one document entails a change in the other. How to carry out the risk assessment itself is described in the article on IT risk analysis.

How do you build a Statement of Applicability step by step?

You build it from the scope and the results of the risk assessment, and the comparison with Annex A comes at the end, not at the beginning. The sequence that works in practice has six steps:

  1. ISMS scope. Without a documented scope, you cannot justify an exclusion, because it is unclear what it refers to. The scope covers locations, processes, systems and suppliers.
  2. Controls from the risk treatment plan. List the controls needed to carry out the decision on each significant risk, with references to risk numbers.
  3. Legal and contractual requirements. Add the controls that follow from the regulations binding the company (for example the GDPR or national cybersecurity legislation) and from customer contracts, as a separate source of justifications.
  4. Comparison with Annex A. Go row by row through all Annex A controls and record a decision for each. An omitted control goes back to the risk treatment plan.
  5. Completing the columns. For each row: implementation status, owner and reference to evidence. A row without an owner signals that the control exists only on paper.
  6. Approval and version. Submit the document for approval by management and risk owners, give it a version number and date, and record changes in the document history.

Step five draws in the largest number of people, because control owners sit in different departments. That is why it pays to bring them together in a single workshop instead of emailing the spreadsheet for completion.

Which Statement of Applicability mistakes surface during an audit?

The mistakes that surface during an audit are above all those that can be detected with a single question: a missing justification, missing evidence or a contradiction with another document. Each of them comes from writing the document as a form rather than as a map of decisions.

“Not applicable” without a reason. An exclusion with no justification, or with one contradicted by the scope of the system, for example excluding requirements on the security of premises when the scope includes an office with its own server room.

“Implemented” without evidence. A status in a spreadsheet is not evidence. For the transition audit to the 2022 edition, IAF MD 26:2023 states explicitly that it must not rely only on document review, especially for technological controls. That sentence concerns one type of audit, but it captures how auditors work: the document is the starting point for interviews and observation.

Dates that do not match. The status “implemented” for an action that, according to the risk treatment plan, ends in three months, or a Statement of Applicability approved before the risk assessment it supposedly relies on.

Old numbering. Procedures and registers referring to controls from the 2013 edition, while the SoA uses the 2022 numbering. After the change in the number and structure of controls, such references lead nowhere.

No owner. A control nobody is responsible for has no one to defend it during the audit, even if it actually works.

How do you maintain the Statement of Applicability after certification?

You update it whenever a change alters the risk or the scope of the system, not once a year before the surveillance audit. Typical triggers are a new system or supplier, a new location, a new regulation, an incident and an internal audit finding.

The transition period between the editions of the standard is over. According to IAF MD 26:2023, certifications issued under accreditation against ISO/IEC 27001:2013 were to expire or be withdrawn at the end of the transition period, which for certified organisations ended on 31 October 2025. Documents rewritten in a hurry before that deadline are worth reviewing again, because that is exactly where old references and justifications copied without checking remain.

A good practice is to tie the Statement of Applicability to the system’s cycle: a review before every management review, a status check after every internal audit and a comparison with the risk register after every significant change. How to make the most of the internal audit itself is covered in the article on the ISO 27001 internal audit.

The change history matters as much as the content. When the auditor sees that an exclusion appeared after an incident or a change of supplier, the question will be about the decision that justifies it. A history entry with a date and a reference to that decision closes the topic in one sentence.

How do you check whether the Statement of Applicability is ready for audit?

The document is ready when the answer to any auditor question about any row leads to a specific document or record. The checklist below turns this into questions worth asking yourself before the audit.

Element of the documentAuditor’s questionEvidence worth having at handWarning sign
ScopeWhat does the system cover and what does it exclude?Scope description with version and dateExclusions contradicted by the scope
Applicability statusDoes every Annex A control have a decision?Complete set of rows in 2022 numberingEmpty rows or 2013 numbering
Justification for inclusionWhere does the need for this control come from?Risk number, regulation, contract, resolutionJustification restates the control name
Justification for exclusionWhy don’t you apply this control?Extract from the scope or process register”Not applicable” without a reason
Implementation statusDoes it work today?Report, register, configuration screenshot, sample”Implemented” with no date and no evidence
OwnerWho will answer questions about this row?Named assignment in the documentA department instead of a person, or no entry
Consistency with the planDo deadlines match the risk treatment plan?Plan with the same risk numbersDifferent dates in the two documents
Version and approvalWho approved this state and when?Change history, approval recordApproval older than the risk assessment

Key takeaways:

  • Entries come from risk, regulations and contracts, and Annex A is used to check that nothing has been missed.
  • Every exclusion must say what the organisation lacks, not just that something is “not applicable”.
  • The status “implemented” without a reference to evidence is only a statement of intent during an audit.
  • Dates in the SoA, the risk treatment plan and the risk assessment must be consistent.

How can nFlo help you prepare the Statement of Applicability?

In the “Governance, risk and compliance” area, nFlo prepares organisations for ISO 27001 certification and helps them maintain the system afterwards. Under the ISO 27001 - Implementation and Certification Preparation service, the team prepares the ISMS documentation, including the Statement of Applicability, runs the risk assessment using a methodology aligned with ISO 27005 and the internal audit, and assists the organisation during the certification audit.

If the system is already running, the ISMS Review, Audit and Advisory service covers a review of the documentation, including the SoA, an evidence-based verification of the effectiveness of implemented controls and a readiness review before the certification audit. The result is a prioritised list of gaps, not a new binder.

nFlo is not a certification body: the certificate is granted by an accredited body, and our role ends with preparing the organisation and its evidence. If you want to check whether your Statement of Applicability will withstand the auditor’s questions, contact us.

What else is worth knowing about the ISO 27001 Statement of Applicability?

Does the Statement of Applicability have to cover every control in Annex A?

Every control in Annex A should receive a decision in the SoA: applied with a justification or excluded with a justification. The comparison with Annex A exists so that no necessary control is omitted by oversight, and an empty row looks exactly like such an oversight.

Can you exclude a control because it is expensive?

Cost alone is not a justification for exclusion. If the control addresses a risk in the register and the company consciously decides not to apply it, that is a risk acceptance decision. The risk owner should make it, it should follow from the risk treatment plan, and the SoA merely records it.

Who approves the Statement of Applicability?

In practice, the Statement of Applicability is approved by the management responsible for the information security management system, after agreement with risk owners and control owners. The approval needs a date and a version number, because the auditor compares them with the dates of the risk assessment and the treatment plan.

How often should you update the Statement of Applicability?

Whenever a change alters the risk or the scope of the system: a new system, supplier, location, regulation or internal audit finding. Beyond that, it is worth reviewing it before every management review so that implementation statuses match the risk treatment plan.

Can you show the Statement of Applicability to a customer?

You can, but with care. The document describes which controls the company applies and which it does not, so the full version reveals a lot about its protection. Instead, you can show the certificate and its scope or a summary of the document shared under a non-disclosure agreement.

Share:

Talk to an expert

Have questions about this topic? Get in touch with our specialist.

Sales Representative
Przemysław Widomski

Przemysław Widomski

Sales Representative

Response within 24 hours
Expert consultation
Individual approach

Providing your phone number will speed up contact.

Want to Reduce IT Risk and Costs?

Book a consultation - we respond within 24h

Response in 24h Custom quote No obligations