What does the Implement workspace do in Acuna GRC?
Direct answer
Implement is the Acuna GRC workspace where you put the programme in place. It holds the requirements of your adopted frameworks, the Measure Library and the Control Library, and the context the programme depends on: assets, third parties, processes, staff, roles and responsibilities.
You set compliance status, maturity and owners on each requirement; measures address requirements across frameworks, and controls, built with a wizard or adopted from a curated repository, verify those measures on a schedule. Acuna GRC computes health from what the controls actually do and rolls it up to the requirement, and a RACI matrix shows who is responsible for what.
What does putting a compliance programme in place involve?
Once the frameworks and their scope are chosen, each requirement needs an answer: is it met, how mature is the practice behind it, who owns it, and how do you know it works. ISO/IEC 27001:2022 asks for this in several places: roles, responsibilities and authorities assigned and communicated (clause 5.3), and the processes needed to meet the requirements planned, implemented and controlled (clause 8.1).
In Acuna GRC, requirements arrive from the frameworks adopted in Comply. You browse them as a tree by framework domain or as a flat table, and set compliance status, maturity, justification, owners (people or roles) and comments from the row, or in bulk. Those two assessments are yours to set. Health is computed beside them, as Healthy, At Risk, Unhealthy, N/A or Unknown.
How do the measure and control libraries work?
The Measure Library holds the practices that meet requirements. Each measure has a reference, title, category, implementation status, maturity, owner and computed health, and its panel lists linked requirements, controls, risks, records and tasks. One measure can address clauses in several frameworks.
The Control Library holds the checks that those practices work:
- Add Control walks through Basics, Effectiveness, Target or Checklist, Schedule, Related and Review. A due control appears in its owner’s My Actions.
- Each control is judged by Record Completion, a Target Value (entered by hand, from a KPI or from a connector) or a Checklist.
- Checklists have sections and items (checkbox, choice, number, text) and published versions. A run is answered and signed item by item, on a computer or a phone, and creates one record with a PDF of the signed run.
- Add from repository adopts controls from the curated Acuna GRC catalog, filtered to your frameworks, with suggested measures pre-checked.
Why does Implement also hold assets, third parties and processes?
Because risks, continuity and controls all depend on them, and keeping them in the same place keeps the links alive.
- Assets carry a Confidentiality, Integrity, Availability and Traceability classification that feeds risk and the business impact analysis, recovery objectives (RTO, RPO and MTPD) and a data residency country.
- Third parties have an Info tab and an Exposure tab with risk level, exposure factors and the Contains PII, Contains IP and Uses AI declarations, named contacts, and a Supply Chain tree of subcontractors. With the TPRM module, suppliers are the same register in a second view.
- Processes form a tree of sub-processes with owner, type, criticality, status, classification, RTO, RPO and MTPD, and an In BIA scope switch.
The Visualizer draws assets, processes, third parties, risks, staff, categories and locations as a 3D graph. Click a node to light up its direct connections, and look for isolated objects to review and bridge nodes that show shared dependencies.
How does Implement show who is responsible for what?
Staff lists people with name, email, position and roles, or pre-filled from a connected Microsoft Entra directory. A No login badge shows who has no platform account, and each person’s linked objects panel groups everything they own, review or approve.
Roles are organisational functions independent of the people filling them, and responsibilities are duties assigned to a role or a person. Each link carries a RACI value: A, R, A/R, C or I. The RACI matrix shows responsibilities as rows and roles and staff as columns, warns on a missing or double A, and exports to XLSX.
Common mistakes at this stage: owners named as a team rather than a role or a person, controls with no schedule, measures written but linked to no requirement, and context records (assets, suppliers, processes) entered once and never linked. See the Implement workspace.
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
Operate
Risks and opportunities, threats, treatment plans, objectives, business impact analysis, tasks, the annual plan and documents.
- Core workspace
Assure
KPIs and measurements, reports, records, audits, issues and corrective actions.
Sources
This page explains the rules in general terms and is not legal advice.
Frequently asked
Do we have to write every control ourselves?
No. Add from repository adopts controls from the curated Acuna GRC catalog, filtered to your frameworks, with the suggested measures pre-checked. You then adjust the owner, schedule and test to fit your organisation.
Can the staff list come from our directory?
Yes. With a connected Microsoft Entra directory, the staff register is pre-filled, and you can invite people who have no platform account from their record.
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)

