Topic starter
23/06/2026 9:18 pm
TL;DR: AI is shifting from answering questions to completing multi-step work across systems, and that makes secure access the gating issue, according to 1Password. The real challenge is not just provisioning credentials, but ensuring human and AI actors can act without exposing secrets or breaking workflow continuity.
Editorial analysis by NHI Mgmt Group, based on content published by 1Password: “1Password and Perplexity expand partnership to secure access for Perplexity Computer”.
Key questions
Q: How should security teams govern AI agents that run long, multi-step workflows?
A: Security teams should require durable execution, full event history, and clear ownership for every multi-step agent workflow that touches sensitive data or privileged tools.
Q: Why do AI agents create more risk when they reuse existing credentials?
A: Credential reuse makes agents hard to attribute and easier to abuse.
Q: What breaks when access controls are not built for cloud and AI-driven automation?
A: When controls are too static, modern pipelines rely on persistent credentials that outlive the task they were meant to serve.
Practitioner guidance
- Define execution-time access rules Map which AI workflows need access only at the moment of action and require those entitlements to expire with the task, not the session.
- Keep secrets out of model context Use mediation layers so agents can request actions without being shown credentials, tokens, or other secrets directly.
- Separate approval from secret delivery Let a human approve the permitted action while the access system delivers the credential through a governed path the model cannot inspect.
Bottom line: AI agent access is no longer a provisioning problem alone, because the decisive control point is the moment an action is taken inside the workflow.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 2:32 am
Execution-time access governance is becoming the control plane for AI work. The article reflects a broader shift in identity architecture: access is no longer a precondition that sits outside the workflow, but a control embedded inside the workflow itself. That changes how teams think about authorisation, auditability, and privilege scope for AI agents. Practitioners should treat execution-time governance as a first-class identity pattern, not a niche integration problem.
A question worth separating out:
Q: How should organisations govern AI agent access without losing operational speed?
A: Use task-scoped access, explicit human ownership, and runtime monitoring together. Fast-moving agents still need a clear approval path, a defined purpose, and revocation when behaviour drifts. The goal is not to slow automation, but to make every action traceable and every entitlement reviewable before it becomes standing risk.
👉 Read our full editorial: AI agent access must be governed at the moment of action