ANKASecure Regulatory Compliance Matrix

Version: 3.0.0
Last Updated: January 2026

Overview

ANKASecure supports multi-regional post-quantum cryptography compliance through policy-based enforcement aligned with global regulatory requirements.

This document provides a comprehensive mapping of ANKASecure capabilities against regulatory requirements from:

• NIST (USA) - National Institute of Standards and Technology
• BSI (Germany) - Federal Office for Information Security
• ANSSI (France) - National Cybersecurity Agency
• ETSI (EU) - European Telecommunications Standards Institute
• ENISA (EU) - EU Cybersecurity Agency

Compliance Status by Regulation

Template-to-Regulation Mapping

Algorithm Support Matrix

ML-KEM (Key Encapsulation Mechanism)

ML-DSA (Digital Signature Algorithm)

Classical Algorithms

Regulatory Requirements Detail

BSI (Germany) - BSI TR-02102-1

Authority: Federal Office for Information Security (Bundesamt für Sicherheit in der Informationstechnik)
Document: TR-02102-1 - Cryptographic Mechanisms: Recommendations and Key Lengths Scope: German federal agencies, critical infrastructure

Key Requirements:

1. Hybrid Mandatory until 2030: PQC-only solutions considered immature
2. Exception: Hash-based signatures (SLH-DSA, XMSS, LMS) can be standalone
3. Minimum Level 3: 192-bit security for government/critical infrastructure
4. Deprecated: RSA-2048 as of December 31, 2025
5. Brainpool Sunset: Classical-only Brainpool use deprecated after December 31, 2031 (BSI TR-02102-3)
6. Brainpool Hybrid: After 2031, Brainpool must be combined with ML-KEM or ML-DSA
7. Hybridisation mechanisms: CatKDF, or the SP 800-227 KeyCombine construction (TR-02102-1 Version 2026-01 §2.2, Table 2.1); the cascade combiner (CasKDF) is not among them

ANKASecure Compliance:

• ✅ Template: BSI_HYBRID_ENFORCED
• ✅ Enforces hybrid-only for ML-KEM/ML-DSA
• ✅ Blocks Level 1 algorithms
• ✅ FrodoKEM is admitted by BSI_COMPLIANT; BSI_HYBRID_ENFORCED does not declare it, because no catalogued composite has a FrodoKEM component
• ✅ Supports Brainpool curves at levels 3 and 5 (brainpoolP384r1, brainpoolP512r1) - German government standard; brainpoolP256r1 is level 1, below the template floor
• ✅ Admits exactly four hybrid combinations, the L3/L5 Brainpool pairs: brainpoolP384r1+ML-KEM-1024, brainpoolP512r1+ML-KEM-1024, brainpoolP384r1+ML-DSA-87 and brainpoolP512r1+ML-DSA-87. No NIST P-curve, OKP (X25519, X448, Ed25519, Ed448), FALCON or HQC pair is admitted
• ✅ Sunset date enforcement: Dec 31, 2031 for classical-only Brainpool
• ✅ allowedKdfs is HKDF-SHA256 and CatKDF; a composite KEM key naming CasKDF is refused

ANSSI (France) - ANSSI RGS v2

Authority: Agence Nationale de la Sécurité des Systèmes d'Information
Document: ANSSI Position Papers on PQC Transition (2022, 2023, 2024) Scope: French defense, government, critical infrastructure

Key Requirements:

1. Strong Hybridization: "PQC not yet mature enough for standalone use"
2. Dual Signatures: Both classical and PQC signatures must be valid
3. Minimum Level 3: 192-bit security baseline
4. Hybridation modes: the ETSI TS 103 744 CatKDF and CasKDF combiners, both "backed-up by security proofs" (2023 follow-up §3.1); ANSSI-PG-083 §2.2 asks for a well-chosen key derivation function

ANKASecure Compliance:

