Full Report
Google Cloud's Key Management Service now features quantum-safe digital signatures to strengthen data integrity and prepare for emerging quantum computing challenges
Analysis Summary
# Best Practices: Adopting Post-Quantum Cryptography (PQC) for Digital Signatures
## Overview
These practices address the immediate and strategic need to migrate critical digital infrastructure to quantum-resistant cryptography to mitigate the long-term risk posed by developing quantum computers, specifically addressing the "Harvest Now, Decrypt Later" (HNDL) threat against long-lived data and trust roots.
## Key Recommendations
### Immediate Actions
1. **Assess Data Lifespan and Risk:** Immediately identify all data, long-lived roots-of-trust, and device firmware that requires protection against decryption for many years. These assets are most vulnerable to HNDL attacks.
2. **Begin PQC Evaluation:** Start evaluating the new NIST-standardized Post-Quantum Cryptography (PQC) algorithms, specifically FIPS 204 (ML-DSA-65 / CRYSTALS-Dilithium) and FIPS 205 (SLH-DSA-SHA2-128S / Sphincs+), for digital signature needs.
3. **Explore Cloud Provider PQC Features:** If utilizing cloud services (like Google Cloud KMS), actively explore and enable any available preview features for quantum-safe digital signatures to protect new digital assets.
### Short-term Improvements (1-3 months)
1. **Implement PQC for New Signatures:** Begin deploying the PQC digital signature algorithms (FIPS 204/205) for signing new, high-value resources, such as firmware updates for critical infrastructure devices.
2. **Integrate with Key Management Services:** Integrate quantum-safe key management capabilities into existing services, focusing on software-based keys within managed KMS offerings where available.
3. **Open-Source Review:** Review and begin integrating open-source software implementations from vendors supporting NIST PQC standards to prepare for broader rollout.
### Long-term Strategy (3+ months)
1. **Develop Hybrid Cryptography Plans:** Formulate a roadmap to support future hybridization schemes (combining current and PQC algorithms) once broader cryptographic community consensus is reached on optimal implementations.
2. **Extend PQC to HSMs (If Applicable):** Plan the migration of key protection from software KMS to Hardware Security Modules (Cloud HSM or on-premise) to support PQC algorithms as these services become available.
3. **Establish Post-Quantum Roadmap:** Formalize a multi-year strategy to completely transition all digital signatures and encryption schemes across the organization to algorithms approved by NIST PQC standards.
## Implementation Guidance
### For Small Organizations
- **Prioritize Cloud Migration:** Leverage managed services (like Cloud KMS) offering PQC features immediately, as this offloads the complex operational burden of managing cryptographic libraries.
- **Focus on Firmware:** If using embedded devices, prioritize updating signing processes for firmware updates using PQC algorithms first.
### For Medium Organizations
- **Phased Rollout:** Implement PQC for systems handling regulatory data or proprietary intellectual property with multi-year retention requirements.
- **Test Open-Source Libraries:** Begin rigorous testing of open-source PQC implementations in non-production environments to assess performance impact before migrating core services.
### For Large Enterprises
- **Hybrid Implementation:** Due to existing long-lived certificates and trust anchors, prioritize developing and rolling out a hybrid signature scheme (e.g., signing with both RSA/ECC and the new PQC standards) during the transition window.
- **Mandate Standards Alignment:** Ensure all internal development teams mandate alignment with current and forthcoming NIST PQC standards (FIPS 204, 205, and 203/ML-KEM).
- **Cloud HSM Strategy:** Develop a specific procurement or configuration plan for PQC support within Hardware Security Modules (HSMs) as part of the overall infrastructure lifecycle management.
## Configuration Examples
Specific technical configurations were not provided in the source article, but the focus is on supporting NIST standards:
- **Algorithm Focus (Signatures):** Utilize **FIPS 204 (ML-DSA-65 / CRYSTALS-Dilithium)** or **FIPS 205 (SLH-DSA-SHA2-128S / Sphincs+)** when configuring digital signing capabilities within key management systems.
## Compliance Alignment
- **NIST PQC Standards:** The preparations and standardization effort directly align with the specifications formalized by the US National Institute of Standards and Technology (NIST) for Post-Quantum Cryptography (formalized in August 2024).
## Common Pitfalls to Avoid
- **Waiting for Standardization:** Delaying implementation until *all* standards and hybrid methods are finalized is dangerous, as attackers are harvesting data *now* ("Harvest Now, Decrypt Later").
- **Ignoring Long-Lived Assets:** Focusing only on short-term data security while ignoring firmware or roots-of-trust that must remain secure for decades.
- **Assuming Cloud Providers Handle Everything Automatically:** While cloud services are adopting PQC, organizations must actively configure and enable these quantum-safe settings for their specific keys and data.
## Resources
- **NIST PQC Standards Documentation:** Refer to the finalized standards documentation from NIST for FIPS 204 and FIPS 205.
- **Google Cloud KMS Documentation:** Review documentation related to enabling quantum-safe digital signatures within Cloud KMS (availability noted as preview).
- **Open-Source Cryptography Repositories:** Track relevant GitHub repositories or partner libraries that provide open-source implementations of the FIPS 204/205 algorithms.