Cultivating a robust and efficient quantum-safe HTTPS
2026-03-18T13:23:41Z•32f0793d676bcf0e3ae1502f5e43c4b90e5982e0c601d1ac2ecac845a35c7f7a
AIAndroidAndroid 15/16CA/Browser ForumCertificate TransparencyChrome Root StoreDCVGPU securityGeminiGoogle PlayIETF-PLANTSMali GPUMerkle Tree CertificatesPKIagentic-browsingapp-ecosystemattack-surface reductionbiometricsdomain-control-validationkernel driversmalware preventionpost-quantumprompt-injectionscam-protectiontheft-protection
What happened
This Google Security Blog aggregate describes multiple defensive initiatives across Chrome and Android. Chrome is pursuing a quantum-safe HTTPS strategy—working with the IETF PLANTS group on Merkle Tree Certificates (MTCs) and avoiding immediate inclusion of post-quantum X.509 certificates in the Chrome Root Store—to address performance and Certificate Transparency scaling. The Chrome Root Program and CA/Browser Forum are also phasing out legacy domain-control-validation (DCV) methods (full benefit by March 2028). Android improvements include AI-driven scam protections, expanded Google Play/mL
Why it matters
A reviewed impact interpretation has not been published for this record.
Evidence and limitations
- Source ID
- google_security_blog
- Record identifier
- 32f0793d676bcf0e3ae1502f5e43c4b90e5982e0c601d1ac2ecac845a35c7f7a
- Enrichment time
- 2026-03-18T13:23:41Z
- 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.