What are KPI data sources in a GRC platform?
Direct answer
In Acuna GRC, a KPI takes its values from one of five sources: manual entry, computed values from live Acuna GRC data, a connector that pulls a metric from a connected service, an external API that receives values by webhook, or a group rollup from subsidiaries. Formula KPIs compute a ratio, a sum or a roll-up from other KPIs nightly.
In Acuna GRC, a KPI takes its values from one of five sources: manual entry for figures from outside the platform; computed values from live Acuna GRC data, using a curated source library or your own Aggregator query (object type, filters, grouping and aggregation); a connector that pulls a metric from a connected service; an external API that receives values by webhook; and, for a head office, a group rollup from subsidiaries. Formula KPIs compute a ratio, a sum or a roll-up from other KPIs and are written nightly. A warning threshold adds an amber band, and a compliance threshold shows how many items are compliant out of the total.
Why does a GRC programme need KPIs?
Because the standards ask you to measure, not only to describe. ISO/IEC 27001:2022 clause 9.1 requires you to determine what needs to be monitored and measured, the methods, when it is done, who does it, and when and by whom the results are analysed and evaluated, and to keep the results as documented information. Clause 9.3 then feeds monitoring and measurement results, audit results and the fulfilment of objectives into the management review.
The data source matters as much as the indicator. A figure retyped from a spreadsheet each quarter is slow, easy to get wrong and hard to defend. A figure computed from the records themselves, or pulled from the system that produces it, is current and traceable. Choosing the source is choosing how much of the measurement you can trust without checking it by hand.
Which data source fits which KPI?
In Acuna GRC, the create wizard starts with the data source, then asks for the title, target, frequency, owner, reviewer, chart type and scopes.
- Manual entry suits figures that live outside the platform and outside any connected service. Record KPI Measurement captures the value, the date, a series and notes.
- Computed values come from live Acuna GRC data, either from a curated source library or from your own Aggregator query: an object type, filters, a grouping and an aggregation. These KPIs snapshot their value on schedule, which builds the trend behind line and column charts.
- A connector pulls a metric from a connected service, for example a device compliance rate from Microsoft Intune. Each connector suggests its own KPIs. The first sync runs when you turn it on, then every 4 hours, and a measurement is recorded when the value changed.
- An external API receives values by webhook, and API v1 can record measurements one at a time or in a batch.
- A group rollup, in a head office, combines each subsidiary’s value of a group KPI with a method (On target, Sum, Average, Lowest or Highest) and a freshness window. Only the values are shared, never the records behind them.
Formula KPIs sit on top: a ratio, a sum of two to five KPIs, or a roll-up over a period. Once published, Acuna GRC writes the value nightly and nobody types one in.
How are targets, thresholds and history handled?
Each KPI has a target. A warning threshold adds an amber band, and a compliance threshold shows how many items are compliant out of the total. Clicking a value or a chart segment opens the list of items behind it, so a number can always be traced to the records that make it.
Measurements can be edited or deleted to correct the past, and the KPI shows the latest dated value. On the shared Assure dashboard, everyone sees the same widgets; administrators add, move, resize or remove them. A widget built on a module you do not have, or on records your access profile hides, is hidden rather than miscounted.
Where do KPIs feed the rest of the programme?
- Controls: a Target Value control can take its value from a KPI, so the KPI drives the control’s health. See how control health works.
- Objectives: a linked KPI shows its target status on the objective.
- Reports: a report section can show one of your KPIs, so the report and the dashboard always agree. Reports export as PDF or Excel, and each generation is kept as a snapshot.
- Compliance KPIs can be narrowed to the frameworks of your programme and their domains.
Common mistakes are easy to avoid: KPIs with no owner or reviewer, targets set once and never revisited, manual figures where a computed or connector source exists, and indicators that count activity rather than outcome. See the Assure workspace.
How Acuna GRC handles it
- Core workspace
Assure
KPIs and measurements, reports, records, audits, issues and corrective actions.
- 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.
- Core workspace
Operate
Risks and opportunities, threats, treatment plans, objectives, business impact analysis, tasks, the annual plan and documents.
Sources
This page explains the rules in general terms and is not legal advice.
Frequently asked
How often do connector KPIs update?
The first sync runs when the connector is turned on, then every 4 hours. A KPI metric records a new measurement when the value has changed.
Can one KPI be built from others?
Yes. A formula KPI computes a ratio, a sum of two to five KPIs, or a roll-up over a period. Once it is published, Acuna GRC writes its value nightly.
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)

