Topic starter
11/10/2026 6:57 pm
TL;DR: As AI agents move into real workflows, logs alone cannot explain who initiated an action, which agent acted, what authority it had, or how delegation changed along the way, according to Newcore. The missing control is operational lineage, which turns agent activity into attributable, scoped, and verifiable identity evidence.
Editorial analysis by NHI Mgmt Group, based on content published by Newcore: “Who Told the Agent to Do That? Proving Operational Lineage for AI Agents”.
Key questions
Q: What breaks when AI agents do not have operational lineage?
A: Accountability breaks because the organisation can no longer prove who initiated the action, which agent executed it, or whether the authority used was actually in scope.
Q: Why do delegated credentials matter for agentic systems?
A: Delegated credentials preserve the distinction between the human requester and the agent acting on their behalf.
Q: How can security teams tell whether operational lineage is actually working?
A: A usable lineage model lets teams answer five questions from evidence alone: who initiated the action, which agent acted, under what authority, through what path, and with what effect.
Practitioner guidance
- Define first-class identities for each agent Register every agent with a unique identity, named owner, declared purpose, model version, tool set, and configuration hash so forensics can distinguish one principal from another.
- Replace impersonation with delegated credentials Issue short-lived credentials that carry both the user subject and the agent actor, with scope limited to the specific task rather than standing access across the day.
- Propagate lineage context across every hop Pass a correlation ID, originating principal, and delegation chain through tools, APIs, and agent-to-agent calls, and refuse requests that arrive without valid context.
Bottom line: AI agents need more than logs because logs do not prove who authorised an action or how authority flowed through the system.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/10/2026 6:57 pm
Operational lineage is the missing identity control for agentic systems. Logs can show activity, but they do not prove whether the action was initiated by a human, assigned by a schedule, or delegated through another agent. That gap becomes material once agents touch production systems because accountability now depends on proving the chain of authority, not merely observing execution. Practitioners should treat lineage as part of the identity model, not an audit afterthought.
A few things that frame the scale:
- Gartner predicts that more than 40% of agentic AI projects will be cancelled by the end of 2027, citing rising costs, unclear value and insufficient risk controls.
A question worth separating out:
Q: What is the difference between audit logs and operational lineage for AI agents?
A: Audit logs capture events after the fact, while operational lineage ties those events back to a verifiable authority chain. Lineage explains why an agent was allowed to act, not just that it acted. For IAM teams, that difference matters because governance depends on provenance, scope, and accountability, not timestamped output alone.
👉 Read our full editorial: Operational lineage is the missing control for agent accountability