← Back to All Articles
Quantum & PQCnull

Post-Quantum Cryptography (PQC) Readiness: CBOM Discovery, NIST FIPS 203/204/205, RFC 10024, and TLS Crypto-Agility

Enterprise crypto-agility architecture against Harvest Now, Decrypt Later threats using NIST FIPS 203/204/205 and IETF RFC 10024, read-only Windows TLS and Azure Key Vault CBOM inventory, Application Gateway KQL auditing, and critical production risk analysis.

·12 min read·
#Quantum#PQC#Crypto-Agility#CBOM#Azure Key Vault#TLS 1.3
Post-Quantum Cryptography (PQC) Readiness: CBOM Discovery, NIST FIPS 203/204/205, RFC 10024, and TLS Crypto-Agility

Executive Summary

Transitioning an enterprise to Post-Quantum Cryptography (PQC) is not a single software update; it is an architectural discipline built on crypto-agility across transport gateways, Hardware Security Modules (HSMs), Public Key Infrastructure (PKI), and application dependencies. This guide defines how security architects establish an accurate Cryptography Bill of Materials (CBOM), distinguish finalized NIST and IETF standards from pending drafts, audit live Windows Schannel and Azure Key Vault inventories, and evaluate critical production failure modes before enforcing hybrid key agreement.

Problem Definition, Business Need, and Mosca's Inequality

Executive prioritization for cryptographic migration rests on Mosca's inequality: X + Y > Z.

  • X (Confidentiality Shelf Life): The number of years regulated telemetry, financial records, intellectual property, or healthcare archives must remain confidential.
  • Y (Migration Timeline): The time required to inventory cryptographic assets, upgrade HSM firmware, modernize PKI roots, and rotate client/server software stacks.
  • Z (Quantum Horizon): The estimated timeframe until fault-tolerant quantum computers can break classical asymmetric cryptography at practical scale.

Whenever X + Y > Z, an organization faces immediate exposure even though cryptographically relevant quantum computers do not yet exist in public operation. Passive network collection turns future decryption risk into a present-day architectural problem.

Threat Model: Shor, Grover, and Passive Capture Exposure

