TL;DR: 20 to 1 is the scale CyberArk cites for non-human identities over human identities. That ratio shows why ownership, regular review, and least privilege become the controls that keep machine accounts governable.
Editorial analysis by NHI Mgmt Group, based on content published by CyberArk: “Strategies for Managing Non-Human Identities”.
Key questions
Q: Why do service accounts and workloads become overprivileged over time?
A: They usually inherit access for a launch or integration and then keep it long after the original purpose changes.
Q: How should security teams run access reviews for non-human identities?
A: Security teams should scope reviews by risk pattern, assign every identity to an accountable owner, and require a documented decision for each item in scope.
Q: What breaks when non-human identity ownership is unclear?
A: When ownership is unclear, rotation stalls, reviews default to approval, and nobody feels safe removing access.
Practitioner guidance
- Assign accountable owners to every NHI Build a process that records a named human owner, a business purpose, and a review cadence for each service account, bot, API token, or integration identity.
- Automate recurring NHI access reviews Review machine identities on a quarterly or more frequent schedule, and verify purpose, entitlements, and whether the identity is still in use.
- Reduce standing privilege on machine identities Remove permissions that are no longer required for the current workload, and revalidate access when the role or integration changes.
Bottom line: The article's central warning is that non-human identities become risky when organisations cannot assign owners, review access, and narrow permissions as workloads change.
Glossary terms: Least Privilege, Non-Human Identity (NHI), Access Review, Orphaned Identity
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Ownership is the first NHI control, not a governance afterthought. Machine identities do not become safe because they are technical rather than human. The governance failure begins when the organisation cannot name a responsible human owner who can answer why the identity exists, who should review it, and when it should be retired. That makes accountability the prerequisite for every other NHI control.
A few things that frame the scale:
- NHIs outnumber human identities by 25x to 50x in modern enterprises, according to the Ultimate Guide to NHIs.
- 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: Should organisations treat NHIs differently from human users in IAM?
A: The governance rules are similar, but the operating model is different. NHIs need owner mapping, entitlement review, and least privilege just like human users, but they also need machine-aware lifecycle controls because they can be created in bulk, hidden inside integrations, and forgotten when applications change. Treat them as first-class identities, not as invisible infrastructure.
👉 Read our full editorial: Managing non-human identities requires ownership, review, and least privilege