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

SPIFFE/SPIRE Dynamic SVID Zero-Downtime TLS Handshake Guardrail

Enforces atomic in-memory dynamic SVID X.509 rotation using thread-safe pointers and dynamic TLS SNI/Handshake callbacks (e.g., GetCertificate/sni_callback). Prevents process restarts, connection draining drops, and destructive TLS renegotiation loops across high-throughput edge proxies.

Prohibited Anti-Pattern: Hard Restarting Services or Rebinding Listeners on SPIFFE SVID Expiration

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: SPIFFE/SPIRE Dynamic SVID Zero-Downtime TLS Handshake Guardrail - Enforces atomic in-memory dynamic SVID X.509 rotation using thread-safe pointers and dynamic TLS SNI/Handshake callbacks (e.g., GetCertificate/sni_callback). Prevents process restarts, connection draining drops, and destructive TLS renegotiation loops across high-throughput edge proxies.
globs: src/**/*.{go,rs,cpp,ts,py}, pkg/security/**/*.{go,rs}, infra/spiffe/**/*.{go,rs,yaml}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/spiffe-spire-dynamic-svid-rotation-guardrail"
---

# SPIFFE/SPIRE Dynamic SVID Zero-Downtime TLS Handshake Guardrail

> **Severity**: CRITICAL | **Category**: devops
> **Anti-Pattern Warning**: Hard Restarting Services or Rebinding Listeners on SPIFFE SVID Expiration

## System Constraints
You are a Principal Security Systems Architect enforcing zero-downtime SPIFFE/SPIRE X.509 SVID rotation. Mandate atomic in-memory swapping via TLS dynamic callback hooks, preventing listener rebinds, connection tearing, or mid-stream renegotiation spikes.

## Strict Guidelines
- Engineers MUST ALWAYS hook into runtime dynamic certificate callbacks (e.g., tls.Config.GetCertificate, GetClientCertificate, or SSL_CTX_set_cert_cb) rather than passing static certificate slices to TLS configurations.
- Engineers MUST ALWAYS update X.509 SVIDs atomically using lock-free atomic pointers (atomic.Pointer[tls.Certificate] in Go, ArcSwap in Rust) or synchronized double-buffering to eliminate race conditions during handshakes.
- Engineers MUST NOT invoke server reloads, process restarts, or close active net.Listener handles upon receiving SVID watch stream rotation events from the SPIRE Workload API.
- Services MUST decouple TLS handshakes for new connections from existing established keep-alive sockets, ensuring ongoing HTTP/2 and HTTP/3 multiplexed sessions remain unaffected by SVID credential turnover.
- Components NEVER trigger explicit TLS session renegotiation on active channels upon credential rotation; new credentials MUST exclusively apply to newly initiated ClientHello handshakes.
- Engineers MUST validate the SAN SPIFFE ID format and bundle trust domain before atomically committing the rotated SVID to the active memory pointer.

## Bad vs Good Implementations
### Atomic SVID Memory Swap via tls.Config.GetCertificate in Go

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Closing and rebinding the net.Listener causes dropped keep-alive TCP connections, introduces 5xx storm spikes, and can result in fatal bind collisions on edge proxies.
```go
package security

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

type StaticServer struct {
	listener net.Listener
}

// ANTI-PATTERN: Recreating the listener or mutating global tls.Config concurrently
func (s *StaticServer) OnSVIDRotated(newCert tls.Certificate) {
	log.Println("SVID renewed, restarting listener to apply certificate...")
	_ = s.listener.Close() // Drops hundreds of live keep-alive connections
	var err error
	s.listener, err = tls.Listen("tcp", ":8443", &tls.Config{
		Certificates: []tls.Certificate{newCert},
	})
	if err != nil {
		log.Fatalf("failed to rebind listener: %v", err)
	}
}
```

