Join our Newsletter — 33% off our NHI Course

How did Access reviews miss AI-connected identities for years?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: Orphaned, idle, exposed and non-expiring machine credentials can stay active for years without formal oversight, according to SailPoint. Machine identity governance breaks when review scopes do not account for ownership and expiry assumptions.

Editorial analysis by NHI Mgmt Group, based on content published by SailPoint: “Bringing access reviews to your non-human identities”.

Key questions

Q: Why do certificates create governance issues for non-human identities?

A: Because certificates are often attached to devices, servers, APIs, and service accounts that do not behave like people.

Q: How should IAM teams prioritise which non-human identities to review first?

A: Start with credentials that are orphaned, idle, exposed, non-expiring, former-employee-linked, high-risk, or over-permissioned.

Q: What breaks when access reviews do not include machine and AI identities?

A: Review cycles miss the identities that often move the most data and inherit the most privilege.

Practitioner guidance

  • Define NHI certification scopes by risk signal Build campaigns around orphaned, idle, exposed, non-expiring, former-employee-linked, high-risk, and over-permissioned credentials so reviewers see a bounded set.
  • Assign explicit ownership before review begins Require every service account, machine token, and API key in scope to have a named attester or fallback owner before it enters certification.
  • Separate easy remediation from owner review Disable idle credentials, reassign obvious ownership, and capture provider-console instructions before escalating unresolved items to developers.

Bottom line: Machine identity access reviews fail when organisations reuse human certification processes without redesigning ownership and expiry assumptions.

Glossary terms: Non-Human Identity Credentials, Orphaned Credential, Long-Lived Secret, Access Certification Campaign

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Human-style certification is the wrong control model for machine identities: access review programmes were designed around people, not service accounts, API keys, and workload tokens. The article exposes a governance gap that appears when reviewers are asked to certify access that has no clear human owner, no HR record, and no natural business narrative. Practitioners should treat that as a control-design problem, not a process exception.

A few things that frame the scale:

  • 80% of identity breaches involved compromised non-human identities such as service accounts and API keys, according to the Ultimate Guide to NHIs.

A question worth separating out:

Q: How do organisations make NHI access reviews auditable?

A: They need a campaign record that shows who reviewed each credential, what decision was made, what action followed, and when the item closed. That evidence turns certification into a defensible governance control instead of an informal checklist.

👉 Read our full editorial: Human review cadences do not fit machine identity governance


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

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.