• ✅ Template: ANSSI_HYBRID_ENFORCED
• ✅ Enforces hybrid-only (strongest mandate)
• ✅ allowedKdfs is HKDF-SHA256, CatKDF and CasKDF
• ✅ FALCON-1024 is admitted standalone by ANSSI_COMPLIANT; ANSSI_HYBRID_ENFORCED does not declare FALCON, because no catalogued composite has a FALCON component
• ✅ No OKP algorithm or pair (X25519, X448, Ed25519, Ed448) is admitted: none carries ANSSI

ETSI (EU) - ETSI TS 103 744

Authority: European Telecommunications Standards Institute
Document: TS 103 744 V1.2.2 (2026-02) - Quantum-safe Hybrid Key Establishment Scope: EU telecommunications operators, 5G/6G networks

Key Requirements:

1. CatKDF/CasKDF Combiners: Specified in TS 103 744 §8.2.3 and §8.3.3
2. Focus on KEM: Key establishment for network encryption
3. Approved post-quantum KEM: ML-KEM (§7.6.2)
4. Parameter sets: The curve/ML-KEM pairs and KDFs §7.7.2 enumerates

ANKASecure support:

• ✅ Template: ETSI_HYBRID_ENFORCED
• ✅ CatKDF and CasKDF on ten of the curve/ML-KEM pairs §7.7.2 enumerates, with the HKDF KDF
• ✅ COMPOSITE_KEM_COMBINE mode restriction
• ✅ HQC pairings as the platform's code-based diversity option, beside the ML-KEM pairs

NIST (USA) - SP 800-227

Authority: National Institute of Standards and Technology
Documents:

• SP 800-227 - Recommendations for Key-Encapsulation Mechanisms
• SP 800-56C Rev. 2 - Recommendation for Key-Derivation Methods

Scope: US federal agencies, defense contractors, FIPS compliance

Key Requirements:

1. Key combiner for hybrids: SP 800-227 (final, September 2025) §4.6.2 approves a two-step KDM (HKDF) over the hybrid shared secret, with the ciphertexts, encapsulation keys and a domain separator bound into FixedInfo
2. FIPS 203/204/205: ML-KEM, ML-DSA, SLH-DSA standards
3. Hybrid Optional: Not mandated, permitted
4. Deprecation Timeline: 112-bit algorithms by 2030

ANKASecure Compliance:

• ✅ Template: NIST_HYBRID_OPTIONAL
• ✅ HKDF-SHA256 as the SP 800-227 §4.6.2 approved combiner (HKDF-SHA384/512 also implemented; not in the seeded template)
• ✅ FIPS 203/204/205 algorithms supported
• ✅ Standalone PQC allowed (US market flexibility)

ENISA (EU) - PQC Guidelines

Authority: European Union Agency for Cybersecurity
Documents:

• Post-Quantum Cryptography: Current state and quantum mitigation (2021)
• Post-Quantum Cryptography - Integration study (2022)

Scope: EU member states, EU cybersecurity framework

Key Requirements:

1. Risk-Based Approach: Hybrid for high-risk, flexible for others
2. Symmetric Key Adjustment: Increase lengths for quantum resistance
3. Migration Strategy: Gradual transition with hybrid schemes
4. Crypto-Agility: Support multiple algorithms

ANKASecure Compliance:

• ✅ Template: ENISA_RISK_BASED
• ✅ Hybrid recommended (not mandatory)
• ✅ Level 3 minimum for high-risk
• ✅ Full algorithm portfolio for crypto-agility

KDF Support by Regulation

The platform's KDF vocabulary is HKDF-SHA256, HKDF-SHA384, HKDF-SHA512, CatKDF, CasKDF; a template's allowedKdfs names the subset its keys may be created, imported, rotated or transitioned with.

Security Level Mappings

See Also

• Policy Templates^*
• Policy Enforcement Guide
• Template Selection Guide
• Composite Keys Overview^*