How do measures and controls link to requirements in Acuna GRC?
Direct answer
In Acuna GRC, the chain runs requirement, measure, control, task. A measure is the practice that meets one or more requirements, and one measure can address clauses in ISO 27001, NIS2 and SOC 2 at the same time. A control is the verification activity, with a frequency, that checks the measure works, and recurring tasks carry it out.
Measures are linked to requirements on the measure itself, on the Mapping page of the Comply workspace, or by adopting reference measures that arrive pre-mapped. Health flows up the same chain, which is how one piece of work counts for every framework it serves.
Why link through measures instead of straight to each framework?
Frameworks overlap far more than their wording suggests. A quarterly review of access rights answers ISO/IEC 27001:2022 Annex A 5.18 (access rights) and NIS2 Article 21(2)(i), which lists access control policies among the cybersecurity risk-management measures, and usually a SOC 2 criterion as well.
If each framework is handled on its own, the same review is described three times, checked three times and evidenced three times, and the copies drift apart. If the review is one measure linked to all three requirements, it is written once, checked by one control and evidenced by one set of records, and every framework sees the same result.
That is the chain in Acuna GRC: the requirement is the obligation, the measure is the practice that meets it, the control is the check that it works, and the task is the action someone performs.
How are the links made in Acuna GRC?
There are several ways in, and they all write the same links:
- On the measure itself, in the Measure Library of Implement, where the panel lists the linked requirements, controls, risks, records and tasks.
- By adopting reference measures from Common Measures in Comply. Each arrives in your Measure Library already linked to the requirements it maps to.
- On the Mapping page, which suggests links for orphan requirements and measures from the reference library, and with Run AI ranks candidates from your own library with a confidence score and a one-line reason. You apply them one by one, in bulk after a review sheet, or with Link all mapped for everything the catalog prescribes.
- With Aiko, by asking for example which measures a control should be linked to. Aiko proposes up to 20 links with a reason each, and larger jobs run as a bulk run of up to 2,000 records that you review before anything is applied.
Controls are linked to the measures they verify in the Related step of the Add Control wizard, and controls adopted from the repository arrive with suggested measures pre-checked.
How do you know nothing is left unlinked?
The Mapping page keeps two gap lists with live counts. Orphan Requirements shows every requirement with no measure, with its real framework reference. Orphan Measures shows every measure linked to no requirement, with green badges for the frameworks it covers and amber Missing badges where the catalog expects a link. A framework picker narrows the view, and an Include ignored switch brings back the orphans you dismissed on purpose.
A requirement that does not apply should be marked Not applicable with a justification rather than left as an orphan. It then shows an N/A badge and stays out of compliance KPIs. See how applicability marking works.
What travels along the links?
Two things: health and proof.
Health starts at the control, from whether it ran on time and from its tasks, and rolls up to the measure and then to every requirement linked to it, on a worse-wins rule. See how control health works.
Proof travels the other way. Records link to controls, measures and requirements, so an auditor can start from a clause and follow it to the measure, the control and the dated records that show the control ran. See how evidence lifecycle works.
Common mistakes: one measure per framework for the same practice, controls linked to no measure, links made once at the start and never revisited after a framework update, and orphans ignored without a reason.
How Acuna GRC handles it
- Core workspace
Implement
Requirements, the measures and controls that address them, and the business context of assets, third parties, processes, roles and staff.
- 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
Assure
KPIs and measurements, reports, records, audits, issues and corrective actions.
Sources
- ISO/IEC 27001:2022, Annex A 5.18
- Directive (EU) 2022/2555 (NIS2), Article 21(2)(i)
- Acuna GRC, Implement workspace
This page explains the rules in general terms and is not legal advice.
Frequently asked
What is a pivot suggestion on the Mapping page?
When two requirements from different frameworks are mapped to the same reference measure in the Common Measures library, Acuna GRC treats them as related, and the Mapping page uses that relation for its suggestions.
Does Aiko link records without review?
Not by default. Proposed links appear on a card or, for a bulk run, on a review page, and nothing is linked until you apply them. An administrator can allow Aiko to link directly, within built-in limits.
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)

