TL;DR: Traditional IAM and IGA leave gaps in SaaS discovery, device trust, and agentic access governance, making access control a performance and risk problem rather than a login problem, according to 1Password’s October 27, 2025 article. 1Password frames Extended Access Management as a way to secure access across people, apps, devices, and AI-driven workflows while preserving speed.
Editorial analysis by NHI Mgmt Group, based on content published by 1Password: “Utah Mammoth and Utah Jazz score with identity security”.
Key questions
Q: How should security teams govern access across SaaS sprawl?
A: Security teams should govern SaaS sprawl with one inventory, one policy model, and one review process that covers both human and non-human access.
Q: Why does device trust matter when credentials are already authenticated?
A: Because a valid credential does not prove the endpoint is safe.
Q: What breaks when AI agents are discovered but not lifecycle-managed?
A: Discovery alone breaks down because the organisation still cannot tell who owns the agent, whether it is still needed, or when its access should end.
Practitioner guidance
- Map SaaS discovery into access governance Use application discovery to identify shadow SaaS and AI usage before recertification and deprovisioning cycles begin.
- Bind high-risk access to trusted devices Require device compliance checks for sensitive applications so sign-in from unmanaged laptops, tablets, or phones is denied before access is granted.
- Define ownership for AI agent access Assign a named owner, scope, and offboarding path for every AI agent that can reach production systems or business data.
Bottom line: Traditional IAM and IGA leave practical gaps when access extends across SaaS sprawl, endpoint trust, and AI-driven workflows.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Extended access management reflects the collapse of the login-only model. The article describes a market reality in which access governance now spans people, SaaS, devices, and AI workflows, which means the control boundary has moved far beyond traditional SSO. Identity programmes that stop at authentication miss discovery and endpoint trust, leaving material exposure in the access layer. Practitioners should treat access as a full lifecycle governance problem, not a sign-in event.
A question worth separating out:
Q: Should IAM teams treat people, devices, SaaS apps, and AI agents as the same access problem?
A: No. They are linked, but they are not governed the same way. People authenticate, devices establish trust, SaaS applications need discovery and certification, and AI agents require explicit ownership and lifecycle controls. A single process will miss one of those dimensions.
👉 Read our full editorial: Extended access management for AI agents and trusted devices