Use a mix of behavioural and activity signals, then look for change over time rather than a single score. Completion rates tell you whether people attended training, but they do not show whether behaviour changed. Combine reporting behaviour, simulation outcomes, intervention response and group-level trends to understand where exposure is actually falling.
What to measure instead of completion rates
Completion data is a participation metric, not a behaviour metric. If you want to understand human cyber risk, measure what people actually do when they encounter suspicious content, policy friction, or a real decision point. The most useful signals are reporting behaviour, simulation outcomes, response to interventions, and whether those measures improve or deteriorate over time.
That means combining leading indicators and outcome indicators. A reporting rate can show whether people escalate suspicious messages, while simulation results can show susceptibility and follow-through. Pair those with time-to-report, repeat clickers, refusal to use unsafe workarounds, and changes by team or role so you can see where exposure is concentrating rather than assuming training attendance reduced risk.
Use Security Culture Measurement Guide when you need a practical model for using reporting rate, time-to-report and survey data together instead of relying on one number.
How to build a usable human risk signal
Start with a small set of signals that reflect behaviour, not awareness alone. Good candidates include phishing reporting rate, click or submission rate in simulations, time to report, completion of just-in-time nudges, and whether users who were exposed to an intervention changed their later behaviour. The point is to detect movement in risk, not to declare a person safe or unsafe from a single event.
Normalise those signals by group and context. A team that handles more external email or customer contact will often generate different patterns from a back-office team, so compare like with like. Track trends at the team, role, or business-unit level, because group-level patterns are usually more actionable than a single individual score.
Use Human Risk Management Programme Guide for the telemetry and intervention model that supports behaviour-based measurement beyond annual awareness cycles.
For a broader programme baseline, Security Awareness and Human Risk Management Guide covers behaviour change, metrics and culture in one operating model.
How to interpret trends without overreading the data
Look for directional change, persistence and concentration. One bad simulation result does not tell you much, but repeated failures after a targeted intervention can show that the control is not sticking. Likewise, a strong reporting rate with a slow time to report may mean people are willing to help but still need better recognition and triage habits.
Be careful with averages. A programme can look healthy overall while a few high-risk groups remain unchanged, or while repeat offenders account for a disproportionate share of exposure. That is why the most useful view is usually a trend line plus segmentation, not a single enterprise score.
Use Security Culture Measurement Guide again when you need to distinguish a true behavioural shift from a temporary metric fluctuation.
Risk and Threat Considerations
Human-risk measurement fails when organisations optimise for easy-to-collect metrics instead of exposure-reducing behaviour. Completion rates can create false confidence, while weak reporting habits, repeated simulation failures, and poor response to nudges leave the real attack surface unchanged.
Failure mechanism: The metric tracks attendance or awareness but not action, so teams miss persistent susceptibility, slow escalation, and concentrated exposure in specific roles or groups.
Impact: Leadership may underinvest in targeted controls, miss repeat patterns, and overestimate the protective value of awareness activity.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, NIST CSF 2.0 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AT-2 — Awareness Training | Human-risk measurement supports evaluating whether awareness activities change behaviour. |
| AT-3 — Role-Based Training | Role-specific trends and interventions depend on training matched to job context. | |
| Recommendation — Measure behaviour change to validate awareness training effectiveness. Tailor training and measurement to role-based exposure patterns. | ||
| NIST CSF 2.0 | PR.AT-01 — Awareness and Training | The topic concerns how to assess whether awareness efforts change user behaviour. |
| Recommendation — Track behavioural outcomes, not completion alone, for awareness effectiveness. | ||
| CIS Controls v8 | 14 — Security Awareness and Skills Training | CIS 14 is directly about improving security awareness and measuring programme effectiveness. |
| Recommendation — Use outcome metrics to show that awareness efforts reduce risky behaviour. | ||
| ISO/IEC 27001:2022 | A.6.3 — Information security awareness, education and training | The question is about proving awareness and education reduce human-risk exposure. |
| Recommendation — Record behavioural evidence that awareness activities are changing risk. | ||
Practitioner Guidance
What to prioritise: Measure the behaviours that change attacker success or defender detection first, especially reporting, response time and repeat failure patterns. If a metric does not help you change a control, an intervention, or a target group, it is probably reporting vanity rather than risk.
What to verify: Check that the data source captures behaviour at the point of decision, not just training attendance. A good dashboard should let you answer whether risk is falling, where it is falling, and whether an intervention changed anything after the fact.
Practitioner takeaway: The best human-risk programmes treat measurement as a feedback loop for behaviour change, not as a compliance record of who completed training.
Related resources from NHI Mgmt Group
- How should security teams measure human risk programmes beyond training completion?
- How should organisations govern human cyber risk beyond awareness training?
- How should schools and universities reduce cyber risk beyond awareness training?
- Why do completion metrics fail as a measure of human cyber risk?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 9, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org