IAM teams should treat activity data as a decision support signal, not an automatic approval or denial rule. Use last-use dates, login frequency, and peer comparisons to validate whether access is still needed, then document the business reason when an entitlement remains despite low use. That makes certifications more defensible and less dependent on assumption.
Using activity data as evidence, not verdict
Activity data helps IAM teams answer a narrower question than the access review itself: is there enough observable use to justify keeping the entitlement? The strongest practice is to treat usage signals as corroboration, then combine them with manager input, system ownership, and business context before making a certification decision.
That matters because inactivity can mean several different things. A permission may be dormant because the role is correct, because a process runs only monthly or quarterly, or because the user has shifted work without the entitlement being removed. The review should test those possibilities rather than turning low usage into an automatic removal trigger.
When a permission is retained despite weak or absent usage, the review record should show why. That could be a temporary project need, periodic operational access, an exception approved by the business owner, or a delegated function that does not produce frequent logins. The point is to make the decision explainable and repeatable, not purely pattern-driven.
Which activity signals are useful in certification campaigns?
Last-use dates are often the most direct signal, but they are only one part of the picture. Login frequency, recent privilege use, and comparison with peers in the same role can show whether the entitlement is consistent with normal behaviour or looks like excess access. Used well, these signals help reviewers focus on entitlements that deserve challenge first.
Peer comparison is especially useful when reviewers face large certification volumes. If most users in a role never touch a sensitive entitlement, that may indicate the access is overbroad or the role model is stale. If most peers use it sparingly but predictably, low frequency may simply reflect the task cycle rather than unnecessary access.
Activity data is also stronger when it reflects the specific entitlement under review, not just a generic account heartbeat. A recent login can show the account is active without proving the entitlement is needed. A cleaner review process looks for evidence of actual use of the permission, function, system, or dataset rather than treating any sign-in as proof of necessity.
For teams building repeatable review processes, it helps to standardise which signals are exposed to reviewers and how they are interpreted. Access Reviews and Certification Guide is useful here because it focuses on cutting review volume, adding context, and avoiding rubber-stamping while still closing the loop on decisions.
How should teams avoid false confidence from activity data?
Low activity does not always mean access is unnecessary, and high activity does not always mean access is appropriate. The main failure mode is confusing observability with legitimacy: a permission can be heavily used and still violate least privilege, separation of duties, or role expectations. Activity should therefore support the review, not replace the entitlement question.
Another common problem is stale context. Activity snapshots can reflect a one-off period, a recent incident, or a temporary assignment that no longer exists. Reviews become more defensible when they use a defined observation window, compare with the entitlement's intended purpose, and require an explicit business reason for exceptions.
When IAM teams review non-human or service access alongside human access, they should be even more careful about interpreting usage. An entitlement may be used by automation on a schedule, by a service during an incident, or by a workload that has no human-style login pattern. That makes the business justification and ownership record more important than simple frequency counts. IAM and IGA Basics is a good companion for the governance model behind those decisions, and NHI lifecycle management helps when the same review logic is applied to machine and service identities.
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 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 | AU-6 — Audit Review, Analysis, and Reporting | Activity data in access reviews depends on reviewing usage evidence to support access decisions. |
| AC-2 — Account Management | Access reviews are part of account and entitlement lifecycle governance. | |
| IA-5 — Authenticator Management | Usage evidence often includes credential and session behavior that informs whether access remains warranted. | |
| Recommendation — Analyze access activity to support entitlement decisions and exception handling. Review account and entitlement necessity on a defined cadence. Track authenticator use and retire unnecessary credentials promptly. | ||
| CIS Controls v8 | CIS-5 — Account Management | Certification campaigns and activity-based review are core account management safeguards. |
| Recommendation — Periodically validate account necessity and remove stale access. | ||
| ISO/IEC 27001:2022 | A.5.15 — Access control | Activity-informed certification supports access governance under ISO 27001 Annex A. |
| Recommendation — Apply access control reviews with documented justification for retained access. | ||
Practitioner Guidance
What to prioritise: Start with entitlements that are both high-risk and hard to justify from the available activity trail, especially privileged access, sensitive data access, and cross-environment access. Those are the cases where the review outcome changes real exposure, not just hygiene.
What to verify: Require reviewers to see the relevant activity context, not just a raw last-login date. The useful test is whether the evidence shows use of the specific entitlement in a way that matches the stated business purpose, with an exception note when it does not.
Decision rule: If the entitlement is low-use but still business-critical, keep it only when the owner can state why it must remain and for how long. If neither the usage pattern nor the business reason is credible, treat the entitlement as a removal candidate, not a pass-by-default item.
Practitioner takeaway: Activity data improves access reviews most when it makes the decision harder to rubber-stamp, not when it is treated as a proxy for approval. The best reviewers use it to challenge assumptions, then force a documented business justification whenever the entitlement survives the evidence.
Related resources from NHI Mgmt Group
- When should organisations prioritise data access governance over more IAM roles and reviews?
- How should identity teams use activity monitoring to improve access reviews?
- How should security teams use identity data connectors to support access reviews across SaaS and on-premises systems?
- How should IAM leaders use AI and data science to modernise access provisioning without adding more manual approval bottlenecks?
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 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org