Menu

AI Agent Identity Explained: SPIFFE, SPIRE and OPA Instead of API Keys
πŸ“°

AI Agent Identity Explained: SPIFFE, SPIRE and OPA Instead of API Keys

DEV Community: securityΒ·RuntimeStackΒ·4 days ago
#Ljqx5Ok2
#devtosecurity#devto#dev#agent#spiffe
Reading 0:00
15s threshold

Many AI agents still run on a static API key: long-lived, and hard to rotate.

It's a bearer secret, not bound to anything. Whoever copies it can act as your agent.

The fix is a passport that expires within the hour.

SPIFFE, SPIRE, SVIDs, OPA, Rego. Alphabet soup. One airport analogy makes it click, plus why a perfect ID won't stop your agent wiping a database.

Two questions: who are you, and may you board?

An airport asks two questions: who are you, and may you board?

SPIFFE and SPIRE issue the passport that answers the first. OPA runs the gate.

SPIFFE is the standard. SPIRE implements it; meshes like Istio issue SPIFFE IDs too.

The SPIFFE ID: the name in the passport

Your agent's name is a SPIFFE ID:

spiffe://example.org/agents/billing β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜ trust domain path

Enter fullscreen mode

Exit fullscreen mode

First, the trust domain : the trust root, like the country that issues a passport. Then the path , naming this workload.

The SVID: the passport

So what makes a name proof?…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.