Blog
ISO 27001 Statement of Applicability: Why Most Projects Get It Wrong
ISO 27001 certification consultancy services start with one test: does the Statement of Applicability trace back to real risks? See what a good one looks like and where ISMS consultancy services fit.
Neha Dvivedi · 16 أغسطس 2026
Why is the Statement of Applicability the document to judge a project by?
It’s where an organisation declares what it thinks matters, and why. Clause 6.1.3 of ISO/IEC 27001:2022 requires it to list the necessary controls, justify including them, say whether they’re implemented and justify excluding any Annex A control. Read closely, it tells you almost everything about how the project is going.
Ask a practitioner to judge an ISO 27001 project from a single document and the answer is rarely the risk register or the policies. It’s the SoA. Annex A holds 93 controls in the 2022 edition, down from 114 in 2013, but it doesn’t make any of them necessary. The organisation decides that through risk treatment, then compares its choices with Annex A to check nothing was missed.
Source for Annex A : https://www.iso.org/standard/27001
What do weak and strong Statements of Applicability look like?
A weak one marks every control applicable with the same justification, “required by the standard”, and links none to a risk. A strong one marks controls applicable because a named risk needs them, and excludes others with reasons a stranger could judge. A healthy number of exclusions shows somebody thought about the organisation.
The weak version often repeats one sentence down ninety-three rows. It happens when the SoA is built first, usually from a bought template, and the risk assessment is written afterwards to support it. The logic runs backwards. Auditors spot it quickly, because they pick a control and ask which risk it treats. A shrug puts the whole system under suspicion.
Marking everything applicable feels safe. It isn’t. The organisation has just committed to implementing and evidencing ninety-three controls, including ones with no relevance to it, and each is now open to examination. ISO 27001 consultants see this most often where the template came first.
The strong version gives an excluded control a justification like this: no on-premise infrastructure, all systems cloud hosted under supplier agreements covered by controls 5.19 to 5.23. An auditor can accept or challenge that on its merits. “Best practice” gives them nothing to weigh. The ISO 27001 certification requirements ask for justified controls, not a long list of applicable ones.
Why does the order of work matter?
Scope comes first, then risk assessment, then risk treatment, then the Statement of Applicability. The SoA is an output that records decisions already made. When people start from the control list and work backwards, the risk assessment becomes a justification exercise and stops being useful.
Organisations can spend months implementing controls that no risk in their own register called for. Meanwhile a genuine exposure sits untreated, because it doesn’t map neatly to an Annex A entry. The standard allows for this. The Annex A set isn’t exhaustive, and an organisation can add the controls its risks need.
How can you test your SoA in ten minutes?
Pick five controls marked applicable at random and ask each system owner which risk the control treats. If they can answer for all five, the system is sound. If they can answer for two, the SoA was written from a template and the risk assessment is decorative. The test takes ten minutes and tells you more than a mock audit.
Experienced ISO 27001 consultants add a column to the SoA that names the risk each control treats, which makes the test quick to run. A properly built SoA describes how the organisation decided to protect itself. It makes every later year easier, because when something changes you can see what it affects. One built backwards exists to be shown to auditors, has to be maintained, never helps anyone and quietly becomes untrue. Only one of those is worth writing.
How do ISO 27001 certification consultancy services play a main role?
Consultants make sure the order is right: scope, risk assessment, treatment, then the SoA. They test each justification, link controls to risks and prepare the evidence an auditor will sample. They don’t issue certificates. An accredited certification body does that after a successful audit.
ISMS consultancy services often start by reading the risk register against the draft SoA and listing every control with no risk behind it. Good ISO 27001 consultant services leave the organisation able to defend each decision without help. Experienced ISMS consultants advise rebuilding the SoA from the risk register, not from a template, and writing each exclusion so a stranger could evaluate it. Management system certification goes more smoothly when the document at its centre is true.
Which industries and countries gain most?
Any organisation that handles information can use ISO 27001: IT and ITES firms, banks and finance, healthcare, education, hospitality, retail, government, transport, manufacturers, real estate, facility management companies and start-ups. The standard doesn’t depend on sector, so the SoA principle holds in every country.
Each organisation’s SoA should look different. In India, ISO 27001 certification consultancy services often start with IT and ITES firms and banks whose SoAs came from templates. Picture a fintech in Nigeria, a hospital in Kenya, a call centre in the Philippines and a bank in Oman. Add a software firm in the USA and a government agency in New Zealand. Each holds different assets and faces different threats, so their documents should differ. Healthcare and public bodies can use ISMS certification consultancy services in Kenya to get there. A company hiring an ISMS consultant in Singapore faces the same task.
How can MSCi help with ISO 27001?
MSCi prepares organisations for conformity assessment and audits. We review the risk register and the draft SoA together with your team, trace each control to a risk and rewrite weak justifications. We don’t issue the ISO certificate or any notified body certificate.
As ISO certification consultants with 40+ years of experience in ISO consultation, we know which controls auditors pick first. We start with the five-control test, then agree with your team what goes into the SoA and what stays out, and why.
5. FAQ
1. What is a Statement of Applicability?
It’s the document that records which Annex A controls an organisation needs, why, whether they’re implemented, and why any others are excluded. Clause 6.1.3 of ISO/IEC 27001:2022 requires it. ISO 27001 consultants usually treat it as the best single view of a project.
2. How many Annex A controls must be marked applicable?
There’s no fixed number. The organisation decides which controls are necessary through risk treatment and justifies every Annex A exclusion. ISO 27001 certification consultancy services help check that each choice traces to a risk.
3. Is it a problem if many controls are excluded?
Not if each exclusion has a justification someone else could evaluate. A meaningful number of exclusions often shows the organisation thought about its own context. ISMS consultants would worry more about a SoA with none.
4. Can we start from a template?
A template is fine as a list of controls to consider. The justifications must come from your own risk assessment, not the template. Good ISO 27001 consultant services rebuild them from the risk register.
5. Do consultants write the SoA for us?
They guide the work and test it, but the organisation owns each decision. An auditor will ask the people who run the systems, so ISMS consultancy services work best when your own team can answer.
6. Can MSCi issue an ISO 27001 certificate?
No. MSCi is a consultancy that prepares companies for conformity assessment and audits. Certificates come only from an accredited certification body after a successful audit.
What this covers
See how this looks as a working system
Reading about a requirement and seeing the documentation that satisfies it are different things. In a short demo we open the actual manual, procedures and records set for ISO/IEC 27001, show you how each clause is answered and where your existing way of working already fits. You will know what implementation involves before you commit to it.
More reading
- Automotive Suppliers Face Stricter Cybersecurity Assessments
Cybersecurity is becoming a key part of supplier evaluations in the automotive industry. Vehicle manufacturers now check how suppliers protect data and systems alongside quality, cost, and delivery.
13 سبتمبر 2026
- Automotive OEM Vendor Cybersecurity Assessment: Controls, Scoring and ISO Standards Mapping
What does an automotive vendor cybersecurity assessment cover?
13 سبتمبر 2026
- Inside an Automotive OEM Vendor Cybersecurity Assessment: The 19 Control Families and What They Actually Ask For
The nineteen control families in an automotive vendor cybersecurity assessment, where the structure came from, and why good controls still score zero.
13 سبتمبر 2026
