TL;DR: Opal Security argues that quarterly or yearly access reviews leave identity risk unmanaged between audits, while over-provisioning and privilege drift create exposure that point-in-time governance misses. Continuous monitoring, least privilege, and time-bound access turn identity management into an active security control rather than a compliance checkpoint.
Editorial analysis by NHI Mgmt Group, based on content published by Opal Security: “If Itâs Not Continuous, Itâs Not Secure: Reimagining Identity Management”.
Key questions
Q: What breaks when quarterly access reviews are used for non-human identities?
A: Quarterly access reviews break when applied to non-human identities because the control assumes stable identities, known ownership, and slow entitlement change.
Q: Why does over-provisioned access become more dangerous in healthcare identity environments?
A: Over-provisioned access increases the blast radius of human error, misuse, and compromised accounts.
Q: How should teams decide which access should be just-in-time?
A: Use just-in-time access for permissions that are high impact, infrequently needed, or sensitive enough that standing privilege creates unnecessary exposure.
Practitioner guidance
- Audit for access based on usage, not title Compare actual system usage to the access users currently hold, then remove entitlements that are justified only by job title, team, or inherited role.
- Introduce time-bound access for elevated permissions Replace standing elevated access with request-based access that expires automatically when the task or approval window ends.
- Continuous monitor for over-provisioned privileges Deploy monitoring that flags unnecessary privileged access in near real time so remediation starts before the next review cycle.
Bottom line: Identity programmes that rely on periodic reviews are blind to privilege drift between certification cycles, which is where much of the real exposure accumulates.
What's in the full article
Opal Security's full article covers the operational detail this post intentionally leaves for the source:
- Examples of how organisations can measure access usage against entitlement scope
- Discussion of how continuous monitoring can be paired with remediation workflows
- Specific guidance on building a least privilege council or identity security council
- The article's own positioning on continuous monitoring versus traditional identity governance
👉 Read Opal Security's analysis of continuous identity management and access drift →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Continuous identity management is a control-plane problem, not a review-cycle problem. Quarterly and yearly reviews were designed for compliance evidence, not for real-time privilege governance. That model fails when access state changes faster than certification cycles, because the programme is measuring yesterday's entitlement picture while the risk is happening today. The implication is that identity teams must treat access state as live security data, not audit residue.
A few things that frame the scale:
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: How can security teams know if cloud identity governance is actually working?
A: The clearest signals are fewer unresolved access findings, shorter evidence-collection cycles, lower counts of stale keys, and reduced reliance on manual review. If teams still spend days reconstructing access state, governance is not operating continuously. Effective programmes can show current MFA coverage, role scope, and credential age on demand.
👉 Read our full editorial: Continuous identity management is the missing control plane