#### Production Standard (Correct)
> **Standard**: Utilizes atomic.Pointer to update the in-memory certificate reference with zero lock contention. New TLS handshakes seamlessly retrieve the rotated SVID without terminating active sessions.
```go
package security

import (
	"crypto/tls"
	"errors"
	"sync/atomic"
)

type DynamicSVIDManager struct {
	currentCert atomic.Pointer[tls.Certificate]
}

func NewDynamicSVIDManager(initialCert *tls.Certificate) *DynamicSVIDManager {
	m := &DynamicSVIDManager{}
	m.currentCert.Store(initialCert)
	return m
}

// OnSVIDRotated atomically replaces the pointer without terminating active sockets
func (m *DynamicSVIDManager) OnSVIDRotated(newCert *tls.Certificate) {
	m.currentCert.Store(newCert)
}

// GetCertificate supplies the current SVID to incoming ClientHello handshakes
func (m *DynamicSVIDManager) GetCertificate(info *tls.ClientHelloInfo) (*tls.Certificate, error) {
	cert := m.currentCert.Load()
	if cert == nil {
		return nil, errors.New("no valid SPIFFE SVID loaded")
	}
	return cert, nil
}

func (m *DynamicSVIDManager) CreateTLSConfig() *tls.Config {
	return &tls.Config{
		GetCertificate: m.GetCertificate,
		MinVersion:     tls.VersionTLS13,
	}
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

SPIFFE Workload API MCP
Validates dynamic X.509 SVID streams, trust bundle updates, and SPIRE agent socket synchronization.
Recommended Agent Skills (askills.dev)

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

spire-svid-lint
Analyzes SPIRE configuration and application-layer TLS handshake bindings for atomic rotation safety.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: SPIFFE/SPIRE Dynamic SVID Zero-Downtime TLS Handshake Guardrail

SPIFFE/SPIRE Dynamic SVID Zero-Downtime TLS Handshake Guardrail defines an industrial-grade behavioral standard for devops engineering. Enforces atomic in-memory dynamic SVID X.509 rotation using thread-safe pointers and dynamic TLS SNI/Handshake callbacks (e.g., GetCertificate/sni_callback). Prevents process restarts, connection draining drops, and destructive TLS renegotiation loops across high-throughput edge proxies. 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: Hard Restarting Services or Rebinding Listeners on SPIFFE SVID Expiration 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 DriftHard Restarting Services or Rebinding Listeners on SPIFFE SVID ExpirationCritical
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

Engineers MUST ALWAYS hook into runtime dynamic certificate callbacks (e.g., tls.Config.GetCertificate, GetClientCertificate, or SSL_CTX_set_cert_cb) rather than passing static certificate slices to TLS configurations.

Engineers MUST ALWAYS hook into runtime dynamic certificate callbacks (e.g., tls.Config.GetCertificate, GetClientCertificate, or SSL_CTX_set_cert_cb) rather than passing static certificate slices to 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.
2

Engineers MUST ALWAYS update X.509 SVIDs atomically using lock-free atomic pointers (atomic.Pointer[tls.Certificate] in Go, ArcSwap in Rust) or synchronized double-buffering to eliminate race conditions during handshakes.

Engineers MUST ALWAYS update X.509 SVIDs atomically using lock-free atomic pointers (atomic.Pointer[tls.Certificate] in Go, ArcSwap in Rust) or synchronized double-buffering to eliminate race conditions during handshakes.

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

Engineers MUST NOT invoke server reloads, process restarts, or close active net.Listener handles upon receiving SVID watch stream rotation events from the SPIRE Workload API.

Engineers MUST NOT invoke server reloads, process restarts, or close active net.Listener handles upon receiving SVID watch stream rotation events from the SPIRE Workload API.

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

Services MUST decouple TLS handshakes for new connections from existing established keep-alive sockets, ensuring ongoing HTTP/2 and HTTP/3 multiplexed sessions remain unaffected by SVID credential turnover.

Services MUST decouple TLS handshakes for new connections from existing established keep-alive sockets, ensuring ongoing HTTP/2 and HTTP/3 multiplexed sessions remain unaffected by SVID credential turnover.

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

Components NEVER trigger explicit TLS session renegotiation on active channels upon credential rotation

Components NEVER trigger explicit TLS session renegotiation on active channels upon credential rotation; new credentials MUST exclusively apply to newly initiated ClientHello handshakes.

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.
6

Engineers MUST validate the SAN SPIFFE ID format and bundle trust domain before atomically committing the rotated SVID to the active memory pointer.

Engineers MUST validate the SAN SPIFFE ID format and bundle trust domain before atomically committing the rotated SVID to the active memory pointer.

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 SPIFFE/SPIRE Dynamic SVID Zero-Downtime TLS Handshake Guardrail critical for AI coding assistants?

Enforces atomic in-memory dynamic SVID X.509 rotation using thread-safe pointers and dynamic TLS SNI/Handshake callbacks (e.g., GetCertificate/sni_callback). Prevents process restarts, connection draining drops, and destructive TLS renegotiation loops across high-throughput edge proxies. 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 (Hard Restarting Services or Rebinding Listeners on SPIFFE SVID Expiration) 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 DEVOPS Rules

View all rules →
devops
86

Kubernetes Gateway API v1 HTTPRoute Canary and ReferenceGrant Invariants

Enforces strict conformance to Kubernetes Gateway API v1 specifications during migration from legacy Ingress controllers. Mandates explicit ReferenceGrant resources for cross-namespace routing, strict relative integer weighting for HTTPRoute canary releases, and explicit backendRef port declarations.

devops
118

ArgoCD ApplicationSet Matrix Generator Invariants & Cascade Deletion Guards

Enforces strict structural constraints on ArgoCD ApplicationSet Matrix generators combining cluster selectors and Git directories. Prevents catastrophic multi-cluster cascade pruning, accidental secret exposure through parameter interpolation, and runaway Application CR explosion via explicit sync policies, preservation finalizers, and parameter validation.

devops
40

Karpenter Resilient Topology, Interruption Queue, and Consolidation Budget Standard

Enforces deterministic disruption budgets, multi-instance-type diversification, and event-driven SQS interruption queue handling across Karpenter NodePools and EC2NodeClasses. Eliminates cascading eviction loops, instance starvation, and availability downtime during AWS Spot rebalances and underutilized node consolidation.

1 Rule in Stack

SPIFFE/SPIRE