NSA CNSA 2.0 Category-5 Floor, PIV/CAC & Firmware Signatures
Severity: HIGH
National Security Systems (NSS) governed by NSA CNSA 2.0 and CNSSP-15 enforce a strict Category-5 security floor: ML-KEM-1024 (FIPS 203) for key establishment, ML-DSA-87 (FIPS 204) for general signatures, LMS or XMSS (NIST SP 800-208) for stateful firmware/software signing, AES-256, and SHA-384 or SHA-512. Category-1/3 primitives (ML-KEM-512/768, ML-DSA-44/65) and stateless hash-based SLH-DSA (FIPS 205) do not satisfy CNSA 2.0 NSS baselines. PQC-FED-001 also inventories FIPS 201-3 PIV/CAC authentication slots (9A, 9C, 9D, 9E) and classical RSA/ECDSA firmware signing manifests.
Remediation checklist
- Upgrade NSS key establishment from X25519MLKEM768 or classical ECDH to SecP384r1MLKEM1024 or pure ML-KEM-1024, and general digital signatures to ML-DSA-87.
- Replace SLH-DSA in CNSA 2.0 NSS contexts with ML-DSA-87 for general signing or hardware-state-tracked LMS/XMSS (SP 800-208) for firmware signing.
- Generate a CNSA 2.0 CSfC compensating wrapper bundle via ciphermap fix . --wrapper cnsa-2.0 --offline and export dual OMB M-23-02 + CMMC 2.0 reports via ciphermap report . --omb-m23-02 --cmmc --offline.
Illustrative Code Examples
These fragments explain migration direction. They are not complete applications or compiler-verified patches for your project.
Flagged under CNSA 2.0 — Category-3 ML-KEM-768 or SLH-DSA in an NSS profile
# cnsa-nss-gateway.yaml tls_groups: "X25519MLKEM768" signature_scheme: "SLH-DSA-SHA2-128s"
Remediated — NSA CNSA 2.0 Category-5 suite (ML-KEM-1024 + ML-DSA-87 + SHA-384)
# cnsa-nss-gateway.yaml tls_groups: "SecP384r1MLKEM1024" signature_scheme: "ML-DSA-87" digest_floor: "SHA-384"
Scan your own repository for PQC-FED-001 locally (0 code egress)
Preview proposed changes free with ciphermap fix . --dry-run --offline --no-telemetry. Eligibility depends on the installed build, call shape, module format, and migration context. The bundled RSA fixture has a classical key-size candidate; that does not make it post-quantum secure. Persisted digests and unsupported contexts may be declined. Applying supported candidates requires an entitlement, explicit verifier consent, and the required project tools. Review the actual verification result before adopting a change.
Other rule families
Quantum-Vulnerable Public Key (RSA / DSA / DH)
PQC-GO-AST-003Quantum-Vulnerable Elliptic Curves (ECC) & Pre-Standard PQC Drafts
PQC-GO-AST-001Deprecated & Broken Cryptographic Primitives
IMM-SQLI-001Dynamic SQL String Interpolation or Concatenation Across Polyglot Drivers
IMM-PATH-001Unjailed Filesystem Path Traversal or Symlink Escape Across Polyglot I/O
IMM-CMD-001Dynamic Shell Command Execution Across Polyglot Process APIs
IMM-BOUND-001Unbounded Stream or Payload Allocation Across Polyglot Boundaries
IMM-DESER-001Unsafe Polymorphic Deserialization or Permissive Boundary Decoding
IMM-AUTH-001Unauthenticated or Unguarded State-Mutating Boundary Endpoint
IMM-TIMING-001Non-Constant-Time Secret, HMAC, or Webhook Signature Comparison
IMM-JWT-001Unverified JWT Signature Decoding Before Claims Trust
IMM-SSRF-001Unvalidated Server-Side Request Forgery (SSRF) & Cloud IMDS Exposure
IMM-AICFG-001AI Coding Agent Instruction & MCP Configuration Poisoning
IMM-CSPRNG-001Weak Non-Cryptographic PRNG in Security Token, OTP, or Secret Generation
IMM-REDIR-001Unvalidated Open Redirect from Raw HTTP Parameter
PQC-COOKIE-4KPQC Wire-Size Rollout Cliffs: 4KB Cookies, SQL VARCHAR(255) & HTTP 431 Headers
PQC-BANK-002Banking TR-31/TR-34 Key Blocks, Mainframe ICSF & Open Banking FAPI 2.0
PQC-IAM-001Identity (OIDC / SAML / FIDO2 WebAuthn) & Cloud KMS Envelope Keys
PQC-OT-001OT/ICS OPC UA, IEC 62443 Secure Boot & Healthcare DICOM/HL7 FHIR