How does control health scoring work in Acuna GRC?
Direct answer
In Acuna GRC, health is a computed status (Healthy, At risk, Unhealthy or Unknown) that nobody sets by hand. It starts at the control, from whether it ran on time and from its recurring tasks, and rolls up to measures and requirements on a worse-wins rule, so a strong result in one area cannot hide a failure in another.
A measure's health combines three dimensions: design, operating (its linked controls) and documentation (its linked documents being current). The Health tab on a control shows which dimension drags the score down and follows the chain to the failing input.
Why compute health instead of asking people for a status?
A status that someone types in reflects what they believe on the day they type it. Frameworks ask for more than that. ISO/IEC 27001:2022 requires you to determine what to monitor and measure, including information security processes and controls, and to evaluate the results (clause 9.1). NIS2 lists, among the measures of Article 21(2), policies and procedures to assess the effectiveness of cybersecurity risk-management measures (point f).
Acuna GRC therefore keeps two kinds of value apart:
- Compliance status and maturity are deliberate assessments that you set on a requirement or a measure.
- Health is computed from those assessments and from what is actually happening below: controls run on time, tasks done, documents current. Nobody can set it by hand.
The gap between the two is often the most useful thing on the screen: a requirement assessed as compliant whose controls have stopped running.
What feeds the health of a control?
Health originates at the control. A control is a verification activity with a frequency, and each control is judged in one of three ways, shown in the Type column of the Control Library:
- Record Completion: judged on the completion of its record.
- Target Value: a value is compared with a target. The value is entered by hand, taken from a KPI or pulled by a connector.
- Checklist: sections and items answered and signed per run, on a computer or a phone. Completing a run creates one record with a PDF of the signed run.
Whether the control ran on time and whether its recurring tasks were completed then set its health. Connectors can do part of this for you: a control metric from a connected service records a pass or a fail, which updates the control’s health and moves its next due date once it is due. See how recurring tasks work.
How does health roll up from controls to requirements and risks?
Every level uses the same worse-wins rule, so a strong result in one place cannot hide a failure in another:
- A measure’s health combines three dimensions: design, operating (its linked controls) and documentation (its linked documents being current). The weakest dimension sets the result.
- A requirement’s health rolls up from its linked measures and controls. Requirements show Healthy, At Risk, Unhealthy, N/A or Unknown.
- A treatment plan’s health is computed from its linked controls, measures and tasks and rolls up into the risk it treats.
- An objective surfaces the health of the controls and measures linked to it.
Because one measure can serve requirements in several frameworks, one failing control shows on every requirement that depends on it, in ISO 27001, NIS2, SOC 2 or a custom framework alike. See how measures and controls link to requirements.
How do you find and fix what drags health down?
Open the Health tab on the control. It shows which dimension drags the score down and follows the chain to the failing input: an overdue task, a missed execution, a value below target, or a document past its review date. Aiko can also list items by health when you ask, for example which controls are unhealthy.
The common causes are ordinary:
- A recurring task that nobody completed, often because its assignee left or changed role.
- A control with no schedule, or a schedule nobody owns.
- A policy linked to a measure that passed its yearly review date, which pulls down the documentation dimension.
- A connector that stopped syncing, so a Target Value control has no fresh value.
Where the cause is a real weakness rather than a missed step, log it as an issue and open a corrective action, so the fix is tracked to verification in Assure.
How Acuna GRC handles it
- Core workspace
Assure
KPIs and measurements, reports, records, audits, issues and corrective actions.
- Core workspace
Operate
Risks and opportunities, threats, treatment plans, objectives, business impact analysis, tasks, the annual plan and documents.
- Module
Integrations and API
Connect Acuna GRC to the security, identity, device, HR, cloud, code, scanner and ticketing tools you already run, with webhooks and an API.
Sources
- ISO/IEC 27001:2022, clause 9.1
- Directive (EU) 2022/2555 (NIS2), Article 21(2)(f)
- Acuna GRC, Implement workspace
This page explains the rules in general terms and is not legal advice.
Frequently asked
Can an administrator override a health status?
No. Health is always computed. What people set by hand are compliance status and maturity, and those feed the computation alongside what controls, tasks and documents actually do.
Does a requirement marked Not applicable affect health?
It shows an N/A badge and stays out of compliance KPIs, with the justification recorded. It does not count against the figures of the requirements that apply.
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)

