Standard
Open standard for workload identity, issuing cryptographic SPIFFE IDs and SVIDs (X.509/JWT) so services can authenticate each other across platforms.
The Linux Foundation is taking over an open spec for hardware-signed agent runtime evidence. The producing side now has code and a spec; nobody has yet named who accepts the record.
Perspective Coverage
4 publishersReality
AWS ends App Mesh support in September 2026. One team scored the replacements on weighted criteria, wrote a rollback for every step, and moved about 40 services in two phases with no outage.
Reality
The spec's own boundary list says a verified catalog entry establishes which domain claims a capability and what trust material it published. It says nothing about whether the calling process is the agent it names.
Reality
Drawing on public comments to its NCCoE concept paper, NIST argues that each agent needs its own identifier and entitlements, and notes that the enterprise protocols for delegating that access already exist.
Reality
Unit 42 showed that spoofing the cgroup data a SPIRE agent reads during workload attestation makes it hand over a co-located workload's SVID, and released a tool so defenders can size the loss per node.
Reality
The ext-auth repo holds two files: a stable extension that authenticates a person through an IdP redirect, and a draft machine flow that hands the agent a pre-registered key it has to keep. Both agent-identity proposals are open.
Reality
The v1.37 GA puts X.509 delivery and refresh inside Kubelet, but the authority that actually signs those certificates is still integration work, which is why no adjacent tooling comes out of the plan this quarter.
Reality
The Linux Foundation now hosts TRACE, a format for evidence of what an AI agent actually did. The package that produces those records still ships as a developer preview.
Reality
Inventory and cadence cannot govern a credential whose holder is already deleted. The arithmetic points at one control: the lifetime written into the token when it is issued.
Reality
Red Hat's pitch for SPIFFE and SPIRE on OpenShift is an argument about exposure windows: a leaked Secret stays valid until someone notices it. Agents sharing the analysts' database worsen the arithmetic.
Reality
An agent that can read Prometheus and reach nothing else is a pattern worth copying. The auto-remediate button in the same dashboard is where the argument gets complicated.
Reality
A PingFederate write-up wires RFC 8693 token exchange to a SPIRE JWT-SVID so neither the user's token nor the workload's proof can stand in for the other. The lifetimes tell you where the risk sits.
Reality