AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
securitycritical PriorityID: spiffe-spire-workload-attestation-mtls-rotation

Zero-Trust Ephemeral Workload Attestation via SPIFFE/SPIRE Workload API & Dynamic mTLS Rotation

Enforces dynamic, cryptographic workload identity using the SPIFFE Workload API over Unix Domain Sockets to obtain short-lived X.509 SVIDs and SPIFFE trust bundles. Mandates streaming SVID auto-rotation directly into TLS handshake listeners to eliminate static API tokens, long-lived certificates on disk, and service restarts during credential rollover.

Prohibited Anti-Pattern: Persisting static certificates or API tokens on disk and failing to dynamically stream X.509 SVID rotations via the Workload API.

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Zero-Trust Ephemeral Workload Attestation via SPIFFE/SPIRE Workload API & Dynamic mTLS Rotation - Enforces dynamic, cryptographic workload identity using the SPIFFE Workload API over Unix Domain Sockets to obtain short-lived X.509 SVIDs and SPIFFE trust bundles. Mandates streaming SVID auto-rotation directly into TLS handshake listeners to eliminate static API tokens, long-lived certificates on disk, and service restarts during credential rollover.
globs: **/*.go, src/**/*.{ts,js}, infra/**/*.yaml, **/spire/**/*.conf
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/spiffe-spire-workload-attestation-mtls-rotation"
---

# Zero-Trust Ephemeral Workload Attestation via SPIFFE/SPIRE Workload API & Dynamic mTLS Rotation

> **Severity**: CRITICAL | **Category**: security
> **Anti-Pattern Warning**: Persisting static certificates or API tokens on disk and failing to dynamically stream X.509 SVID rotations via the Workload API.

## System Constraints
You are a Principal Security Architect enforcing Zero-Trust ephemeral identity standards using SPIFFE/SPIRE. Mandate that microservices communicate over mTLS backed by dynamically rotated X.509 SVIDs obtained exclusively via the SPIFFE Workload API Unix Domain Socket. Forbid static certificates on disk, long-lived API tokens, ambient Kubernetes tokens, and manual certificate reloads.

## Strict Guidelines
- Services MUST connect to the SPIFFE Workload API exclusively over a local Unix Domain Socket (UDS, e.g., 'unix:///spiffe-workload-api/spire-agent.sock') and NEVER over unauthenticated network TCP sockets.
- Services MUST obtain X.509 SVIDs and trust bundles in-memory via an asynchronous streaming client (e.g., 'go-spiffe/v2/workloadapi.X509Source') and MUST NOT write private keys or certificates to persistent disk or tmpfs mounts.
- Network listeners and clients MUST bind their TLS configurations directly to the dynamic X509Source to trigger seamless, in-memory mTLS credential rotation without restarting the process or terminating established connections prematurely.
- Authorizers MUST validate the remote peer's exact SPIFFE ID format ('spiffe://<trust-domain>/<workload-path>') rather than Subject Alternative Name (SAN) strings or deprecated Subject Common Name (CN) attributes.
- Workloads MUST fail closed and refuse network traffic if the SPIFFE Workload API is unreachable or returns an invalid/expired SVID; workloads MUST NEVER fall back to static API keys, shared secrets, or default permissive TLS configurations.

## Bad vs Good Implementations
### Go: Dynamic SPIFFE Workload API mTLS Listener vs Static Disk-Loaded TLS

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Static X.509 key-pairs loaded from disk require manual reloads or process restarts upon renewal. Private keys written to storage violate zero-trust ephemeral credential storage invariants.
```go
package main

import (
	"crypto/tls"
	"net/http"
)

func startServer() error {
	// BAD: Loading static certificates from disk.
	// Requires external cron or container restart to rotate before expiration.
	// Exposes long-lived private key files to disk inspection and node exfiltration.
	cer, err := tls.LoadX509KeyPair("/var/run/secrets/tls.crt", "/var/run/secrets/tls.key")
	if err != nil {
		return err
	}

	server := &http.Server{
		Addr: ":8443",
		TLSConfig: &tls.Config{
			Certificates: []tls.Certificate{cer},
			ClientAuth:   tls.RequireAndVerifyClientCert,
		},
	}
	return server.ListenAndServeTLS("", "")
}
```

