Topic starter
24/06/2026 7:27 pm
TL;DR: Ghost agents can stay active after their creator leaves, 1Kosmos reports, because their API keys, service accounts, or tokens are still valid outside standard offboarding. Runtime governance has to reach the agent itself, or orphaned access keeps producing decisions with no current owner.
Editorial analysis by NHI Mgmt Group, based on content published by 1Kosmos: “The Ghost Agent Problem: When Employees Leave But AI Agents Keep Running”.
Key questions
Q: Why do offboarding and access review controls miss ghost agents?
A: They are built to govern people, not separate runtime identities.
Q: How should organisations stop AI agents after the creator departs?
A: They should bind agent credential issuance to the creator’s active status and deny fresh credentials the moment that owner is offboarded.
Q: What breaks when an AI agent outlives the employee who created it?
A: The break point is accountability.
Practitioner guidance
- Map every AI agent to a named human owner Build a complete inventory of agents, the systems they can touch, and the employee accountable for each one.
- Tie credential issuance to active employment status Require the authentication layer to check whether the owner is still active before issuing any new agent credential.
- Add agent offboarding to JML workflows Extend joiner-mover-leaver procedures so they include non-human identities created by the employee, with explicit decommissioning steps for API keys, service accounts, and OAuth tokens.
Bottom line: Ghost agents are a governance failure mode where an AI system keeps acting after its human creator is offboarded.
Glossary terms: Runtime Governance, Shadow Agent, Orphaned Identity, Ownership Assumption Collapse
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 1 hour ago by NHI Mgmt Group
25/06/2026 4:43 am
Ghost agents expose a runtime governance gap, not just a lifecycle gap: the failure is that IAM can end a person's access while leaving the agent's access untouched. That separation matters because the control boundary sits at credential issuance and runtime enforcement, not at employee offboarding. The practitioner conclusion is that AI identity must be governed as its own runtime subject, not as a side effect of human JML.
A few things that frame the scale:
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them, according to the Ultimate Guide to NHIs.
- 70% of organisations grant AI systems more access than they would give a human employee performing the exact same job, according to the 2026 Infrastructure Identity Survey.
A question worth separating out:
Q: When should organisations separate AI agent governance from human IAM reviews?
A: Organisations should separate them as soon as AI agents begin acting inside production workflows. Human access reviews assume a person, a role, and a review cadence that fit a stable entitlement. AI agents require task-scoped boundaries, lifecycle ownership, and monitoring that can keep up with runtime behaviour.
👉 Read our full editorial: Ghost agents expose a runtime governance gap in AI identity