How does applicability marking work for framework requirements?
Direct answer
In Acuna GRC, applicability is set in two places. In the Comply workspace, you tick the requirements of each adopted framework that apply to your organisation and assign the framework to scopes. In Implement, a requirement can be marked Not applicable with a justification: it shows a quiet N/A badge and stays out of compliance KPIs.
For ISO 27001, these decisions and their justifications are what your Statement of Applicability records. Deselecting a whole framework takes its requirements out of KPIs, pickers and Mapping but keeps the records and links, so selecting it again brings everything back.
Why does applicability matter in ISO 27001?
ISO/IEC 27001:2022 separates two kinds of requirement. Clauses 4 to 10 define the management system, and none of them can be excluded. The 93 controls of Annex A are different: each one is included or excluded as a result of risk treatment (clause 6.1.3).
The Statement of Applicability records that decision. It lists the necessary controls, the justification for including them, whether each one is implemented, and the justification for excluding any Annex A control. Auditors read it next to the risk assessment and the risk treatment plan, so every exclusion should trace back to the scope or to the absence of a risk, and every inclusion to a risk, a legal requirement or a contractual obligation.
Other frameworks need the same discipline even when they do not call it an SoA: a requirement you consider out of scope should say why, and someone should be able to check that reason later.
How do you decide a requirement does not apply?
A requirement is a fair candidate for Not applicable when one of these is true and you can show it:
- The activity it governs falls outside the defined scope, for example a site, entity or service the programme does not cover.
- The risk it addresses does not exist for you, according to your risk assessment.
- No legal, regulatory or contractual obligation calls for it.
Write the justification in plain terms, name who made the decision, and revisit it when the scope, the risks or the services change. A requirement that applies but is not yet in place is not "not applicable"; it is a gap, and it belongs in the plan.
What mistakes do auditors find in applicability decisions?
- Exclusions with no documented justification, or a justification copied from a template.
- Requirements marked not applicable to lift a compliance score, when they are really not implemented.
- Decisions that no longer match the scope after a new site, product or entity was added.
- Applicability that contradicts the risk assessment: a control excluded although a risk in the register depends on it.
- No trace of who decided and when.
How does applicability marking work in Acuna GRC?
In the Comply workspace, an administrator adopts each framework and ticks the requirements that apply. Each framework can be assigned to one or more scopes, such as a legal entity, a site or a business unit; the rest stays Global, and the global scope filter then limits every table and dashboard to the scopes you choose.
In Implement, a requirement can be marked Not applicable with a justification. It shows a quiet N/A badge and stays out of compliance KPIs, so the figures reflect only what you committed to. Each applicable requirement carries its compliance status, maturity, owners and linked measures and controls, which is what an SoA needs beside the decision itself.
Deselecting a whole framework is a different action. It takes the framework’s requirements out of KPIs, pickers and the Mapping page, but keeps the records and links, so selecting it again brings everything back. Where the compliance roadmap is switched on, requirements marked Not applicable are proposed for exclusion when you review the roadmap items.
How Acuna GRC handles it
- Core workspace
Comply
The frameworks you select, the scopes and tags that segment your organization, the common measures library and the mapping of measures across frameworks.
- Solution
ISO 27001
Adopt ISO 27001, give every control an owner, run your risks and policies, and keep the records an auditor asks for, with measures shared across frameworks.
- Core workspace
Implement
Requirements, the measures and controls that address them, and the business context of assets, third parties, processes, roles and staff.
Sources
This page explains the rules in general terms and is not legal advice.
Frequently asked
What is the difference between not applicable and not implemented?
Not applicable means the requirement does not concern you, with a justification. Not implemented means it concerns you and is not yet met. The first stays out of compliance figures; the second is a gap that should count against them until it is closed.
Can we exclude ISO 27001 clauses 4 to 10?
No. Clauses 4 to 10 apply to every ISMS. Only Annex A controls can be excluded, and each exclusion needs a justification in the Statement of Applicability.
Does deselecting a framework in Acuna GRC delete its data?
No. Its requirements leave KPIs, pickers and Mapping, but the records and links are kept, and selecting the framework again restores them.
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
.png&w=3840&q=75&dpl=dpl_96PxuEbyzwoWxjweCh9wLaGaDCHP)

