SPIFFE workload identity: short-lived identity needs a clear trust boundary
How SPIFFE and SPIRE identity issuance, rotation, federation, and authorization fit together.
Tag archive
How SPIFFE and SPIRE identity issuance, rotation, federation, and authorization fit together.
Why sharing your users' OAuth tokens with AI agents breaks audit, least privilege, and enterprise deals — and how to run agent identity with OBO exchange on a local stack.
After I published One identity, two clouds: an AWS-hosted agent that authorizes with Microsoft Entra...
Vercel has acquired Better Auth, framed as a bet that AI agents opening PRs, reviewing code and creating deployments should hold first-class identity of their own. For CI/CD platforms, that reopens the question of what the merge and deploy gates are actually verifying.
The architecture diagram was the easy part. In Your SPIFFE workload can authenticate as an Entra...
Por Bruno Siqueira - Especialista em Desenvolvimento da Magalu Cloud Como uma aplicação rodando no...
SPIFFE with Microsoft Entra Agent ID sounds almost too tidy. Let SPIRE attest an AI agent running in...
A New Stack analysis argues agentic systems pass functional review and then stall at the security gate because no one scoped identity, permissions or audit at the platform layer first. For CI/CD owners, it pushes a familiar workload-identity problem onto a much larger fleet of callers.
Unlock the power of AI agents with this comprehensive guide to creating and deploying effective AI agents using subagents, HITL Gate, and workload identity....

According to the Verizon Data Breach Investigations Report 2024, credential abuse was involved in 77%...

If you run SPIRE, are you SPIFFE compliant? How far do you have to go with a custom implementation? I read the spiffe/spiffe spec end to end and pulled out the MUST requirements for SPIFFE-ID, X.509-SVID, JWT-SVID, Workload API, and Trust Bundle.

Day-to-day, I mainly contribute to Elva, a powerhouse of AWS experts aiming to help our customers...