Cultivating a robust and efficient quantum-safe HTTPS
2026-03-19T01:23:39Z•c426c42f050f9f0ab7df747d514cbfad670bc86d4cf1f3cfc6301c82e0b9de5d
AndroidCA/Browser ForumCertificate TransparencyChrome Root StoreDCV deprecationGPU securityGoogle PlayLLM/agent safetyMali GPUMerkle Tree CertificatesPKIPLANTS IETFTLSagentic browsingapp ecosystemattack-surface reductiondomain validationfailed authentication lockidentity checkkernel driver hardeningpost-quantumpost-quantum cryptographyprompt injectionscam protectiontheft protection
What happened
This collection of Google Security Blog posts outlines multiple forward-looking platform and ecosystem security efforts: Chrome is pursuing quantum-safe HTTPS by collaborating in the IETF PLANTS working group on Merkle Tree Certificates (MTCs) rather than immediately adding post‑quantum X.509 roots to the Chrome Root Store, addressing Certificate Transparency and performance concerns for post‑quantum cryptography. Chrome/Root Program and the CA/Browser Forum are phasing out 11 legacy Domain Control Validation (DCV) methods (ballots SC‑080/SC‑090/SC‑091) with a full deprecation target of March
Why it matters
A reviewed impact interpretation has not been published for this record.
Evidence and limitations
- Source ID
- google_security_blog
- Record identifier
- c426c42f050f9f0ab7df747d514cbfad670bc86d4cf1f3cfc6301c82e0b9de5d
- Enrichment time
- 2026-03-19T01:23:39Z
- 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.