An activity metric shows whether an identity process moved or completed, such as a certification being closed or a ticket being resolved. It is useful for operations, but it does not prove that access became safer, more appropriate, or better governed.
What activity metrics do well
Activity metrics are useful for showing throughput and completion: a review was closed, a ticket was resolved, a queue moved, or a workflow advanced. For identity operations, that makes them good operational telemetry because they show work is happening and where it is accumulating. They are not, by themselves, evidence that the underlying access decision was sound.
That distinction matters because a busy control can still be a weak control. A certification can be completed on time even if the reviewer rubber-stamped it, and a revocation ticket can be closed even if the access remained effective elsewhere.
Why activity metrics are often mistaken for control effectiveness
Teams frequently turn activity into a proxy for assurance because it is easy to count. A high closure rate, for example, may look healthy even when the quality of the decision is poor, the scope is incomplete, or the underlying entitlement model is stale. In governance terms, the metric measures motion, not correctness.
That is why activity metrics can coexist with risk. A process can be efficient and still fail to reduce exposure, especially when the actual outcome depends on judgment, entitlement accuracy, or follow-through after the task is marked complete.
How activity metrics should be interpreted
Use activity metrics as leading operational signals, not as proof of security outcome. They are most valuable when paired with outcome or quality measures that answer the harder question, such as whether access was reduced, exceptions were cleared, inappropriate permissions were removed, or recurring issues fell over time.
In practice, the same activity count can describe very different realities. Ten completed reviews may reflect disciplined governance, or it may reflect superficial review behaviour with no meaningful challenge to access.
This is why activity metrics should be read alongside evidence of decision quality, sample-based validation, and downstream effect. Without that context, they can flatter a control that has not actually improved.
Where activity metrics fit in governance and reporting
Activity metrics belong in operational reporting because they show volume, pace, and backlog movement. They help managers see whether a process is being executed and where resourcing or workflow issues may exist.
Their governance value is narrower. They can support management attention, but they should not be used alone for board-level assurance, risk acceptance, or claims that access has become safer. The stronger the governance claim, the more important it is to separate completed work from improved control.
When used well, an activity metric becomes a context measure: it tells you that the machine is turning. It does not tell you whether the machine is producing the right result.
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 and NIST CSF 2.0 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | CA-7 — Continuous Monitoring | Activity metrics support monitoring whether governance processes are operating. |
| Recommendation — Track process completion and backlogs as monitoring evidence, but pair them with effectiveness checks. | ||
| NIST CSF 2.0 | GV.OV-01 — Oversight of Cybersecurity Risk Management | Governance oversight needs metrics that distinguish activity from actual risk reduction. |
| Recommendation — Use oversight reporting to verify that control activity translates into measurable risk reduction. | ||
| ISO/IEC 27001:2022 | A.5.36 — Compliance with policies, rules and standards for information security | Activity metrics often report policy and process execution, which needs governance review. |
| Recommendation — Review execution metrics alongside evidence that the underlying policy objective was achieved. | ||
Related resources from NHI Mgmt Group
- How should security teams monitor AI agent activity without disrupting developers?
- How can SOC teams use identity context to improve response to agent activity?
- What is the difference between activity metrics and risk metrics in IAM?
- How can organisations tell legitimate automation from compromised service account activity?
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 October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org