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: rfc-9449-dpop-hardware-enclave-key-rotation-standard

RFC 9449 DPoP Hardware-Bound Ephemeral Key Rotation Standard

Enforces cryptographic binding of OAuth 2.1 access and refresh tokens to non-exportable, hardware-enclave-backed asymmetric keys per RFC 9449. Mandates strict verification of DPoP proof claims (htm, htu, jti, iat, ath, nonce) and zero-trust key rotation intervals to neutralize token exfiltration and replay attacks.

Prohibited Anti-Pattern: Exportable Software-Managed Private Keys and Static DPoP Proof Reuse Across HTTP Requests

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: RFC 9449 DPoP Hardware-Bound Ephemeral Key Rotation Standard - Enforces cryptographic binding of OAuth 2.1 access and refresh tokens to non-exportable, hardware-enclave-backed asymmetric keys per RFC 9449. Mandates strict verification of DPoP proof claims (htm, htu, jti, iat, ath, nonce) and zero-trust key rotation intervals to neutralize token exfiltration and replay attacks.
globs: src/auth/**/*.{ts,tsx}, src/security/**/*.{ts,tsx}, src/lib/crypto/**/*.{ts,tsx}, src/middleware/**/*.{ts,tsx}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/rfc-9449-dpop-hardware-enclave-key-rotation-standard"
---

# RFC 9449 DPoP Hardware-Bound Ephemeral Key Rotation Standard

> **Severity**: CRITICAL | **Category**: security
> **Anti-Pattern Warning**: Exportable Software-Managed Private Keys and Static DPoP Proof Reuse Across HTTP Requests

## System Constraints
You are a Principal Engineer enforcing RFC 9449 DPoP Ephemeral Hardware Enclave Key Rotation Standard. Mandate non-exportable hardware-isolated asymmetric keys, strictly validated proof payloads, single-use jti nonces, correct ath hashes, and automated enclave key rotation cycles. Reject all software-extracted private keys and unhashed token transmissions.

## Strict Guidelines
- Engineers MUST ALWAYS generate DPoP keypairs within non-exportable cryptographic boundary contexts (e.g., SubtleCrypto with extractable: false, WebAuthn PRF, TPM 2.0, or Cloud HSM/Nitro Enclaves).
- Engineers MUST NOT persist raw asymmetric private keys in local storage, session storage, software heap dumps, or transferable unencrypted blobs.
- Code MUST compute and bind the access token hash ('ath') using SHA-256 (base64url-encoded) on all resource access requests accompanied by a Bearer/DPoP access token.
- Services MUST reject DPoP proof JWTs if 'htm' does not exactly match the uppercase HTTP request method, if 'htu' does not match the sanitized absolute target URI (excluding query and fragment), or if 'iat' falls outside a strict clock skew window (maximum 60 seconds).
- Components NEVER reuse a 'jti' (JWT ID) claim; all verified proof identifiers must be stored in a distributed fast cache (e.g., Redis) with TTL matching proof validity to prevent replay attacks.
- Services MUST enforce server-provided 'DPoP-Nonce' challenges when the authorization or resource server responds with an invalid/missing nonce error (HTTP 401 with DPoP-Nonce header).

## Bad vs Good Implementations
### RFC 9449 Hardware-Bound DPoP Proof Generator with Extractable: False

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The private key is maintained as an exportable string in memory or software storage, leaving it vulnerable to exfiltration. The 'jti' is static (enabling instant replay attacks), the 'ath' (access token hash) is absent, and the algorithm does not enforce hardware-enclave non-exportability.
```typescript
import jwt from 'jsonwebtoken';

// ANTI-PATTERN: Exportable software private key stored in memory/string
const softwarePrivateKey = process.env.SOFTWARE_DPOP_KEY!;

export async function createDPoPProof(method: string, url: string, accessToken?: string): Promise<string> {
  // Anti-pattern: Missing 'ath' computation, static jti, exportable software key
  const payload = {
    htm: method,
    htu: url,
    iat: Math.floor(Date.now() / 1000),
    jti: 'static-reused-token-id'
  };
  return jwt.sign(payload, softwarePrivateKey, { algorithm: 'RS256' });
}
```

