Identity (OIDC / SAML / FIDO2 WebAuthn) & Cloud KMS Envelope Keys
Severity: HIGH
Enterprise identity providers (Okta, Keycloak, Microsoft Entra ID, Ping, Active Directory CS) and cloud key management services (AWS KMS, Google Cloud KMS, Azure Key Vault, HashiCorp Vault) anchor workforce authentication and envelope encryption. PQC-IAM-001 identifies OIDC discovery documents pinned solely to RS256/ES256 and FIDO2 WebAuthn pubKeyCredParams restricted to ES256 (-7) and RS256 (-257) without COSE ML-DSA (-48/-49/-50) agility. PQC-KMS-001 and PQC-CLOUD-001 detect Terraform and cloud configs provisioning classical RSA_2048 or ECC_NIST_P256 KMS signing/KEM keys.
Remediation checklist
- Append COSE ML-DSA-65 (alg: -49) and ML-DSA-87 (alg: -50) ahead of ES256 (-7) in WebAuthn pubKeyCredParams so PQC-capable authenticators negotiate lattice signatures cleanly.
- Upgrade Terraform signing keys (aws_kms_key customer_master_key_spec = "ML_DSA_65", google_kms_crypto_key_version_template algorithm = "KEM_ML_KEM_768") using ciphermap fix . --dry-run --offline.
- Collect live sanitized IAM/K8s/Cloud/AD configurations without exposing secrets via ciphermap collect cloud -o ./sanitized-configs.
Illustrative Code Examples
These fragments explain migration direction. They are not complete applications or compiler-verified patches for your project.
Vulnerable — classical RSA-2048 AWS KMS signing key & ES256/RS256-only WebAuthn
resource "aws_kms_key" "jwt_signer" {
key_usage = "SIGN_VERIFY"
customer_master_key_spec = "RSA_2048"
}Remediated — FIPS 204 ML-DSA-65 AWS KMS signing key (auto-upgraded by ciphermap fix)
resource "aws_kms_key" "jwt_signer" {
key_usage = "SIGN_VERIFY"
customer_master_key_spec = "ML_DSA_65"
}Scan your own repository for PQC-IAM-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-FED-001NSA CNSA 2.0 Category-5 Floor, PIV/CAC & Firmware Signatures
PQC-BANK-002Banking TR-31/TR-34 Key Blocks, Mainframe ICSF & Open Banking FAPI 2.0
PQC-OT-001OT/ICS OPC UA, IEC 62443 Secure Boot & Healthcare DICOM/HL7 FHIR