CONCEPT Cited by 1 source
Supply-chain pressure¶
Definition¶
Supply-chain pressure is the adoption strategy where a large buyer (typically a government or dominant enterprise) uses procurement requirements to force vendors throughout the supply chain to adopt a technology standard on a fixed timeline. The pressure cascades: products built to satisfy the dominant buyer's requirements become the default offering for all customers.
PQC example (EO 14409)¶
The U.S. federal government uses this mechanism for PQC migration:
- FAR Council rules require covered federal contractors to comply with NIST PQC FIPS by December 2030.
- CISA product categories designate which technology sectors must be PQC-capable "now" (widely available) vs. still transitioning.
- Procurement preference — agencies are directed to favor PQC-capable vendors in mature markets immediately.
The deadline for contractors (2030) is set one year before agencies' own authentication deadline (2031) — ensuring the vendor ecosystem is ready before agencies need it.
Products that vendors build to federal requirements will end up used by hospitals, banks, universities, and small businesses, which makes PQC support more broadly available. (Source: sources/2026-06-23-cloudflare-post-quantum-eo-milestone)
Historical precedents¶
The same mechanism drove adoption of: - IPv6 — federal mandate preceded broad commercial deployment - RPKI — routing security standards catalyzed by government adoption - DNSSEC — federal deployment created vendor/resolver support that then became available to all
Seen in¶
- sources/2026-06-23-cloudflare-post-quantum-eo-milestone — EO contractor requirements as PQC adoption forcing function