Topic starter
10/06/2026 11:00 pm
TL;DR: Agentic systems break the human assumption that authentication can establish trust for a fixed period, because they expand scope mid-task, make fresh tool choices, and require continuous authorization, attribution, and mediated credential use, according to 1Password. Static identity controls are no longer enough when an agent can change intent after login.
Editorial analysis by NHI Mgmt Group, based on content published by 1Password: “OpenAI’s Fotis Chantzis on why identity protocols weren’t designed for agents”.
Key questions
Q: What breaks when agents rely on static login trust?
A: Static login trust breaks because authentication confirms only the starting identity, not the agent's later actions.
Q: Why do agent workflows require continuous authorization?
A: Agent workflows require continuous authorization because their intent can change after the initial grant.
Q: How can security teams preserve attribution across agent actions?
A: Security teams should preserve attribution by recording each action with the agent identity, the initiating human authority, and the systems touched along the way.
Practitioner guidance
- Define per-action authorization boundaries Map each agent workflow to the exact actions, tools, and destinations that must be approved independently instead of inheriting a broad session grant.
- Route secrets through a mediation layer Keep credentials out of the agent context window by using proxies, gateways, or injection layers that bind access to specific destinations.
- Preserve step-level attribution Require execution traces that tie each action back to the initiating human authority and the agent that carried it out across systems.
Bottom line: Agentic workflows expose a basic mismatch between one-time authentication and changing runtime intent, so login alone cannot carry identity trust.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 2 days ago by NHI Mgmt Group
12/06/2026 4:47 am
Authentication does not equal trust for autonomous work: the login event only establishes who started the session, not what the agent will do after its intent changes. Agents can expand scope, choose new tools, and continue acting without a fresh human decision. The implication is that identity programmes must stop treating authentication as a durable trust boundary for non-human execution.
A few things that frame the scale:
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap, according to the State of Secrets in AppSec.
A question worth separating out:
Q: What is the difference between delegated access and mediated credential use for agents?
A: Delegated access gives the agent direct possession of a credential, while mediated credential use keeps the secret behind a proxy or gateway and only allows the agent to request approved actions. That difference matters because exposed credentials expand abuse potential, whereas mediation preserves control at the point of use.
👉 Read our full editorial: Agent identity needs continuous authorization, not static login trust
This post was modified 2 days ago by NHI Mgmt Group