TL;DR: C1.ai's analysis of service account ownership finds teams often record creators instead of accountable owners, so turnover can orphan non-human identities. Governance has to survive personnel change or downstream controls lose the person who can act on the identity.
Editorial analysis by NHI Mgmt Group, based on content published by C1.ai: “Who Owns a Service Account After Its Owner Leaves?”.
Key questions
Q: Why do orphaned service accounts create a governance problem, not just an inventory problem?
A: Because inventory tells you what exists, but governance requires someone who can approve rotation, revoke access, and explain business impact.
Q: How should organisations structure NHI ownership so it survives staff turnover?
A: Use role- or team-backed ownership with a named individual attached to the role, then make reassignment a mandatory step in offboarding.
Q: What breaks when service account ownership is tied to the person who created it?
A: The model breaks at turnover.
Practitioner guidance
- Define accountable ownership for every service account Assign each NHI to a team or role with a named individual responsible for review, escalation, and lifecycle decisions.
- Make ownership transfer part of offboarding Do not close a departure until all identities tied to the leaver have been reassigned and validated by the receiving owner.
- Separate creator fields from owner fields Keep creation history, technical steward, and accountable owner as distinct attributes so turnover does not blur responsibility.
Bottom line: Service account ownership fails when organisations record who created an identity instead of who remains accountable for it.
Glossary terms: NHI Ownership, Orphaned Identity, Ownership Continuity, Creator Versus Owner
What's in the full article
C1.ai's full blog post covers the operational detail this post intentionally leaves for the source:
- The three ownership models discussed for service accounts and how each behaves under turnover
- The offboarding pattern that reassigns NHIs before a departure is considered complete
- The distinction between creator history and accountable ownership in NHI governance
- The way teams can keep service accounts, API keys, and automation linked to a responsible owner
👉 Read C1.ai's analysis of service account ownership and orphaned NHIs →
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Ownership is the control plane for every other NHI control: revocation, rotation, incident response, and offboarding all fail when there is nobody accountable to act. C1.ai's example is useful because it shows the operational truth that discovery alone does not create governance. The real question is not whether the account exists, but whether someone can still answer for it after personnel change. The practitioner lesson is to make accountability a live control, not a directory field.
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.
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: How do teams know if NHI governance is actually working?
A: Look for complete inventory coverage, clear ownership, enforced rotation, and reliable decommissioning. If new credentials appear faster than they are classified, or if stale secrets stay valid after workload changes, the programme is not governing machine identities effectively.
👉 Read our full editorial: Service account ownership fails when the owner leaves