#### Production Standard (Correct)
> **Standard**: Ensures the private key is generated with 'extractable: false', preventing memory-dump extraction. Generates a unique RFC 4122 UUID for 'jti', strictly normalizes 'htu', calculates the SHA-256 'ath' hash for token binding, supports dynamic server nonces, and uses the standardized ES256 curve.
```typescript
import { webcrypto } from 'node:crypto';

interface DPoPProofOptions {
  httpMethod: 'GET' | 'POST' | 'PUT' | 'PATCH' | 'DELETE';
  targetUri: string;
  accessToken?: string;
  serverNonce?: string;
}

export class EnclaveDPoPProvider {
  private keyPairPromise: Promise<CryptoKeyPair>;

  constructor() {
    // Invariant: Generate non-exportable hardware/isolated enclave keypair (ES256 / P-256)
    this.keyPairPromise = webcrypto.subtle.generateKey(
      { name: 'ECDSA', namedCurve: 'P-256' },
      false, // non-exportable: private key cannot be extracted from crypto boundary
      ['sign']
    );
  }

  public async generateProof(options: DPoPProofOptions): Promise<string> {
    const { privateKey, publicKey } = await this.keyPairPromise;
    const exportedJwk = await webcrypto.subtle.exportKey('jwk', publicKey);

    const header = {
      typ: 'dpop+jwt',
      alg: 'ES256',
      jwk: {
        kty: exportedJwk.kty,
        crv: exportedJwk.crv,
        x: exportedJwk.x,
        y: exportedJwk.y
      }
    };

    // Normalize URI: RFC 9449 Section 4.3 mandates absolute URI without query or fragment
    const parsedUrl = new URL(options.targetUri);
    const htu = `${parsedUrl.protocol}//${parsedUrl.host}${parsedUrl.pathname}`;

    const payload: Record<string, unknown> = {
      jti: webcrypto.randomUUID(),
      htm: options.httpMethod.toUpperCase(),
      htu,
      iat: Math.floor(Date.now() / 1000)
    };

    if (options.serverNonce) {
      payload.nonce = options.serverNonce;
    }

    if (options.accessToken) {
      const encoder = new TextEncoder();
      const tokenBytes = encoder.encode(options.accessToken);
      const hashBuffer = await webcrypto.subtle.digest('SHA-256', tokenBytes);
      const athBase64Url = Buffer.from(hashBuffer)
        .toString('base64url');
      payload.ath = athBase64Url;
    }

    const encoder = new TextEncoder();
    const encodedHeader = Buffer.from(JSON.stringify(header)).toString('base64url');
    const encodedPayload = Buffer.from(JSON.stringify(payload)).toString('base64url');
    const signingInput = `${encodedHeader}.${encodedPayload}`;

    const signature = await webcrypto.subtle.sign(
      { name: 'ECDSA', hash: { name: 'SHA-256' } },
      privateKey,
      encoder.encode(signingInput)
    );

    const encodedSignature = Buffer.from(signature).toString('base64url');
    return `${signingInput}.${encodedSignature}`;
  }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

HashiCorp Vault Enclave & Transit Engine MCP
Interface for interacting with hardware security modules (HSM) and transit secrets engines for hardware-bound asymmetric signatures.
Recommended Agent Skills (askills.dev)

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

Smallstep CLI (step)
Zero-trust identity and cryptographic utility for generating and inspecting DPoP tokens, JWKs, and enclave certificates.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: RFC 9449 DPoP Hardware-Bound Ephemeral Key Rotation Standard

RFC 9449 DPoP Hardware-Bound Ephemeral Key Rotation Standard defines an industrial-grade behavioral standard for security engineering. Enforces cryptographic binding of OAuth 2.1 access and refresh tokens to non-exportable, hardware-enclave-backed asymmetric keys per RFC 9449. Mandates strict verification of DPoP proof claims (htm, htu, jti, iat, ath, nonce) and zero-trust key rotation intervals to neutralize token exfiltration and replay attacks. 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: Exportable Software-Managed Private Keys and Static DPoP Proof Reuse Across HTTP Requests 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 DriftExportable Software-Managed Private Keys and Static DPoP Proof Reuse Across HTTP RequestsCritical
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 generate DPoP keypairs within non-exportable cryptographic boundary contexts (e.g., SubtleCrypto with extractable

Engineers MUST ALWAYS generate DPoP keypairs within non-exportable cryptographic boundary contexts (e.g., SubtleCrypto with extractable: false, WebAuthn PRF, TPM 2.0, or Cloud HSM/Nitro Enclaves).

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 NOT persist raw asymmetric private keys in local storage, session storage, software heap dumps, or transferable unencrypted blobs.

Engineers MUST NOT persist raw asymmetric private keys in local storage, session storage, software heap dumps, or transferable unencrypted blobs.

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

Code MUST compute and bind the access token hash ('ath') using SHA-256 (base64url-encoded) on all resource access requests accompanied by a Bearer/DPoP access token.

Code MUST compute and bind the access token hash ('ath') using SHA-256 (base64url-encoded) on all resource access requests accompanied by a Bearer/DPoP access token.

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 reject DPoP proof JWTs if 'htm' does not exactly match the uppercase HTTP request method, if 'htu' does not match the sanitized absolute target URI (excluding query and fragment), or if 'iat' falls outside a strict clock skew window (maximum 60 seconds).

Services MUST reject DPoP proof JWTs if 'htm' does not exactly match the uppercase HTTP request method, if 'htu' does not match the sanitized absolute target URI (excluding query and fragment), or if 'iat' falls outside a strict clock skew window (maximum 60 seconds).

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 reuse a 'jti' (JWT ID) claim

Components NEVER reuse a 'jti' (JWT ID) claim; all verified proof identifiers must be stored in a distributed fast cache (e.g., Redis) with TTL matching proof validity to prevent replay attacks.

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

Services MUST enforce server-provided 'DPoP-Nonce' challenges when the authorization or resource server responds with an invalid/missing nonce error (HTTP 401 with DPoP-Nonce header).

Services MUST enforce server-provided 'DPoP-Nonce' challenges when the authorization or resource server responds with an invalid/missing nonce error (HTTP 401 with DPoP-Nonce header).

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 RFC 9449 DPoP Hardware-Bound Ephemeral Key Rotation Standard critical for AI coding assistants?

Enforces cryptographic binding of OAuth 2.1 access and refresh tokens to non-exportable, hardware-enclave-backed asymmetric keys per RFC 9449. Mandates strict verification of DPoP proof claims (htm, htu, jti, iat, ath, nonce) and zero-trust key rotation intervals to neutralize token exfiltration and replay attacks. 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 (Exportable Software-Managed Private Keys and Static DPoP Proof Reuse Across HTTP Requests) 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

RFC