Back

Amazon, Microsoft Accelerate Post‑Quantum Security Plans; Meta and Apple Remain Silent on Timelines

Amazon Web Services and Microsoft have each outlined concrete measures to make their platforms resistant to the looming threat of quantum computers, while Meta and Apple have left their post‑quantum roadmaps vague. The moves come as industry experts warn that the cryptographic algorithms protecting today’s data could become obsolete once large‑scale quantum machines are operational.

Amazon’s quantum‑safe authentication

Amazon’s security team has rolled out SigV4, an internally developed algorithm designed to keep authentication quantum‑safe. According to Amazon security lead Campagna, the service limits the transmission of secret keys to the moment they are generated and never re‑sends them to customers. “AWS limits the transmission of these secrets to the moment of generation,” he wrote. “Once initially distributed, it is never re‑sent to the customer.”

For customers needing long‑lived roots of trust, Amazon employs its AWS Private Certificate Authority paired with the Key Management Service (KMS). The combination complies with FIPS 204, a NIST certification that validates post‑quantum readiness. Data at rest remains encrypted with AES‑256, a symmetric algorithm that quantum computers cannot break more efficiently than classical machines.

Microsoft’s 2033 timeline and phased rollout

Microsoft has set 2033 as the farthest deadline for full post‑quantum cryptography (PQC) readiness across its services. Azure CTO and deputy CISO Mark Russinovich emphasized that the company has been planning for PQC since 2014 as a founding member of the Open Quantum Safe project. “We have been at the forefront of PQC planning since 2014,” he said in an email.

Russinovich outlined three guiding principles: follow NIST standards rather than proprietary solutions, avoid disrupting global customers, and prioritize a platform‑focused rollout beginning with Windows, Azure and identity layers. He likened the effort to past transitions such as the shift from SHA‑1 to SHA‑2 and the adoption of TLS 1.3, but warned that the quantum risk adds urgency.

Microsoft’s approach mirrors earlier industry migrations, aiming to protect both legacy and new workloads without forcing a sudden switch that could break existing applications.

Meta and Apple, by contrast, have not disclosed specific timelines. Meta’s recent post, which largely recycles a two‑year‑old announcement, introduced a taxonomy of PQC maturity levels—PQ hardened, PQ ready, PQ aware, and PQ unaware—but stopped short of committing to a deadline. Apple declined to comment when asked for its schedule.

The uneven disclosures underscore a competitive landscape where cloud providers and social platforms grapple with the same technical challenge yet adopt differing strategies. While Amazon and Microsoft are betting on immediate, standards‑based implementations, Meta and Apple appear to be taking a more cautious, observation‑driven stance.

Industry watchers note that the push toward quantum‑resistant cryptography is not a simple flip‑the‑switch upgrade. It requires coordinated changes across hardware, software and key‑management practices. As the quantum horizon draws nearer, the pressure to align with NIST’s evolving standards will likely compel the quieter players to reveal more concrete plans.

Used: News Factory APP - news discovery and automation - ChatGPT for Business

Source: Ars Technica2