Cultivating a robust and efficient quantum-safe HTTPS
2026-03-04T20:45:03Z•86af01565169b1cc22893461add2d388b6f4a02ede8a13c17cc52773e9af026d
AI defensesAndroid 16Android securityCABForumCertificate TransparencyChrome Root StoreChrome securityDCV deprecationGPU securityGoogle Play safetyMTCMali GPUMerkle Tree CertificatesPKIPLANTSTLSagentic browsing security','prompt-injection','Gemini','Quick- /app ecosystemattack-surface reductionidentity checkin-call protectionpost-quantum-cryptographyquantum-safescam protectiontheft protection
What happened
A collection of Google Security Blog updates covering multiple defensive initiatives across Chrome and Android. Key items: Chrome is pursuing a quantum-safe HTTPS strategy (favoring Merkle Tree Certificates via the IETF PLANTS working group) instead of immediately adding post‑quantum X.509 roots to the Chrome Root Store, and calls out Certificate Transparency and scalability concerns for post‑quantum signatures. The HTTPS ecosystem will phase out 11 legacy Domain Control Validation (DCV) methods per CAB Forum ballots (deprecation staged through March 2028). Android updates include expanded AI‑
Why it matters
A reviewed impact interpretation has not been published for this record.
Evidence and limitations
- Source ID
- google_security_blog
- Record identifier
- 86af01565169b1cc22893461add2d388b6f4a02ede8a13c17cc52773e9af026d
- Enrichment time
- 2026-03-04T20:45:03Z
- AI-assisted enrichment
- Yes
This record may overlap with other records. Its enrichment can be incomplete or wrong, and machine assistance was used. Validate consequential decisions against the linked source and your own environment.