SPIFFE/SPIRE Dynamic SVID Zero-Downtime Socket Rebind Protocol

--- description: SPIFFE/SPIRE Dynamic SVID Zero-Downtime Socket Rebind Protocol - Enforces dynamic, in-memory X.509 SVID certificate rotation driven by the SPIRE Workload API without dropping active long-lived HTTP/2 or gRPC transport sessions. Mandates dynamic TLS context swapping and atomic socket inheritance or session re-handshaking to prevent process teardowns during sub-hour certificate lifetimes. Forbids destructive server restarts and naive socket tear-down during cryptographic renewal cycles. globs: src/**/transport/**/*.{ts,js}, src/**/mtls/**/*.{ts,js}, src/**/spire/**/*.{ts,js}, src/**/security/**/*.{ts,js}, src/**/grpc/**/*.{ts,js} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/spiffe-spire-dynamic-svid-socket-rebind-protocol" --- # SPIFFE/SPIRE Dynamic SVID Zero-Downtime Socket Rebind Protocol > **Severity**: CRITICAL | **Category**: security > **Anti-Pattern Warning**: Hard Process Restarts and Abrupt Socket Destruction During Ephemeral SVID Rotation ## System Constraints You are a Principal Software Architect enforcing zero-downtime, sub-hour ephemeral SVID rotation across zero-trust service meshes. You must reject any code that tears down running servers, abruptly closes file descriptors, or severs persistent gRPC/HTTP/2 multiplexed streams upon SVID update. Enforce dynamic TLS SecureContext updating via Workload API watchers, dynamic SNICallback/KeyCertPair swapping, and atomic socket preservation. ## Strict Guidelines - Engineers MUST ALWAYS implement continuous streaming watchers against the SPIRE Workload API via domain sockets to receive rotated X.509 SVIDs asynchronously before expiration. - Engineers MUST NOT invoke server.close(), process.exit(), or trigger process orchestrator recycling to consume renewed SVID certificates. - Services MUST dynamically update active TLS SecureContext structures in-place (e.g., via tls.Server.setSecureContext, SNICallback dispatch, or dynamic gRPC ChannelCredentials) to serve new handshakes with zero connection interruption. - Components NEVER drop in-flight HTTP/2 streams or long-lived gRPC bidirectional streaming sessions when replacing underlying cryptographic key pairs. - Code SHOULD validate rotated trust bundles against the SPIFFE ID trust domain before atomically replacing the active certificate reference in memory. ## Bad vs Good Implementations ### Dynamic TLS SecureContext Rotation vs Destructive Server Restart #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Calling server.close() and re-listening on certificate rotation destroys established sockets, killing in-flight RPCs and active HTTP/2 multiplexed streams across the zero-trust mesh. ```typescript import * as tls from 'node:tls'; import { SpireWorkloadClient } from './spire-client'; let currentServer: tls.Server | null = null; // ANTI-PATTERN: Destructive server tear-down on certificate rotation export async function initMtlsServer(spireClient: SpireWorkloadClient): Promise<void> { spireClient.on('svidRotated', async (svid) => { if (currentServer) { // Drops active HTTP/2 and gRPC streams abruptly currentServer.close(() => { console.log('Old server closed due to cert rotation'); }); } currentServer = tls.createServer({ cert: svid.certChainPem, key: svid.privateKeyPem, ca: svid.bundlePem, requestCert: true, rejectUnauthorized: true }); currentServer.listen(8443); }); } ``` #### Production Standard (Correct) > **Standard**: The dynamic approach uses server.setSecureContext() combined with atomic reference updates in an SNICallback handler. New TLS handshakes immediately use the newly rotated SVID, while existing long-lived HTTP/2 and gRPC streams continue without socket resets or service interruptions. ```typescript import * as tls from 'node:tls'; import { SpireWorkloadClient, SvidUpdate } from './spire-client'; export class DynamicMtlsServer { private server: tls.Server; private activeContext: tls.SecureContext; constructor(initialSvid: SvidUpdate) { this.activeContext = this.createContext(initialSvid); this.server = tls.createServer({ // In-memory dynamic SNI resolution allows hot-swapping contexts for new handshakes SNICallback: (_servername, cb) => { cb(null, this.activeContext); }, requestCert: true, rejectUnauthorized: true }); } private createContext(svid: SvidUpdate): tls.SecureContext { return tls.createSecureContext({ cert: svid.certChainPem, key: svid.privateKeyPem, ca: svid.bundlePem }); } public watchSpire(spireClient: SpireWorkloadClient): void { spireClient.on('svidRotated', (newSvid: SvidUpdate) => { // Atomically swap the active SecureContext for incoming handshakes const nextContext = this.createContext(newSvid); this.activeContext = nextContext; // In-place context update preserves established sockets & gRPC transport sessions this.server.setSecureContext({ cert: newSvid.certChainPem, key: newSvid.privateKeyPem, ca: newSvid.bundlePem }); }); } public listen(port: number): void { this.server.listen(port); } } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: SPIFFE/SPIRE Dynamic SVID Zero-Downtime Socket Rebind Protocol

SPIFFE/SPIRE Dynamic SVID Zero-Downtime Socket Rebind Protocol defines an industrial-grade behavioral standard for security engineering. Enforces dynamic, in-memory X.509 SVID certificate rotation driven by the SPIRE Workload API without dropping active long-lived HTTP/2 or gRPC transport sessions. Mandates dynamic TLS context swapping and atomic socket inheritance or session re-handshaking to prevent process teardowns during sub-hour certificate lifetimes. Forbids destructive server restarts and naive socket tear-down during cryptographic renewal cycles. 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 Process Restarts and Abrupt Socket Destruction During Ephemeral SVID Rotation 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 Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Hard Process Restarts and Abrupt Socket Destruction During Ephemeral SVID Rotation	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 Inconsistency	AI 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:

Engineers MUST ALWAYS implement continuous streaming watchers against the SPIRE Workload API via domain sockets to receive rotated X.509 SVIDs asynchronously before expiration.

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.