What does the Comply workspace do in Acuna GRC?
Direct answer
Comply is the Acuna GRC workspace where you define your compliance programme. Administrators adopt frameworks from the library or import custom ones, you tick the requirements that apply and assign each framework to scopes, and you adopt reference measures from the Common Measures library, already mapped to requirements across frameworks.
The Mapping page lists orphan requirements and orphan measures with suggestions, including AI-ranked candidates with a confidence score, and applies links in bulk. With Data Privacy on, Comply also holds your applicable privacy laws. The daily work on requirements, measures and controls then happens in Implement.
What does defining a compliance programme involve?
Before anyone writes a policy or runs a control, three decisions shape the programme:
- Which frameworks apply: a certification you seek, a regulation you fall under, a contract that requires one.
- Where each one applies: ISO/IEC 27001:2022 asks you to determine the boundaries and applicability of the ISMS to establish its scope (clause 4.3), and regulations such as NIS2 or DORA apply to specific entities and services.
- Which requirements apply within that scope, and why the others do not. See how applicability marking works.
When several frameworks apply at once, the fourth decision is how to avoid doing the same work several times. Most frameworks ask for overlapping practices, such as access reviews, backups, incident handling and supplier oversight, and one well-defined measure can serve all of them.
How do frameworks, scopes and tags work in Comply?
Your Frameworks lists what you have adopted. An administrator opens the Library tab, searches it and adopts a framework, or imports one already adopted under a different name. A custom framework can be imported from a CSV file (Reference, Level, Title, Description and an optional NodeType) under Admin, or prepared by the Acuna GRC team. Several frameworks make one programme with a single measure and control library.
Scopes mirror your organisation. Each has a name, a type (Geographic, Business Unit, Legal Entity, Product Line, Department, Site or Other), an optional parent, a colour and a description. Scopes nest, and a Global scope exists from the start. You assign frameworks, requirements and any record to a scope, and the global scope filter in the top bar then limits every table, dashboard and detail view to the chosen scopes, follows you between modules and pre-assigns new records.
Tags are free labels for filtering across modules. In an access profile, a profile restricted to scopes sees only those scopes, and unchecking a tag hides every record carrying it.
How does Comply close coverage gaps across frameworks?
Two pages do the work:
- Common Measures is a curated, read-only library of reference measures recommended for your frameworks, grouped by domain. 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.
- Mapping lists Orphan Requirements, with no measure linked, and Orphan Measures, linked to no requirement, with live counts. Suggestions come from the reference library, and Run AI ranks candidates from your own library with a confidence score and a one-line reason. You apply links one by one or in bulk, ignore an intentional orphan (hidden, never deleted), or connect everything the catalog prescribes with Link all mapped.
Two requirements from different frameworks mapped to the same reference measure count as related, which is what powers the cross-framework suggestions. See cross-framework control mapping.
What else is set up in Comply?
With the Data Privacy module on, Privacy Laws holds the privacy frameworks that apply to you. Before the first save, the page proposes those already in your programme. The selection drives the legal bases on processing activities, the ROPA wizard tabs, the privacy dashboard figures, the citations on generated privacy documents and the wording of privacy portal emails.
Where the compliance roadmap is switched on for your organisation, Roadmap setup offers a curated path per framework: ordered steps in phases, each recommending tasks, controls, measures, documents, KPIs, risks, objectives, roles and responsibilities. You tick what you want, and Approve & seed creates it all in one pass with the links between items. A docked panel then tracks each step as Done, Blocked or Not created yet while you work in Implement and Operate.
A typical start: adopt the frameworks, create the scopes, adopt the recommended Common Measures, then work through the orphan requirements in Mapping. See the Comply workspace.
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
Can we add a framework that is not in the library?
Yes. An administrator imports it from a CSV file with Reference, Level, Title, Description and an optional NodeType column, or asks the Acuna GRC team to prepare it.
What is the difference between Comply and Implement?
Comply defines the programme: frameworks, scopes, common measures, mapping, privacy laws and the roadmap. Implement builds it: requirements assessed one by one, the measure and control libraries, and the assets, third parties, processes and people they depend on.
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)

