Skip to content
IAM Insights

Explainers · Glossary

GDPR

General Data Protection Regulation

The EU's General Data Protection Regulation, which obliges organisations processing personal data (including data touched by software agents) to support pseudonymization, consent, and demonstrable access-control accountability.

reference →

In our briefings

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

  1. Six voices say that knowing who an agent is and what it may access does not settle whether its next action is right, so the check has to look at what the agent is doing while it runs. Steven Rennick of Ciena says "we might know who the agent is and what it's allowed to do, but we really don't know how it's going to make those decisions," so trust has to become continuous and work at runtime. Sathvik Krishnamurthy, an investor with Security Leadership Capital speaking on Entrust's podcast, says identity and zero trust do not control an agent's behavior, and that a layer on top of them has to. Josh Woodruff of the Cloud Security Alliance and MassiveScale AI says zero trust checks who you are and what you can reach, and agents need one more check on every action: what are you doing right now, and is it allowed? Michael Davis of JPMorganChase says most detective controls only ask whether a tool call is allowed, and wants security to look at the actions themselves, not just the permissions. Sagar Batchu of Speakeasy retells an agent that deleted a production database with a valid full-access token: it "had valid credentials, but it didn't have valid intent." Dror Zelber of Radware wants each action compared with the agent's stated intent and goals, and blocked when they do not match. A seventh voice, Maia Iyer of IBM Research, describes the idea behind one such check, which could flag an outgoing call the user never asked for, and calls checks of this kind a soft layer for defense in depth. They differ on how much intent can carry. Rennick and Zelber would judge each action against the agent's intent. Woodruff says the checkpoint must be able to refuse an action whatever the intent was, because an agent with the right intent can still do damage. Rennick adds that judging actions by their outcomes as well is the desired end state, but he does not think the technology is there yet.

    Knowing who an agent is and what it may reach is not enough, six voices say: check each action as it runsBI-FIND-2026-2330

  2. The draft puts the agent's actions in four new vCon event types: tool-call, tool-result, reasoning and system-event. Its compatibility section says vCon software that does not support the extension ignores those events and still processes the session's messages as usual, so "the agent trace is not processed". The authors call that compatible, and the "ai_agent" name is not required in the critical parameter. Those same events are where the draft asks for privacy care: tool-call inputs may contain credentials, API keys or file contents, and tool results may hold personal data. A redactor that does not support the extension cannot assess those fields and, the draft says, may reject a vCon that lists "ai_agent". The security section adds that malicious prompts kept in a record may execute if an AI system processes the record later.

    A draft rebuilds agent session records on vCon, where software without the extension ignores the tool callsBI-FIND-2026-2135

  3. In AGTP -09 the Agent-ID header on a request is self-asserted: the server records what the client wrote. The base check, Level 2, resolves that ID to an Agent Identity Document signed by the issuing governance platform and confirms the ID matches the hash of the agent's Agent Genesis record. Binding the ID and its Authority-Scope to the TLS connection, Level 3, takes the Agent Certificate extension (AGTP-CERT). The draft marks that extension optional, and Hood lists it, with Agent Genesis, among mechanisms that may be subject to his pending patents; section 11.7 says implementers of the core specification are not affected by claims on those extensions and formats, and Hood offers a royalty-free licence. No step in the Level 2 procedure has the caller prove it holds a key, so we read Level 2 as showing that an ID exists and is properly signed, not that the caller is that agent. An OAuth, OIDC or SPIFFE credential can ride in the Authorization header, but the draft says that credential identifies the principal the agent acts for. The threat model itself says full mitigation of Agent Genesis spoofing requires AGTP-CERT.

    AGTP checks that an agent ID is signed; binding it to the connection is an add-on in the author's patent noticeBI-FIND-2026-1898

›Cited in 33 briefings

