Skip to content
IAM Insights

Explainers · Glossary

SAML

SAML 2.0

Security Assertion Markup Language (SAML): an XML-based (Extensible Markup Language) standard for single sign-on, in which an identity provider sends signed assertions about a user to an application.

reference →

In our briefings

The claim each of the newest briefings on SAML would have you leave with.

  1. Neiderman's case that the identity stack has to be rebuilt for agents starts with history. Identity spent decades as IT plumbing behind the firewall, the cloud made the identity provider the real gatekeeper, and companies answered with point tools: he recalls an average of about 8.3 per company, from a spreadsheet of conversations with, by his estimate, 100 to 200 or more CISOs. Agents, he says, will bring roughly a hundred times more identities working around the clock, and probably 99.9 percent of actions on data and systems will be theirs. In his view a stack built for humans and carrying decades of undocumented connections will not hold that load, while NewCore, starting fresh, can adjust its design as agent protocols are "still being formed". Two less interested voices in other sources we have read make a similar case. The founder of an identity threat detection company Okta had just acquired warned that bolting a bunch of things on will fail over time, and a paper led by Cloud Security Alliance authors lays out a new layered identity architecture for agents.

    Can your identity stack be patched for AI agents, or does it have to be replaced? NewCore's CTO says replacedBI-FIND-2026-0103

  2. One Identity's CEO says least privilege, granting only the permissions a job needs, is 'a very hard thing to actually achieve' and 'easier said than actually done'. Garg says organizations 'haven't put the governance systems in control', and that privileged access management, which separates administrator accounts from everyday ones, is 'not very widely deployed inside organizations'. Those organizations now face what he calls 'a compounding problem of agent identities', and the speed of it is what he says costs him sleep. His advice to customers is to start with 'the most critical things': privileged, administrative and infrastructure accounts before the average employee, and among agents, those 'driving automation in the back end' and 'doing business critical work' before those working on behalf of users. In the lightning round he named 'least privileged' the most overrated security buzzword. Other speakers we have read start in the same place: Rick Scot of Elevate Textiles, on Identity at the Center, would build a least-privilege model first and then review every service account. Identity Navigator's host describes one way the gap opens: a developer prompted for MFA all the time creates a service account that might not have MFA and can share it across the team.

    The agent problem is the service-account problem, at machine speedBI-FIND-2026-0161

  3. Asked which identity and security controls are most likely to break first as agentic systems scale, John Yeoh, CSA's chief scientific officer, names lifecycle management. He cites CircleCI and Microsoft's Midnight Blizzard breach as poor lifecycle management of non-human identities, where keys for secrets were not rotated fast enough, and expects agents to fail faster because people now give them specs that spin up sub-agents. Access reviews that ignore intent and behaviour come next, then logging, in what he calls "a good domino of control collapse". Aizome's Amir Ofek answers the same question differently: applying controls built for non-human identities, which are deterministic rather than dynamic, is what will break first.

    CSA's John Yeoh expects lifecycle management to be the first agent control to breakBI-FIND-2026-0113

›Cited in 53 briefings

