Cultivating a robust and efficient quantum-safe HTTPS
2026-03-19T19:23:42Z•b094d719ffcc634dc50d1617c7a4e105dec4c758101b0711a9aa039b5658cb4a
AndroidAndroid 16CABForumCTCertificate TransparencyChrome Root StoreDCVGPU security','Mali GPU','kernel driver','attack surface','Arm']Google PlayHTTPSMTCMerkle Tree CertificatesPKIPLANTSSC-080SC-090SC-091TLSapp safetybiometricsdomain validationpost-quantumquantum-safescam protectiontheft protection
What happened
Collection of Google security posts describing multiple defensive initiatives: Chrome is pursuing quantum-safe HTTPS via Merkle Tree Certificates (MTCs) in the IETF PLANTS working group rather than immediately adding PQ X.509 roots, and Certificate Transparency / CT performance concerns are being addressed. The Chrome Root Program and CA/Browser Forum ballots will phase out 11 legacy domain-control validation (DCV) methods (full effect by March 2028). Android protections were expanded — enhanced scam detection at scale, stronger app vetting on Google Play (blocking millions of policy-violating
Why it matters
A reviewed impact interpretation has not been published for this record.
Evidence and limitations
- Source ID
- google_security_blog
- Record identifier
- b094d719ffcc634dc50d1617c7a4e105dec4c758101b0711a9aa039b5658cb4a
- Enrichment time
- 2026-03-19T19:23:42Z
- 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.