Skip to content
IAM Insights

Explainers · Glossary

Cloud Native Computing Foundation

CNCF

The vendor-neutral foundation that hosts Kubernetes and related cloud-native projects, including SPIFFE and SPIRE.

reference →

In our briefings

The claim each of the newest briefings on Cloud Native Computing Foundation would have you leave with.

  1. Under revision -03, a WIMSE credential that validates against its trust domain's anchors proves membership, not identity. Section 9.2, new in -03, says that check "establishes that the peer belongs to that trust domain, but does not by itself establish which workload the peer represents", for clients and servers alike, and adds: "Proof of possession does not mitigate this vulnerability." Telling workloads apart takes the identifier comparison that section 1.2 now spells out. A caller checks the server certificate against the identifier it expects, as RFC 9525 describes, and a callee checks the audience of the caller's proof. Section 5.2 says the callee MUST make that audience check against trusted configuration "rather than request fields such as Host", because intermediaries may rewrite the request URI. Where several instances share one identifier, the identifier alone cannot tell them apart for authorization or auditing.

    WIMSE credentials -03: a valid signature proves trust-domain membership, not which workload is callingBI-FIND-2026-1907

  2. Four voices, all giving opinions rather than measurements, say the access an agent runs on today covers far more than its task. Steve Rennick of Ciena says OAuth's additions for acting on a user's behalf are not fine-grained enough for agents. Dev Rishi of Rubrik says an OAuth scope lets an agent send email when a firm may want it to write to internal recipients only. On two panels, Ian Livingstone of Keycard says OAuth was not designed for agents, and Dick Hardt of Hellō calls existing OAuth scopes far too coarse-grained for them. Grace Rachmany of the Decentralized Identity Foundation says the agent works under the whole department's authorization, which is separate from the login of the person who prompted it. They differ on the fix. Rishi thinks it may come from some of the tooling built around the protocols, Livingstone wants permissions set per task, and Rennick says people tell him standards are coming. On Rishi's episode, host Caleb Sima disagrees and says A2A's custom scopes already allow finer control.

    OAuth scopes grant agents far more than the task needs, four voices say, and authorization handed from agent to agent has no settled pattern yetBI-FIND-2026-1750

  3. Speakers from three large companies describe SPIRE, the open-source CNCF project that issues SPIFFE workload identities, as something they already run, and each names a next step that widens it. LinkedIn's Junyuan Zeng and Wei Zhang say they relied for years on a basic internal certificate server that was not built to scale, and now run SPIRE as a separate deployment per regional production data center, with each node proven through its TPM and LinkedIn's asset database; a boot-integrity check is planned. Uber's speakers describe a library that gets certificates from SPIRE so one service can authenticate to another, retrofitted onto thousands of running services, and Yangmin Zhu says Uber is extending it from service-to-service to person-to-service traffic. State Farm's Ivy Alkhaz and May Large run SPIRE across their cluster fleet, mostly issuing JWT credentials so far; next on their list are X.509 and mTLS through a service mesh, platforms outside Kubernetes, and federation with more trust domains. These next steps are plans with no dates, and all three are CNCF talks dated November 2025.

    LinkedIn, Uber and State Farm already run SPIRE for workload identity, and each plans to extend itBI-FIND-2026-1752

Cited in 5 briefings

Every briefing that discusses this term, newest first.

  1. WIMSE credentials -03: a valid signature proves trust-domain membership, not which workload is calling

    Draft · · IETF Datatracker · Brian Campbell et al. · Jul 2, 2026

  2. OAuth scopes grant agents far more than the task needs, four voices say, and authorization handed from agent to agent has no settled pattern yet

    Field signals · · 7 voices from the field · Oct 2025 to Oct 2026

  3. LinkedIn, Uber and State Farm already run SPIRE for workload identity, and each plans to extend it

    Field signals · · 12 voices from the field · Nov 2024 to Oct 2026

  4. IBM Research puts agent identity in a SPIFFE and OAuth sidecar; Maia Iyer calls authorization policy still open

    Podcast · · Kubernetes Bytes · Your AI Agent Has Too Much Access | Fixing Agent Identity · Sep 15, 2026

  5. Two ways to give an AI agent an OAuth identity clashed in April; a draft now lets them work together

    Podcast · · Hybrid Identity Protection Podcast · Securing Non-Human Identities in the Age of Agentic AI with Sarah Cecchetti, Director of Product Management at Semperis · Apr 28, 2026