FIDO2 Hardware Enterprise Attestation & FIDO MDS3 Cryptographic Verification Standard

--- description: FIDO2 Hardware Enterprise Attestation & FIDO MDS3 Cryptographic Verification Standard - Mandates strict cryptographic validation of WebAuthn registration attestation statements, certificate chains, and AAGUIDs against the FIDO Alliance Metadata Service (MDS3) root of trust. Prevents software-emulated authenticators, compromised keys, and non-compliant tokens from enrolling in zero-trust enterprise perimeters. globs: src/**/auth/**/*.{ts,tsx}, src/**/webauthn/**/*.{ts,tsx}, src/**/identity/**/*.{ts,tsx}, src/**/services/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/fido2-enterprise-attestation-mds-verification-standard" --- # FIDO2 Hardware Enterprise Attestation & FIDO MDS3 Cryptographic Verification Standard > **Severity**: CRITICAL | **Category**: security > **Anti-Pattern Warning**: Accepting unverified 'none' attestation or skipping cryptographic MDS root chaining during WebAuthn credential enrollment. ## System Constraints You are a Principal Security Architect enforcing FIDO2 WebAuthn Hardware Enterprise Attestation Verification. You must guarantee that zero-trust registration endpoints reject software-emulated authenticators. Enforce explicit attestation conveyance ('direct' or 'enterprise'), strict validation of the attestation statement (e.g., packed, fido-u2f) against the FIDO Alliance Metadata Service (MDS3) root certificates, verification that the AAGUID embedded in the certificate matches authData, and validation that authenticator security characteristics meet enterprise compliance standards. ## Strict Guidelines - Engineers MUST ALWAYS set attestation conveyance preference to 'enterprise' or 'direct' in registration options; 'none' is strictly prohibited for zero-trust perimeters. - Engineers MUST ALWAYS cryptographically verify the leaf attestation certificate against cached FIDO MDS3 BLOB trust anchors using full X.509 path validation (including revocation checks via CRL/OCSP). - Services MUST extract the AAGUID from authenticator data (authData.attestationData.aaguid) and verify exact byte parity against the AAGUID encoded in the X.509 cert extension (OID 1.3.6.1.4.1.45724.1.1.4). - Services MUST reject enrollment if the authenticator's MDS status indicates compromise, such as 'USER_VERIFICATION_BYPASS', 'ATTESTATION_KEY_COMPROMISE', or 'REVOKED'. - Components NEVER persist public keys or complete enrollment before attestation verification, AAGUID policy evaluation, and cryptographic signature validation succeed completely. ## Bad vs Good Implementations ### WebAuthn Registration Verification with FIDO MDS3 Hardware Attestation #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Accepts credentials without enforcing attestation statement verification or validating the device AAGUID against the FIDO Metadata Service (MDS3). An attacker or compromised device can supply a virtual software authenticator generating software-bound keys. ```typescript import { verifyRegistrationResponse } from '@simplewebauthn/server'; import type { RegistrationResponseJSON } from '@simplewebauthn/types'; export async function registerDevice(userId: string, response: RegistrationResponseJSON, expectedChallenge: string) { // INSECURE: Relies on default verification which allows 'none' attestation // and bypasses FIDO MDS hardware root validation. const verification = await verifyRegistrationResponse({ response, expectedChallenge, expectedOrigin: 'https://identity.enterprise.internal', expectedRPID: 'identity.enterprise.internal', requireUserVerification: true, }); if (!verification.verified || !verification.registrationInfo) { throw new Error('Registration failed verification'); } // Flaw: Software emulators (e.g., VirtualBox, software passkeys) can register // without proving physical hardware security module or FIPS certification. const { credentialID, credentialPublicKey, counter } = verification.registrationInfo; return await saveCredential(userId, credentialID, credentialPublicKey, counter); } ``` #### Production Standard (Correct) > **Standard**: Enforces direct cryptographic verification, rejects unauthenticated '00000000-...' software authenticators, cross-references device AAGUID and cert status against the FIDO MDS3 metadata cache, rejects revoked hardware, and limits enrollment strictly to enterprise-approved hardware security keys. ```typescript import { verifyRegistrationResponse } from '@simplewebauthn/server'; import type { RegistrationResponseJSON } from '@simplewebauthn/types'; import { fidoMdsClient } from '../crypto/fido-mds-client'; const ZERO_TRUST_ALLOWED_AAGUIDS = new Set([ 'cb69481e-8ff7-4039-93ec-0a2729a1e67d', // YubiKey 5 Series 'fa2b99dc-9e39-4257-8f9a-0f8824f1414e', // YubiKey 5 FIPS ]); export async function registerDevice(userId: string, response: RegistrationResponseJSON, expectedChallenge: string) { // Invariant 1: Cryptographic attestation verification with MDS3 integration const verification = await verifyRegistrationResponse({ response, expectedChallenge, expectedOrigin: 'https://identity.enterprise.internal', expectedRPID: 'identity.enterprise.internal', requireUserVerification: true, }); const { verified, registrationInfo } = verification; if (!verified || !registrationInfo) { throw new Error('WebAuthn cryptographic verification failed'); } const { aaguid, attestationObject } = registrationInfo; // Invariant 2: Deny zero-UUIDs indicating lack of hardware-bound attestation if (!aaguid || aaguid === '00000000-0000-0000-0000-000000000000') { throw new Error('Self-attested or software authenticators are prohibited'); } // Invariant 3: Validate against FIDO MDS3 trust anchors & check revocation const mdsEntry = await fidoMdsClient.findMetadataByAaguid(aaguid); if (!mdsEntry) { throw new Error(`AAGUID ${aaguid} is not recognized by FIDO MDS3`); } const isRevokedOrCompromised = mdsEntry.statusReports.some((report) => ['USER_VERIFICATION_BYPASS', 'ATTESTATION_KEY_COMPROMISE', 'REVOKED'].includes(report.status) ); if (isRevokedOrCompromised) { throw new Error('Authenticator model is flagged as compromised in FIDO MDS'); } // Invariant 4: Enforce Enterprise Perimeter Hardware Allowlist if (!ZERO_TRUST_ALLOWED_AAGUIDS.has(aaguid)) { throw new Error(`Device model ${aaguid} not authorized for zero-trust perimeter`); } const { credentialID, credentialPublicKey, counter } = registrationInfo; return await saveCredential(userId, credentialID, credentialPublicKey, counter, aaguid); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: FIDO2 Hardware Enterprise Attestation & FIDO MDS3 Cryptographic Verification Standard

FIDO2 Hardware Enterprise Attestation & FIDO MDS3 Cryptographic Verification Standard defines an industrial-grade behavioral standard for security engineering. Mandates strict cryptographic validation of WebAuthn registration attestation statements, certificate chains, and AAGUIDs against the FIDO Alliance Metadata Service (MDS3) root of trust. Prevents software-emulated authenticators, compromised keys, and non-compliant tokens from enrolling in zero-trust enterprise perimeters. 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: Accepting unverified 'none' attestation or skipping cryptographic MDS root chaining during WebAuthn credential enrollment. 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	Accepting unverified 'none' attestation or skipping cryptographic MDS root chaining during WebAuthn credential enrollment.	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 set attestation conveyance preference to 'enterprise' or 'direct' in registration options

Engineers MUST ALWAYS set attestation conveyance preference to 'enterprise' or 'direct' in registration options; 'none' is strictly prohibited for zero-trust perimeters.

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.