Post-Quantum Cryptography: What’s Next for Edge Security
This article provides an overview of the post-quantum cryptography (PQC) landscape, covering newer signature algorithms (FN-DSA/Falcon, SLH-DSA), composite signatures, and the IETF PLANTS working group's development of Merkle Tree Certificates to address TLS handshake bloat. It notes that while symmetric encryption remains quantum-safe, the industry is accelerating PQC adoption timelines to 2029 in response to research suggesting cryptographically relevant quantum computers may arrive sooner than expected.
Detection / Hunteropenrouter
What Happened
This article explains how the cybersecurity industry is preparing for a future where quantum computers could break the encryption that currently protects internet communications. While symmetric encryption like AES-128 remains safe, the main concern is with digital signatures and key exchange used in TLS (the protocol that secures web browsing). New post-quantum algorithms are being standardized by NIST, but they produce much larger signatures, which slows down web connections—especially for newer protocols like HTTP/3. A new IETF working group called PLANTS is working on Merkle Tree Certificates to solve this size problem. Major companies like Google and Akamai are moving their quantum-safe deadlines up to 2029. Organizations should begin evaluating their cryptographic infrastructure and planning for the transition to post-quantum algorithms.
Key Takeaways
- FN-DSA (Falcon) offers smaller key/signature sizes than ML-DSA but is difficult to implement due to floating-point arithmetic and constant-time execution challenges.
- The IETF PLANTS working group is developing Merkle Tree Certificates (MTC) to reduce TLS handshake overhead caused by large PQC signatures, which can add 20-40 KB to initial server messages.
- Symmetric encryption (AES-128) and hash functions (SHA-256) remain secure against quantum threats; no transition to AES-256 is required.
- Google accelerated its quantum-safe timeline from 2035 to 2029, and Akamai plans to offer PQC certificates by 2029.
- Composite signatures combine traditional and post-quantum algorithms into a single signature, but introduce interoperability concerns due to combinatorial growth in identifiers.
Affected Systems
- TLS/SSL implementations
- Web PKI infrastructure
- UDP-based protocols (DNS, HTTP/3 over QUIC)
- Cryptographic libraries supporting RSA and elliptic curve cryptography
Vulnerabilities (CVEs)
None identified.
Detection Availability
- YARA Rules: No
- Sigma Rules: No
- Snort/Suricata Rules: No
- KQL Queries: No
- Splunk SPL Queries: No
- EQL Queries: No
- Other Detection Logic: No
No detection rules are provided in this article. It is an informational overview of post-quantum cryptography standards and industry readiness.
Detection Engineering Assessment
| Dimension | Rating | Rationale |
|---|---|---|
| EDR Visibility | None | This article discusses cryptographic standards and protocol-level changes; it does not describe endpoint threats or behaviors detectable by EDR. |
| Network Visibility | Low | While TLS handshake changes are network-observable, the article does not describe specific network-based detection logic. Future PQC algorithm identifiers in TLS handshakes could be monitored once standardized. |
| Detection Difficulty | N/A | Not applicable — this is an informational article about cryptographic standards, not a threat analysis with detection requirements. |
Hunting Hypotheses
| Hypothesis | Telemetry | ATT&CK Stage | FP Risk |
|---|---|---|---|
| Consider monitoring TLS handshakes for new post-quantum cipher suite identifiers (e.g., ML-DSA, X25519MLKEM768) to establish a baseline of PQC adoption in your environment and identify unexpected or non-standard algorithm negotiations. | TLS/SSL inspection logs, network flow metadata with cipher suite visibility, proxy logs | Defense Evasion / Command and Control | Low — legitimate PQC adoption will generate these signals; the value is in baselining rather than alerting. |
Control Gaps
- Current TLS inspection and network monitoring tools may not parse or log post-quantum cipher suite identifiers or composite signature algorithms.
- Certificate transparency log monitoring may need updates to handle Merkle Tree Certificate formats once standardized.
Key Behavioral Indicators
- TLS handshake messages significantly larger than baseline (20-40 KB increase) may indicate PQC signature deployment
- New TLS cipher suite identifiers related to ML-DSA, FN-DSA, or X25519MLKEM768 in network traffic
False Positive Assessment
N/A
Recommendations
Immediate Mitigation
- Verify against your organization's incident response runbook and team escalation paths before acting. No immediate mitigation is required; this is an informational article about future cryptographic standards.
Infrastructure Hardening
- Consider inventorying all TLS-terminating systems, load balancers, and CDN configurations to identify where post-quantum algorithm support will be needed.
- Evaluate whether your TLS inspection and DLP tools can handle the larger handshake messages (20-40 KB overhead) that PQC signatures introduce.
- If applicable, begin evaluating hybrid key exchange (X25519MLKEM768) support in your TLS stacks as an interim step toward full PQC adoption.
User Protection
- No direct user protection actions are required at this time; the transition timeline targets 2029.
- Consider engaging with your PKI team or certificate authority to understand their PQC certificate roadmap.
Security Awareness
- Consider briefing security architecture teams on the distinction between quantum threats to asymmetric cryptography (RSA, ECC) versus symmetric encryption (AES-128 remains safe).
- Where applicable, incorporate PQC transition planning into existing cryptographic lifecycle management programs to avoid last-minute migration pressure.
