Who owns orphaned service accounts after a resignation?

TL;DR: C1.ai shows that service account ownership often collapses at turnover because teams record creators, not accountable owners, so an employee departure can orphan dozens of NHIs. The governance failure is not discovery but continuity: ownership must survive personnel change or revocation, rotation, incident response, and offboarding all lose their control point.

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: What breaks when service account ownership is tied to the person who created it?

A: The model breaks at turnover.

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.

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.

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 →