Google Cloud Announces Quantum Safe Digital Signature for Software-Based Keys (Cloud KMS) as a way to prevent encryption systems against threats posed by quantum computers related to encryption I did.
This feature, currently previewed, coexists with post-National Institute of Standards and Technology (NIST), and its final version was officially made in August 2024.
“Our Cloud KMS PQC Roadmap supports post-NIST encryption standards (FIPS 203, FIPS 204, FIPS 205, and future standards) in both software (cloud KMS) and hardware (cloud HSM). Included is “there is a lot of attention.”
“This helps customers perform quantum-safe major imports and key exchanges, encryption and decryption operations, and digital signature creation.”
Tech Giant uses FIPS 203 (aka ML-KEM), FIPS 204 (aka Crystals-Dilithium or ML-DSA), and FIPS 205 (aka Sphincs+ or Slh-DSA) as well as FIPS 205 (aka Sphincs+ or Slh-DSA). It’s possible. Open source software.
Additionally, we will work with Hardware Security Module (HSM) vendors and Google Cloud Foreign Key Manager (EKM) partners to enable quantum security encryption across the platform.
By adopting PQC early on, IDEA is to protect your system against threats called Harvest Now, Decrypt (HNDL). This includes threat actors with threat actors harvesting encrypted sensitive data with the aim of Quantum Computer decrypting them at some point in the future. It is sufficient to break existing key exchange protocols and algorithms.
“Its future may be years away, but those deploying long-term roots or signature firmware for devices managing critical infrastructure should consider mitigation options for this threat vector. There is.”
“The faster we can protect these signatures, the more resilient the foundation of trust in the digital world.”
Cloud KMS quantum safe digital signatures are available in previews of both ML-DSA-65 (FIPS 204) and SLH-DSA-SHA2-128S (FIPS 205). Arrive at a wider consensus.
Source link