#### Production Standard (Correct)
> **Standard**: The X509Source maintains an open streaming channel with the local SPIRE agent over a Unix Domain Socket, continuously updating SVIDs and root bundles in-memory prior to expiration without service restarts.
```go
package main

import (
	"context"
	"net/http"

	"github.com/spiffe/go-spiffe/v2/spiffetls/tlsconfig"
	"github.com/spiffe/go-spiffe/v2/spiffeid"
	"github.com/spiffe/go-spiffe/v2/workloadapi"
)

func startServer(ctx context.Context) error {
	// GOOD: Establish an in-memory streaming X509Source via the SPIFFE Workload API UDS.
	source, err := workloadapi.NewX509Source(ctx, workloadapi.WithClientOptions(
		workloadapi.WithAddress("unix:///spiffe-workload-api/spire-agent.sock"),
	))
	if err != nil {
		return err
	}
	defer source.Close()

	// Authorize only specific client SPIFFE IDs within the trusted domain.
	clientMatcher := tlsconfig.AuthorizeID(spiffeid.RequireFromString("spiffe://prod.internal/ns/workloads/sa/order-client"))

	// Configure dynamic mTLS: certificates and bundles rotate in-memory without downtime.
	tlsConfig := tlsconfig.MTLSServerConfig(source, source, clientMatcher)

	server := &http.Server{
		Addr:      ":8443",
		TLSConfig: tlsConfig,
	}
	return server.ListenAndServeTLS("", "")
}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Kubernetes Resource Inspector
Verifies SPIRE Agent DaemonSet configurations, CSI driver mounts, and workload socket injection across cluster nodes.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

SPIRE Agent CLI Tools
CLI utility to test local workload attestation and validate SVID issuance via the SPIFFE Workload API socket.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Zero-Trust Ephemeral Workload Attestation via SPIFFE/SPIRE Workload API & Dynamic mTLS Rotation

Zero-Trust Ephemeral Workload Attestation via SPIFFE/SPIRE Workload API & Dynamic mTLS Rotation defines an industrial-grade behavioral standard for security engineering. Enforces dynamic, cryptographic workload identity using the SPIFFE Workload API over Unix Domain Sockets to obtain short-lived X.509 SVIDs and SPIFFE trust bundles. Mandates streaming SVID auto-rotation directly into TLS handshake listeners to eliminate static API tokens, long-lived certificates on disk, and service restarts during credential rollover. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Persisting static certificates or API tokens on disk and failing to dynamically stream X.509 SVID rotations via the Workload API. Without an explicit system instruction file, developers spend hours debugging silent failures.
Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftPersisting static certificates or API tokens on disk and failing to dynamically stream X.509 SVID rotations via the Workload API.Critical
Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production.
Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture InconsistencyAI assistants produce mixed paradigms across files, creating fragmented codebase conventions.Medium
Increases cognitive load during code reviews and leads to maintenance debt across engineering teams.
Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.
Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

1

Services MUST connect to the SPIFFE Workload API exclusively over a local Unix Domain Socket (UDS, e.g., 'unix

Services MUST connect to the SPIFFE Workload API exclusively over a local Unix Domain Socket (UDS, e.g., 'unix:///spiffe-workload-api/spire-agent.sock') and NEVER over unauthenticated network TCP sockets.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Services MUST obtain X.509 SVIDs and trust bundles in-memory via an asynchronous streaming client (e.g., 'go-spiffe/v2/workloadapi.X509Source') and MUST NOT write private keys or certificates to persistent disk or tmpfs mounts.

Services MUST obtain X.509 SVIDs and trust bundles in-memory via an asynchronous streaming client (e.g., 'go-spiffe/v2/workloadapi.X509Source') and MUST NOT write private keys or certificates to persistent disk or tmpfs mounts.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Network listeners and clients MUST bind their TLS configurations directly to the dynamic X509Source to trigger seamless, in-memory mTLS credential rotation without restarting the process or terminating established connections prematurely.

Network listeners and clients MUST bind their TLS configurations directly to the dynamic X509Source to trigger seamless, in-memory mTLS credential rotation without restarting the process or terminating established connections prematurely.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Authorizers MUST validate the remote peer's exact SPIFFE ID format ('spiffe

Authorizers MUST validate the remote peer's exact SPIFFE ID format ('spiffe://<trust-domain>/<workload-path>') rather than Subject Alternative Name (SAN) strings or deprecated Subject Common Name (CN) attributes.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Workloads MUST fail closed and refuse network traffic if the SPIFFE Workload API is unreachable or returns an invalid/expired SVID

Workloads MUST fail closed and refuse network traffic if the SPIFFE Workload API is unreachable or returns an invalid/expired SVID; workloads MUST NEVER fall back to static API keys, shared secrets, or default permissive TLS configurations.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is Zero-Trust Ephemeral Workload Attestation via SPIFFE/SPIRE Workload API & Dynamic mTLS Rotation critical for AI coding assistants?

Enforces dynamic, cryptographic workload identity using the SPIFFE Workload API over Unix Domain Sockets to obtain short-lived X.509 SVIDs and SPIFFE trust bundles. Mandates streaming SVID auto-rotation directly into TLS handshake listeners to eliminate static API tokens, long-lived certificates on disk, and service restarts during credential rollover. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Persisting static certificates or API tokens on disk and failing to dynamically stream X.509 SVID rotations via the Workload API.) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related SECURITY Rules

View all rules →
security
105

OpenFGA Graph Invariants: Cyclic Relation Prevention & Contextual Tuple Hardening

Enforces strict directed acyclic graph (DAG) topology validation during relationship mutation writes and mandates strict server-side schema verification for ephemeral contextual tuples in OpenFGA evaluations. Prohibits persistent storage of ephemeral request attributes and guards against recursive relation loops causing graph expansion denial-of-service.

security
81

WebAuthn Conditional UI Mediation, Nonce Atomicity, and Assertion Cryptographic Verification

Enforces zero-trust cryptographic validation for FIDO2/WebAuthn Passkey authentication with Conditional UI autofill. Requires atomic single-use challenge consumption to eliminate replay attacks, strict RP ID hash and origin binding, authenticatorData flag verification (User Presence and User Verification), and monotonic signature counter enforcement to detect authenticator cloning.

security
111

Enforce Sigstore Keyless OIDC Attestation and Admission Controller Verification

Enforces immutable supply-chain security using Sigstore Cosign keyless signing via ephemeral OIDC tokens issued by Fulcio and verified against the Rekor transparency log. Container workloads must be signed and attested at build time by digest, and admission controllers (such as Kyverno or Sigstore Policy Controller) must strictly validate the OIDC issuer and subject identity before allowing image execution.

1 Rule in Stack

Zero-Trust