Topic starter
06/11/2026 6:37 pm
TL;DR: Identity controls built for people break when personal and autonomous agents inherit authority, because a phished user can make every dependent agent dangerous and an abandoned agent can keep acting after its sponsor leaves, according to Newcore. Accountability has to follow the agent chain, not just the login.
Editorial analysis by NHI Mgmt Group, based on content published by Newcore: “Securing the Modern Workforce: People, Personal Agents, and Autonomous Agents”.
Key questions
Q: How should teams govern agent actions that run under a human's authority?
A: Govern agent actions by binding each agent to a named human owner, a scoped service account or OAuth/OIDC grant, and explicit allow-listed tools, data sets and runtime limits.
Q: What breaks when agent approval workflows are the only control on autonomous actions?
A: Approval-only models fail when the agent can assemble and execute a sequence too quickly for review to be meaningful.
Q: How do I offboard an AI agent when its owner leaves the organisation?
A: Offboard an AI agent by revoking its tokens, API keys, certificates and refresh grants, disabling its service account or workload identity, and transferring ownership of any queues, automations and secrets it can reach.
Practitioner guidance
- Define one accountable owner per agent Assign a named human owner to every production agent, including agents created by other agents, and make that ownership visible in the identity record.
- Tie agent access to owner risk signals Propagate compromise, anomalous behaviour, and role-change signals from the person to every agent acting under that person's authority.
- Put lifecycle decisions in place before role changes Decide in advance what happens to each agent when its owner changes teams or leaves, including whether the agent pauses, transfers, or is retired.
Bottom line: Agents that act on a person's authority create a governance problem that classic human identity controls do not fully cover.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
06/11/2026 6:41 pm
Identity governance for agents is now a delegation problem, not just an authentication problem. The source framing shows that the dangerous unit is no longer the logged-in person alone, but the person plus every agent executing under their authority. That means access reviews that only certify human accounts miss the real acting surface. Practitioners should govern the delegation chain as the identity boundary, not the login screen.
A few things that frame the scale:
- Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption, according to the 2026 Infrastructure Identity Survey.
- Claude Code-assisted commits leaked secrets at a rate of 3.2%, more than double the human-only baseline of 1.5%, with peaks reaching 31 secrets per 1,000 commits in August 2025, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: What is the best way to detect risky agent behaviour in identity logs?
A: Detect risky agent behaviour by correlating identity logs across authentication, tool use, data access and privilege changes, then flagging anomalies such as unusual call volume, new destinations, repeated denials or access outside approved hours. Good identity logs include the agent identity, the human owner, the credential used, the resource touched and the decision outcome, so policy violations and compromise are visible.
👉 Read our full editorial: Identity controls break when agents outlive their human owners