Skip to main content
Founding Partner + 7-Day Trial
Back to docs
PQC-FED-001PQC-CNSA-003PQC-SLHDSA-001HIGHNSA CNSA 2.0 · CNSSP-15 · OMB M-23-02 · NIST SP 800-208

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

terminal · zsh
# 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)

terminal · zsh
# 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