Architects must separate asymmetric key-compromise threats from symmetric key adjustments:

  • Harvest Now, Decrypt Later (Shor's Algorithm): Passive adversaries capturing TLS traffic or cross-region replication streams today can archive ciphertext until Shor's algorithm renders classical integer factorization and discrete logarithm assumptions (RSA, DH, ECDH, ECDSA) obsolete.
  • Active Impersonation and Supply Chain Forgery: Without post-quantum digital signatures, future attackers could forge X.509 leaf or intermediate certificates, software package signatures, and firmware trust anchors.
  • Symmetric Ciphers and Hashing (Grover's Algorithm): Grover's search algorithm quadratically weakens brute-force resistance rather than causing exponential collapse. Moving from AES-128 to `AES-256` and standardizing on `SHA-384` / `SHA-512` preserves adequate post-quantum security margins without replacing symmetric primitives.

Standards Maturity and Platform Dependencies

Procurement and engineering roadmaps must separate finalized standards from pending drafts:

  • NIST FIPS 203 — ML-KEM (Finalized Standard, August 2024): Module-Lattice-Based Key-Encapsulation Mechanism serving as the primary standard for general encryption and key establishment.
  • NIST FIPS 204 — ML-DSA (Finalized Standard, August 2024): Primary lattice-based digital signature standard for X.509 certificate chains and software artifact verification.
  • NIST FIPS 205 — SLH-DSA (Finalized Standard, August 2024): Stateless hash-based signature standard delivering larger signatures but mathematical diversity from lattices, suited as a conservative fallback for long-lived root authorities.
  • IETF RFC 10024 — Hybrid ECDHE-MLKEM Key Agreement for TLS 1.3 (Published Proposed Standard, August 2026): Formally standardized from the earlier draft-ietf-tls-ecdhe-mlkem effort, specifying `X25519MLKEM768` (IANA code point 0x11EC), SecP256r1MLKEM768, and SecP384r1MLKEM1024.
  • NIST FIPS 206 (`FN-DSA` / Falcon) and Backup KEM `HQC` (Draft / In Progress): Compact lattice signature candidate FIPS 206 remains in draft development. Likewise, HQC (*Hamming Quasi-Cyclic*), selected by NIST in March 2025 as an error-correcting-code backup KEM to diversify beyond lattices, is still progressing through FIPS drafting toward an anticipated ~2027 finalization. Architects should track both for cryptographic diversity without delaying FIPS 203/204/205 planning.

Operating System, Protocol, and Network Constraints

  • Strict TLS 1.3 Prerequisite: TLS 1.0, TLS 1.1, and TLS 1.2 do not and will not support post-quantum key exchange. Only TLS 1.3 accommodates hybrid ML-KEM negotiation. Any application locked to TLS 1.2 remains unprotected against passive HNDL capture.
  • Windows SymCrypt and Schannel Readiness: Windows 11 and Windows Server 2025 expose native ML-KEM and ML-DSA primitives in SymCrypt/CNG, with Schannel hybrid TLS 1.3 key exchange rolled out through mid-2026 servicing updates. Hybrid groups are generally disabled or deprioritized by default for backward compatibility and require explicit Group Policy or registry configuration for staged rollout.
  • TCP MSS and Middlebox Fragmentation: Whereas classical X25519 transmits a 32-byte key share, X25519MLKEM768 expands the client share to roughly 1,216 bytes. Combined with standard TLS extensions, ClientHello frequently exceeds the 1,460-byte TCP Maximum Segment Size (MSS), spanning two TCP segments. Legacy firewalls and inline DPI proxies that fail to reassemble fragmented ClientHello frames will drop or reset connections.

Target Crypto-Agile Architecture

A defensible architecture separates modernization into three decoupled layers:

  • CBOM Discovery Plane: Continuous read-only telemetry across Windows Schannel policies, Azure Key Vault / Managed HSM key inventories, and Application Gateway TLS negotiation logs.
  • Transport Plane: Deprecate TLSv1.0, TLSv1.1, and CBC cipher suites; enforce TLS 1.3 across public ingress and backend APIs; validate X25519MLKEM768 interoperability in staging zones behind all corporate firewalls.
  • Identity, RBAC, and HSM Governance: Enforce least-privilege separation in Azure Key Vault by restricting audit automation to Key Vault Reader while gating key rotation behind Entra Privileged Identity Management (Key Vault Crypto Officer).

Technical Implementation: Read-Only PowerShell CBOM Audit

The script below operates strictly in read-only mode without mutating host or cloud state.

  • Execution Environment: Windows PowerShell 5.1 or PowerShell 7.4+ with built-in Windows TLS module and Az.Accounts / Az.KeyVault modules.
  • Required Permissions: Standard local read access for Get-TlsCipherSuite; Azure Key Vault Reader RBAC role (plus Key Vault Keys/Get and Keys/List permissions) for Key Vault auditing.
  • Security Control Served: Cryptographic Asset Visibility and Legacy Protocol Deprecation Baseline.
  • Operational Notes & Error Handling: Run against a non-production Key Vault first to measure API throttling if hundreds of keys exist. Note that Get-TlsCipherSuite returns HashLength = 0 for AEAD ciphers such as AES-GCM because integrity is built into GCM rather than a separate HMAC; similarly, numeric protocol identifiers in Protocols map 771 to TLS 1.2 and 65277 to TLS 1.3 in CNG internals.
powershell
#Requires -Modules TLS, Az.Accounts, Az.KeyVault
# Purpose: Read-only inventory of Windows TLS cipher suite order and Azure Key Vault key types/sizes.
[CmdletBinding()]
param(
    [Parameter(Mandatory = $true)]
    [ValidateNotNullOrEmpty()]
    [string]$VaultName
)

$ErrorActionPreference = 'Stop'

Write-Host "[1/2] Auditing local Windows TLS cipher suites..." -ForegroundColor Cyan
Get-TlsCipherSuite |
    Select-Object Name, Exchange, Cipher, HashLength, @{
        Name       = 'Protocols'
        Expression = { ($_.Protocols -join ',') }
    } |
    Sort-Object Exchange, Name |
    Format-Table -AutoSize

Write-Host "[2/2] Auditing Azure Key Vault ($VaultName) cryptographic keys..." -ForegroundColor Cyan
try {
    if (-not (Get-AzContext)) {
        Connect-AzAccount | Out-Null
    }

    # Query individual key objects so KeyType, KeySize, and CurveName properties are fully populated.
    $KeyList = Get-AzKeyVaultKey -VaultName $VaultName
    $Inventory = foreach ($Item in $KeyList) {
        $FullKey = Get-AzKeyVaultKey -VaultName $VaultName -Name $Item.Name
        [PSCustomObject]@{
            VaultName   = $VaultName
            KeyName     = $FullKey.Name
            KeyType     = $FullKey.KeyType
            KeySize     = $FullKey.KeySize
            CurveName   = $FullKey.CurveName
            Enabled     = $FullKey.Enabled
            ExpiresUtc  = $FullKey.Expires
            PqcStatus   = if ($FullKey.KeyType -in @('RSA', 'RSA-HSM', 'EC', 'EC-HSM')) {
                'Classical-Asymmetric-Track'
            } else {
                'Symmetric-Or-Other'
            }
        }
    }

    $Inventory | Format-Table -AutoSize
} catch {
    Write-Warning "Failed to read Key Vault inventory due to permissions or network rules: $($_.Exception.Message)"
}

Security Verification via Azure Application Gateway KQL

Before mandating TLS 1.3 and hybrid key agreement on public ingress, confirm which external integrations still negotiate legacy TLS protocols.

  • Data Source & Workspace: Azure Application Gateway diagnostic logs streamed to Log Analytics (AzureDiagnostics, Category == "ApplicationGatewayAccessLog").
  • Required Permissions: Log Analytics Reader on the target workspace.
  • Control Served & Limitation: Legacy TLS dependency elimination. Standard ApplicationGatewayAccessLog fields capture negotiated TLS version and cipher suite strings rather than granular post-quantum hybrid group names such as X25519MLKEM768.
kql
// Data Source: Azure Application Gateway Diagnostics -> Log Analytics (AzureDiagnostics)
// Prerequisite: ApplicationGatewayAccessLog category must be enabled for the target gateway.
AzureDiagnostics
| where TimeGenerated > ago(14d)
| where Category == "ApplicationGatewayAccessLog"
| summarize
    RequestCount = count(),
    SampleClients = make_set(clientIP_s, 10),
    SampleHosts = make_set(host_s, 10)
    by sslProtocol_s, sslCipher_s, sslEnabled_s
| extend RemediationFlag = case(
    sslProtocol_s in ("TLSv1.0", "TLSv1.1"), "Urgent-Legacy-TLS-Removal",
    sslCipher_s has "CBC", "Weak-CBC-Cipher-Cleanup",
    "Modern-TLS-Ready"
)
| order by RequestCount desc

Critical Architectural Assessment

  • What Risk It Mitigates: Hybrid X25519MLKEM768 under TLS 1.3 (RFC 10024) directly reduces HNDL confidentiality risk for data in transit without sacrificing classical X25519 security properties.
  • What Risks It Does NOT Mitigate: Hybrid key agreement alone does not harden classical RSA or ECDSA X.509 certificate authentication against future active quantum impersonation (that requires FIPS 204 ML-DSA certificate chains), nor does it remediate plaintext data leakage, weak authorization, or legacy TLS 1.2 clients.
  • New Dependencies Introduced: Strict dependency on OS builds supporting SymCrypt/Schannel PQC groups, middlebox/firewall inspection engines tolerant of multi-packet ClientHello handshakes, and vendor HSM firmware roadmaps for post-quantum signing.
  • Production Failure Conditions: Enforcing strict TLS 1.3 prematurely severs legacy B2B/IoT integrations; enabling hybrid key shares behind legacy DPI devices can trigger silent TCP resets during initial handshakes.
  • Rollback Strategy: Maintain exported Schannel Group Policy baselines and previous custom Application Gateway SSL policy templates. If handshake timeouts spike in pilot rings, revert hybrid curve priority behind X25519/P-256 or restore the prior approved TLS policy template within minutes.

Implementation Roadmap

  • Phase 1 (0–30 Days): Run Get-TlsCipherSuite, Get-AzKeyVaultKey, and AzureDiagnostics KQL baselines to complete the CBOM and retire TLS 1.0/1.1 and CBC ciphers.
  • Phase 2 (30–90 Days): Enable hybrid X25519MLKEM768 in staging environments on Windows Server 2025 / edge proxies for high-sensitivity workloads and verify middlebox MTU reassembly.
  • Phase 3 (90+ Days): Promote hybrid TLS 1.3 to production ingress while aligning HSM/PKI procurement with vendor ML-DSA (FIPS 204) and SLH-DSA (FIPS 205) support milestones.

Verified Primary Sources & Open-Source Repositories

This architectural guide was cross-corroborated against the official advisories, Microsoft Learn docs, and open-source PowerShell / KQL repositories below.

Multi-Channel Distribution Summary (X & LinkedIn Draft)

Toggle X (Twitter) & LinkedIn sharing drafts
X (Twitter) Draft

PQC transition is architectural crypto-agility, not a checkbox patch. Updated blueprint covering NIST FIPS 203/204/205, RFC 10024 (X25519MLKEM768), draft FN-DSA/HQC status, Windows Schannel + Key Vault CBOM PowerShell, and TCP MSS middlebox risks. #PQC #CryptoAgility

LinkedIn Draft

Rebuilt our Post-Quantum Cryptography (PQC) engineering blueprint from a senior security architect perspective: Mosca's inequality, finalized FIPS 203/204/205 vs. draft FIPS 206/HQC status, RFC 10024 hybrid TLS 1.3 key agreement, least-privilege CBOM PowerShell discovery, KQL telemetry, and rollback design.