Topic starter
19/12/2025 11:28 am
TL;DR: Clarity Security says customers reclaimed 438,255 manual work hours in 2025 by automating 74,667 joiners, 113,628 movers, 6,252 leavers and 10.6 million review items, showing that manual identity governance still absorbs massive operational capacity. The governance problem is not just volume, but whether access decisions can keep pace with changing attributes, entitlements and lifecycle events.
Editorial analysis by NHI Mgmt Group, based on content published by Clarity Security: “2025 Year in Review: How Our Customers Reclaimed 438k Manual Work Hours”.
Key questions
Q: What breaks when identity governance processes rely too heavily on manual reviews and assessments?
A: Manual governance breaks down when access volumes grow faster than review capacity.
Q: Why does attribute-based access control reduce risk in cloud identity management?
A: ABAC reduces risk because access decisions are made from current attributes rather than static, long-lived grants.
Q: How do security teams know if lifecycle automation is actually working?
A: Measure removal completeness, not just provisioning speed.
Practitioner guidance
- Implement attribute-driven authorization policies Map access decisions to attributes such as role, location and device instead of relying only on static role membership.
- Automate joiner-mover-leaver workflows Tie onboarding, role change and offboarding directly to identity events so access changes happen when the business condition changes, not after manual review.
- Add decision context to access reviews Show reviewers the data points that justified access, including last login and termination dates, so certification decisions are evidence-based rather than role-label-based.
Bottom line: Manual identity governance remains a scale problem because access change, review and revocation still consume large amounts of human effort.
What's in the full article
Clarity Security's full article covers the operational detail this post intentionally leaves for the source:
- The full year-in-review breakdown of joiner, mover, leaver and review automation metrics.
- Product-specific descriptions of the ABAC engine and its lifecycle workflow changes.
- Expanded details on integrations, connectors and webhook-driven workflow triggers.
- The vendor's own framing of how audit trails and review UX changed for customers.
👉 Read Clarity Security's year-in-review on ABAC and autonomous identity governance →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 10 months ago by Abdelrahman
This topic was modified 5 days ago by NHI Mgmt Group
07/10/2026 6:08 pm
ABAC is becoming a governance control, not just an access model. The article is not really about replacing one provisioning style with another; it is about moving identity governance closer to the decision point. When access depends on role, location, device or lifecycle state, static roles become a lagging abstraction. Practitioners should treat ABAC as a control-plane change that reduces the gap between business context and authorization outcome.
A question worth separating out:
Q: Should non-human identities be included in access reviews?
A: Yes. Non-human identities can hold persistent access, reach sensitive systems, and outlive the business purpose that created them. If they are excluded from review, organizations leave a major blind spot in governance. Service accounts, API keys, tokens, and certificates should be reviewed with the same ownership and risk logic used for human users.
👉 Read our full editorial: ABAC and autonomous governance reshape identity reviews in 2025