When an auditor opens the Statement of Applicability (SoA) in an ISO 27001 audit, they look at two things: does every row have a justification, and does that justification match something in the risk register? An SoA you may come across is a table with “Yes – Implemented” on all 93 rows and an empty justification column. Such an SoA doesn’t show the link between the decisions arising from the organization’s risk assessment and the controls it applies; it doesn’t answer the auditor’s question, “Why do you apply this control, and why don’t you apply that one?” Below are the columns of a good SoA, the preparation steps, sample rows and typical mistakes.
What the SoA must contain
The standard expects the SoA to contain the necessary controls, the justification for including them, whether they’re implemented and the justification for excluding any Annex A controls. In practice, each row has these columns:
| Column | Explanation |
|---|---|
| Check | Annex A control number and name |
| Applicable? | Yes / No |
| Reason | Risk treatment decision, legal/contractual requirement, business need or reason for exclusion |
| Implementation status | Implemented / partial / planned (with target date) |
| Reference | Related policy, procedure or technical record |
| Owner | Role responsible for the control |
The “Reference” and “Owner” columns aren’t elements the standard explicitly lists; but they’re the two columns that save the most time in an audit. When the auditor samples a control, which document holds the evidence and who has it is read from the table. No searching. To see that access and configuration controls work in the live environment, define the scope of a technical cybersecurity audit.
Adding controls from outside Annex A is also possible. If a sector standard, customer contract or legislation requires a control with no exact equivalent in Annex A, it can be written into the SoA as a separate row.
How to prepare the SoA: six steps
- Gather the risk treatment decisions. List the controls selected for each “reduce” decision.
- Add other requirements. Mark the controls made mandatory by requirements such as KVKK, customer contracts or TISAX.
- Compare with Annex A. Go through every Annex A control and confirm that no necessary control has been missed.
- Justify exclusions. For example, excluding secure development controls on the grounds that “the organization doesn’t develop software”; but if off-the-shelf software is customized, this justification may no longer hold.
- State the implementation status honestly. Controls not yet completed are marked “planned” and tracked in the risk treatment plan.
- Approve and version it. The SoA is a living document; it’s updated when controls change.
Order matters. Starting the SoA from the Annex A list and ticking “do we have this?” is the most common shortcut, and it makes the risk assessment meaningless. Control selection comes from risk; Annex A only serves as a checklist: “Did we forget anything?”
Check exclusion justifications against reality on the ground. The owner of an SoA stating “the organization doesn’t develop software” often doesn’t know that the IT team automates with PowerShell scripts, writes custom reports and integrations in the ERP, and edits plugins on the website. These are development activities. In that case, the exclusion justification no longer holds.
Sample SoA rows
| Control (summary) | Applicable | Reason | Status |
|---|---|---|---|
| Information backup | Yes | Risk R-07 (ransomware), customer contract | Implemented — Backup Policy, quarterly test records |
| Physical security monitoring | Yes | Risk R-12 (unauthorized entry) | Partial — camera coverage being extended |
| Outsourced development | No | No software development or outsourced development is carried out | — |
The phrase “quarterly test records” in the first row is a commitment. The auditor will ask for restore test records for the last four quarters. If there are no records, the row should be “Partial”, not “Implemented”. For technical controls, open the relevant system’s report before writing the status: the backup software’s job history, the patch tool’s compliance report, the coverage list in the EDR console. The status in the SoA must match the status in the console.
Common SoA mistakes
- Marking all controls “Yes / implemented” without justification.
- Writing only “risk” in the justification column without stating which risk is involved.
- Not updating an old SoA built on the 114-control structure of the 2013 version.
- Referenced documents not existing or being kept under a different name.
- Inconsistent status information between the risk treatment plan and the SoA.
The last one usually comes from version management: the risk treatment plan is updated in Excel while the SoA stays in its old form in Word. Keeping the two tables in the same file on separate sheets, or feeding the SoA’s status column directly from the risk treatment plan, prevents this drift. With each update, the version number, date and approver should be written into a change table.
The SoA in the transition to the 2022 version
ISO/IEC 27001:2022 reorganized the Annex A controls under four themes aligned with ISO/IEC 27002:2022 and added new controls such as threat intelligence, use of cloud services, configuration management, data masking and monitoring activities. The number of controls fell from 114 to 93; much of this comes from merging old controls, so the scope hasn’t shrunk. An SoA prepared with the 2013 version needs to be moved to the new structure and the new controls assessed through risk decisions. Certification bodies’ transition timelines should be confirmed from their own announcements before implementation.
A practical method for the move is to use the old–new control mapping table in the annex to ISO/IEC 27002:2022. Each justification in the old SoA is carried over to the new control, and justifications are merged for merged controls. For new controls, the justification is written from scratch; controls such as configuration management and monitoring activities should be assessed together with the IT team, based on existing tools and records.
Test the SoA yourself before the audit
Do the auditor’s sampling yourself a week earlier. Pick ten random rows from the SoA; for each row marked “Implemented”, open the referenced document, then find the latest record that document produced. If all three steps can be completed, the row is solid. If the document exists but there’s no record, the status is moved to “Partial” or record production starts immediately.
- For each excluded control, does the justification still match the organization’s current activities?
- Has the target date of any “planned” row passed? If so, is there a new date and approval?
- Is every “reduce” decision in the risk register linked to at least one SoA row?
- Is the latest version of the SoA more recent than the latest risk assessment date?
This check is half a day’s work. It shows in advance most of the findings that would come up on audit day.
Frequently asked questions
Do we have to share the SoA with customers?
No. The SoA is an internal document and may contain sensitive information. If customers request it, sharing a summary or sharing under a confidentiality agreement can be considered.
Do controls marked “planned” in the SoA cause problems in the audit?
Planned controls must be tracked in the risk treatment plan with an owner and target date, and the residual risk must have been approved. If incomplete controls relate to critical risks, the auditor may question the justification.
How often is the SoA updated?
When the control selection or implementation status changes, and at the planned intervals at which the risk assessment is reviewed. Each update should be recorded with a version number and approval.
If you’d like to run your SoA and risk work together, take a look at our ISO 27001 Risk Analysis, Risk Treatment and SoA service.