Every briefing that discusses this term, newest first.

  1. Knowing who an agent is and what it may reach is not enough, six voices say: check each action as it runs

    Field signals · · 14 voices from the field · Dec 2025 to Nov 2026

  2. A draft rebuilds agent session records on vCon, where software without the extension ignores the tool calls

    Draft · · IETF Datatracker · Henk Birkholz et al. · Nov 2, 2026

  3. AGTP checks that an agent ID is signed; binding it to the connection is an add-on in the author's patent notice

    Draft · · IETF Datatracker · Chris Hood, Nomotic, Inc. · Jun 28, 2026

  4. An agent audit log now names whom the agent acted for, but at low trust levels the agent may write that itself

    Draft · · IETF Datatracker · Raza Sharif, CyberSecAI · Oct 26, 2026

  5. Drake's revised draft: an agent identity outlives its operator but is never reissued once its last key is gone

    Draft · · IETF Datatracker · Christopher Drake, 1id.com · Sep 25, 2026

  6. 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

  7. A point-in-time access review can't keep pace with changing access, four voices say, and four vendors now put AI inside the review

    Field signals · · 9 voices from the field · Nov 2024 to Aug 2026

  8. Joseph Carson says AI agents are workloads, and asks if identifiers and audit trails are all they need

    Podcast · · Identity at the Center · #456 - AI vs Reality with Joseph Carson · Oct 26, 2026

  9. The OWASP MCP Top 10 lead says few security teams can find the MCP servers developers run on their own machines

    Podcast · · The Application Security Podcast · Shadow MCP Servers: The AI Security Risk Hiding on Your Developers' Laptops · Oct 12, 2026

  10. Of 30 deployed AI agents, 7 publish how a website can recognize them and one signs its requests

    Paper · · arXiv · Leon Staufer et al. · Feb 19, 2026

  11. An OAuth profile for AI agents makes every hand-off cut privileges, but a shorter expiry alone counts as a cut

    Draft · · IETF Datatracker · Angel Cruz · Feb 7, 2026

  12. Anthropic asks for per-agent identity; its guide leaves Claude Code sub-agent credentials unspecified

    Article · · Anthropic (Claude) · Anthropic · May 27, 2026

  13. A county CTO says identity is already critical infrastructure, and nobody will own it until someone declares it

    Podcast · · Identity at the Center · #452 - When Identity Becomes Critical Infrastructure with Shea McGrew · Oct 5, 2026

  14. A proposed consent log for A2A and MCP records the terms an agent accepted, but the agent fills it in itself

    Paper · · arXiv · Ravi Kiran Kadaboina · Apr 16, 2026

  15. A proposed record of who authorized an AI agent's actions cannot yet prove which agent took them

    Paper · · arXiv · Asiri Dalugoda, Helixar · Apr 6, 2026

  16. OpenID agent-claims draft adds a provider-set user, application or agent label; scores stay each provider's own

    Draft · · IETF Datatracker · Raza Sharif, CyberSecAI · Mar 26, 2026

  17. A cross-domain agent trust draft requires the call chain, then leaves its format to a version that never came

    Draft · · IETF Datatracker · Daniel King et al. · Mar 15, 2026

  18. 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

  19. A China Mobile draft would end an agent's token when its task ends, if a webhook says so

    Draft · · IETF Datatracker · Meiling Chen et al. · Feb 4, 2026

  20. The best AI models can tell a screen holds private data but, on one test, found and labelled at most 13.3% of it

    Paper · · arXiv · Yanxi Wang et al. · Jan 26, 2026

  21. For US banks to accept mobile driver's licenses, an OpenID Foundation group proposes five trust signals

    Article · · OpenID Foundation · Serj Hallam · Nov 5, 2025

  22. CORAL's public agent server rejected forged messages but let a wrong key open the session stream

    Paper · · arXiv · Yedidel Louck et al. · Nov 5, 2025

  23. A decade of AI privacy papers: nearly half on training-data leakage, 2% on agents leaking user context

    Paper · · arXiv · Niloofar Mireshghallah et al. · Oct 2, 2025

  24. Stytch sells a one-call check for whether a visitor is an AI agent, priced at half a cent a lookup

    Podcast · · So What About AI Agents · EP 39 - Agentic Authentication | Bobbie Chen · Sep 23, 2025

  25. 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

  26. DIRF credits its anti-cloning controls with a jump from near 0% to over 90%; no test in the paper applies them

    Paper · · arXiv · Hammad Atta et al. · Aug 2, 2025

  27. A July OAuth draft proposes authorization for models inside a client

    Draft · · IETF Datatracker · Yurong Song et al. · Jul 3, 2025

  28. Each of eight AI models fell for at least one jailbreak planted in a simulated MCP server

    Paper · · arXiv · Junfeng Fang et al. · Jun 16, 2025

  29. The W3C credential standard leaves out what agents need most: which issuers to trust, and who may present

    Article · · W3C · Manu Sporny et al. · May 15, 2025

  30. ATFAA names identity inheritance as an agent threat and answers it with existing cloud policy tools

    Paper · · arXiv · Vineeth Sai Narajala et al. · Apr 28, 2025

  31. LOKA lets AI agents own their identities and vote on ethics, without naming anyone they act for

    Paper · · arXiv · Rajesh Ranjan et al. · Apr 15, 2025

  32. DIF's Presentation Exchange lets a verifier ask for credentials, but not ask who is presenting them for whom

    Article · · Decentralized Identity Foundation · Daniel Buchner et al. · Apr 25, 2024

  33. A 2024 FAccT paper suggests services could turn away AI agents without identifiers, and concedes users could easily add one

    Paper · · arXiv · Alan Chan et al. · Jan 23, 2024

Related terms

What appears alongside GDPR in the same briefings.

Digital Identity Rights FrameworkHIPAAEU AI ActDID / Verifiable CredentialsISO/IEC 42001A2APCI DSSIBM