What is cross-framework control mapping?
Direct answer
Cross-framework control mapping identifies where requirements from different frameworks overlap: for example, ISO 27001 A.5.15 (access control) and NIS2 Article 21(2)(i) (access management) describe essentially the same practice. By mapping these overlaps, organisations implement and evidence a control once instead of duplicating effort per framework. In Acuna GRC, requirements from different frameworks link to shared measures.
Reference measures from the Common Measures library arrive pre-mapped, the Mapping page lists orphan requirements and measures with suggestions, Run AI ranks candidates from your own library with a confidence score, and bulk linking applies many links with one confirmation.
Where do ISO 27001 and NIS2 overlap?
Article 21(2) of NIS2 lists the cybersecurity risk-management measures essential and important entities must take. Most of them have a counterpart in the 93 controls of ISO/IEC 27001:2022 Annex A:
- Access control policies and asset management (Article 21(2)(i)) and access control (A.5.15) and the inventory of assets (A.5.9).
- Business continuity, backup management and disaster recovery (Article 21(2)(c)) and information backup (A.8.13) and ICT readiness for business continuity (A.5.30).
- Supply chain security (Article 21(2)(d)) and information security in supplier relationships (A.5.19).
- Cryptography and encryption (Article 21(2)(h)) and use of cryptography (A.8.24).
- Cyber hygiene practices and cybersecurity training (Article 21(2)(g)) and awareness, education and training (A.6.3).
Overlap is not identity. NIS2 also places accountability on management bodies (Article 20) and sets incident reporting obligations (Article 23) that a control set alone does not cover, and SOC 2 or DORA bring their own wording and evidence expectations. A mapping shows where one piece of work can serve several frameworks; it does not make the frameworks equal. See does ISO 27001 cover NIS2?
How do you build a cross-framework mapping?
Mapping every framework to every other one does not scale: three frameworks give three pairs, five give ten. The usual method is a pivot, one shared set of measures that each framework maps to.
- Define the measures your organisation actually runs, in your own words, each with an owner.
- Link each framework requirement to the measures that meet it. One requirement can need several measures, and one measure can serve many requirements.
- Note how strongly each measure covers the requirement, so a partial match is visible.
- Work the gaps in both directions: requirements with no measure, and measures that serve no requirement.
- Attach controls and evidence to the measure, not to each framework, so one record counts everywhere it applies.
- Review the mapping when a framework is revised or a new one is adopted.
What mistakes make a control mapping unreliable?
- Assuming a one-to-one match. A single NIS2 point often spans several Annex A controls, and the reverse.
- Mapping by keyword. Two clauses that mention "access" can ask for different things.
- Treating "mapped" as "compliant". A link says which measure should meet a requirement; only the evidence shows it does.
- Letting the mapping age. Framework revisions and new measures leave orphans on both sides.
- Duplicating measures per framework, which defeats the purpose and splits the evidence.
How does cross-framework mapping work in Acuna GRC?
In the Comply workspace, the Common Measures library lists reference measures recommended for your selected frameworks. Each card shows an Acuna Reference ID and badges for the requirements it maps to, with a primary or secondary strength. Adopting one creates your own measure in the Measure Library, already linked to those requirements. Two requirements from different frameworks mapped to the same reference measure count as related, which is the pivot behind the suggestions.
The Mapping page keeps two live gap lists: Orphan Measures, with green badges for frameworks covered and amber Missing badges where the catalog expects a link, and Orphan Requirements with no measure linked. From either list you can:
- Open suggestions from the reference library, or Run AI, which ranks candidates from your own library with a confidence score and a one-line reason.
- Adopt & link a matching reference measure in one step.
- Ignore an intentional orphan, which hides it and deletes nothing.
- Select many rows and Suggest for selected, review the top suggestion per row, then Apply N links with one confirmation.
Controls then verify the measure in Implement, and their health rolls up to every requirement the measure serves. See how measures and controls link to requirements.
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.
- Core workspace
Implement
Requirements, the measures and controls that address them, and the business context of assets, third parties, processes, roles and staff.
- Platform
Acuna GRC platform
Acuna GRC is one GRC platform: four core stages from frameworks to audits on the same data, add-on modules when you need them, and Aiko at your pace.
Sources
This page explains the rules in general terms and is not legal advice.
Frequently asked
Does mapping ISO 27001 to NIS2 make us NIS2 compliant?
No. The mapping shows which existing measures address NIS2 requirements. You still need evidence that they run, and NIS2 obligations with no ISO 27001 counterpart, such as incident reporting under Article 23, need their own work.
Should frameworks be mapped to each other or to a common set of measures?
To a common set of measures. Each new framework then maps once to that set, and evidence attached to a measure counts for every framework linked to it.
Can AI do the mapping?
It can propose it. In Acuna GRC, Run AI ranks candidate links with a confidence score and a reason, and a person ticks the ones to apply. The decision stays with the team that owns the programme.
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)