Every briefing that discusses this term, newest first.

  1. Can your identity stack be patched for AI agents, or does it have to be replaced? NewCore's CTO says replaced

    Podcast · · TechSpective Podcast · Rebuilding Identity Security From Scratch for the Age of AI Agents · Sep 21, 2026

  2. The agent problem is the service-account problem, at machine speed

    Podcast · · Shift AI · AI Agents, Identity and Enterprise Security with One Identity CEO Praerit Garg · First aired Jul 2026 · Sep 14, 2026

  3. CSA's John Yeoh expects lifecycle management to be the first agent control to break

    Podcast · · The Non-Human & AI Identity Podcast · NHI & AI Identity Summit : The Next 24 Months · Sep 7, 2026

  4. When AI agents hand work to other agents, the person who started the job can get lost

    Podcast · · The Non-Human & AI Identity Podcast · NHI & AI Identity Summit : Governing AI · Sep 7, 2026

  5. A paper's 90- and 180-day rules for machine identities come with no test behind them

    Article · · International Journal For Multidisciplinary Research (Vol 8, Issue 3) · Thrinaath Vajragowni · May 23, 2026

  6. Transaction Tokens carry who started a request through internal services and define no list of the hops in between

    Draft · · IETF OAuth Working Group · Atul Tulshibagwale et al. · Jul 30, 2026

  7. OAuth's draft for crossing trust domains is approved for publication and never says agent

    Draft · · IETF OAuth Working Group · Arndt Schwenkschuster et al. · Jul 19, 2026

  8. The JWT an agent or other OAuth client signs in with may name only the server's issuer, never the token endpoint

    Draft · · IETF Datatracker · Michael B. Jones et al. · Apr 28, 2026

  9. WIMSE's agent draft adds how an agent's access ends and where policy engines fit, without a new requirement

    Draft · · IETF WIMSE Working Group · Pieter Kasselman et al. · Sep 15, 2026

  10. Cross-App Access draft warns that one stolen sign-in token could reach every app the identity provider permits

    Draft · · IETF Datatracker · Aaron Parecki et al. · May 21, 2026

  11. RFC 9207's issuer check stops at the redirect, and n8n's token-exchange flaw sat just past it

    Article · · WorkOS · Maria Paktiti · Jul 20, 2026

  12. Global Token Revocation must end a user's refresh tokens; their access tokens can outlive the call

    Draft · · IETF Datatracker · Aaron Parecki, Okta · Feb 25, 2026

  13. Agent delegation records not anchored in trusted time become deniable once timestamps can be forged

    Draft · · IETF Datatracker · V.K. Uppalapati · Sep 29, 2026

  14. NovaFabric seals AI agent runs as signed evidence, and its author says a signature proves a key, not a person

    Paper · · arXiv · Mohsen Seyedkazemi Ardebili · Oct 25, 2026

  15. LinkedIn, Uber and State Farm already run SPIRE for workload identity, and each plans to extend it

    Field signals · · 12 voices from the field · Nov 2024 to Oct 2026

  16. A cross-domain transaction-token grant now names AI agents as a use and keeps the call chain at home

    Draft · · IETF Datatracker · George Fletcher et al. · Sep 10, 2026

  17. Best Buy shrank its identity stack to three tools in 2021 and now throttles AI agents ahead of an RFP

    Podcast · · Identity at the Center · #411 - Making IAM a Best Buy with Greg Handrick · Mar 30, 2026

  18. KuppingerCole's Mike Small blames most cloud incidents on customers' identity mistakes and sees CNAPP moving to cover AI

    Podcast · · Identity at the Center · #455 - CNAPP and the Cloud Identity Problem with Mike Small · Oct 19, 2026

  19. Six companies' agent-auth draft, since adopted by the WIMSE group, keeps credentials out of the model's reach

    Draft · · IETF Internet-Draft (individual submission, since adopted by the WIMSE working group) · Pieter Kasselman et al. · Jul 6, 2026

  20. Eve Maler says the push to give every AI agent a responsible human misses agents a company does not own

    Podcast · · Identity at the Center · #453 - Treating Identity Like a Product with Eve Maler · Oct 12, 2026

  21. NIST and CISA advise one-hour tokens, 90-day keys and hardware key storage; AI agents get one paragraph

    Article · · NIST (CSRC) · Ryan Galluzzo et al. · Sep 15, 2026

  22. MCP's enterprise login extension says IdP revocation is immediate. Its own spec does not back that up

    Article · · Model Context Protocol (modelcontextprotocol.io) · MCP project et al. · Jun 18, 2026

  23. A survey rates only workload identity ready for agents, and argues no standard can tell what an agent intends

    Paper · · arXiv · Takumi Otsuka et al. · Apr 25, 2026

  24. Transaction tokens are nearly a standard, and there is still no agreed place in them for the agent

    Podcast · · Identity at the Center · #449 - Decoded - Transaction Tokens with George Fletcher · Sep 21, 2026

  25. Opal's access-review AI runs with a person approving by default, and an Opal engineer still reads the rejections

    Podcast · · Identity at the Center · #448 - Sponsor Spotlight - Opal Security · Sep 17, 2026

  26. Eight panels agree an agent acts for a person, never as that person. When agents hand work to other agents, nobody had an answer.

    Conference · · Las Vegas · June 2026, a one-day summit track inside Identiverse 2026; the eight panels were published as podcast episodes between 18 August and 7 September 2026

  27. Okta's answer to agent sprawl: put the identity provider between every agent and every app

    Podcast · · Cloud Security Podcast · Who Governs Your AI Agents? Identity, Offboarding & Open Standards · Jul 2, 2026

  28. An OpenID Foundation co-chair says AI agents need modest upgrades to today's identity systems, not a new one

    Podcast · · Identity at the Center · #390 - Identity Management for Agentic AI with Tobin South · Dec 8, 2025

  29. Canva sandboxes bounded conversion jobs; broad workforce agents pose a different access problem

    Podcast · · AI Security Podcast · Why I Dont Trust Your AI Agent | Kane Narraway, Canva · Aug 20, 2026

  30. xChk ships human OIDC portfolios and a separate agent approval API

    Paper · · arXiv · Sean MacGuire · Jul 15, 2026

  31. AgentDID checks an AI agent's identity and readiness in 13.5 seconds, but was tested on at most 50 agent pairs

    Paper · · arXiv · Minghui Xu et al. · Apr 28, 2026

  32. An OAuth client brokering many tools, as agent services do, can let a rogue tool take over a user's other tools

    Draft · · IETF Datatracker · Tim Würtele et al. · Mar 2, 2026

  33. MACAW Security's trust layer signs every agent call, but what stopped its prompt-injection test was a policy

    Paper · · arXiv · Mohan Rajagopalan et al. · Feb 11, 2026

  34. Credential wallet draft makes holder binding a MUST; its own SD-JWT profile names no way to provide it

    Draft · · IETF Datatracker · Leif Johansson et al. · Nov 4, 2025

  35. On its authors' tasks, an LLM check of agent scopes works at one tool and refuses most valid three-tool requests

    Paper · · arXiv · Majed El Helou et al. · Oct 30, 2025

  36. CAEP 1.0 tells apps what changed after login and leaves almost every response to the receiver

    Article · · OpenID Foundation · Tim Cappalli et al. · Aug 29, 2025

  37. Under Shared Signals 1.0 a sender may accept a subscription and send nothing, so agent revocation needs a backup

    Article · · OpenID Foundation · Atul Tulshibagwale et al. · Aug 29, 2025

  38. A 'provable' bound on agent-memory injection assumes independent layers and fills in none of its detection rates

    Paper · · arXiv · Ken Huang et al. · Aug 17, 2025

  39. The July 2025 Cross App Access draft lets the IdP decide app-to-app access and treats agents as plain clients

    Draft · · IETF Datatracker · Aaron Parecki et al. · Jul 2, 2025

  40. A Cloud Security Alliance paper wants AI agents on a new identity stack, with OAuth kept for simple cases

    Paper · · arXiv (cs.CR preprint 2505.19301) / Cloud Security Alliance · Ken Huang et al. · May 25, 2025

  41. A rogue OAuth server can collect a client's signed assertion and replay it at an honest server the client also uses

    Article · · IACR Cryptology ePrint Archive · Pedram Hosseyni et al. · Apr 7, 2025

  42. In GNAP (RFC 9635), a client is known by its key, and tokens stay key-bound unless the server flags them bearer

    Article · · RFC Editor · Justin Richer et al. · Oct 1, 2024

  43. The token exchange RFC that agent designs cite says its record of earlier actors is not for access decisions

    Article · · IETF Datatracker · Michael B. Jones et al. · Jan 1, 2020

  44. RFC 7800 gives a JWT one place to name its holder's key, and leaves the proof to each protocol

    Article · · RFC Editor · Michael B. Jones et al. · Apr 1, 2016

  45. In 2015, OpenID Connect discovery let an attacker's server choose where a client sent the user's code

    Paper · · arXiv · Christian Mainka et al. · Aug 18, 2015

  46. RFC 7522 lets a SAML assertion serve as a grant or authenticate the client independently

    Article · · IETF / RFC Editor · Brian Campbell et al. · May 1, 2015

  47. OAuth's assertion framework is built for bearer assertions, and one can buy fresh tokens until it expires

    Article · · RFC Editor · B. Campbell et al. · May 1, 2015

  48. RFC 7519 makes "none" mandatory to implement and leaves refusing an unwanted algorithm as a SHOULD

    Article · · RFC Editor · Michael B. Jones et al. · May 1, 2015

  49. RFC 7523 lets a signed JWT authenticate an OAuth client or serve as a grant, and leaves replay checks optional

    Article · · RFC Editor · Michael B. Jones et al. · May 1, 2015

  50. Macaroons, 2014: bearer tokens any holder can narrow but not widen, checkable only by the service that minted them

    Article · · NDSS Symposium 2014 (Google Research) · Arnar Birgisson et al. · Feb 23, 2014

  51. RFC 6819 warned in 2013 that servers receiving a token may reuse it, and offered audience binding and client-bound tokens

    Article · · RFC Editor · T. Lodderstedt et al. · Jan 2013

  52. RFC 6749 admits a server can't tell who presents a token; the fixes arrived in 2020 and 2023

    Article · · RFC Editor · D. Hardt et al. · Oct 2012

  53. Ian Glazer's sketch of a 2025 IAM stack: one shared identity data layer, with Shared Signals announcing changes

    Podcast · · Identity at the Center · #325 - Theorycrafting Modern Identity Architecture with Ian Glazer · Jan 13, 2025

Related terms

What appears alongside SAML in the same briefings.

OpenID ConnectOktaPing IdentityJWT Bearer GrantOAuthJWTSPIFFESSF