PQC Open Intelligence Source Map

Signal: Federal high-value and high-impact systems have named 2030 key-establishment and 2031 signature deadlines.

Use: Anchor board and procurement timing to signed policy, not generic Q-Day speculation.

Signal: Agencies must prioritize critical IT, plan PQC migration, and manage cryptographic inventory work.

Use: Translate executive direction into operational evidence requirements for inventory, owners, and migration sequence.

Signal: FIPS 203, FIPS 204, and FIPS 205 are the principal standardized PQC algorithm references.

Use: Separate standards-backed migration claims from vendor-specific implementation claims.

Signal: CNSA 2.0 and related resources define the National Security System migration context.

Use: Keep civilian enterprise guidance distinct from classified or NSS-specific requirements.

Signal: CISA identifies categories where PQC support is available or still transitioning.

Use: Turn vendor-readiness claims into category-specific procurement questions.

Signal: Public telemetry tracks post-quantum encrypted browser traffic and origin-server readiness.

Use: Compare an organization's exposed surface against observable Internet adoption signals.

Signal: Cloudflare distinguishes key-establishment migration from authentication and certificate migration.

Use: Prevent a false green where TLS key agreement improves but signatures, roots, or code signing remain classical.

Signal: Google frames encryption and authentication as separate migration tracks with different urgency.

Use: Prioritize long-lived data exposure now while tracking the longer dependency chain for identity and signing.

Signal: IBM's public analysis frames harvest-now-decrypt-later risk and crypto-agility as present-tense enterprise work.

Use: Use an external enterprise reference point without treating it as endorsement.