Cultivating a robust and efficient quantum-safe HTTPS
2026-03-20T19:23:41Z•d282c53a7177d1b65e8b0a5fe93a9f193acea991e7223db1aa893cfbd3bb4f19
PLANTSagentic-browsingandroidandroid-16app-securityattack-surface-reductionbiometricsca-browser-forumcertificate-transparencychromechrome-root-storectdcv-deprecationdomain-validationgoogle-playgpu-securitykernel-driversmali-gpumerkle-tree-certificatesmtcpost-quantumpost-quantum-cryptographyprompt-injectionscam-protectiontheft-protection
What happened
A set of Google Chrome and Android security updates and roadmap items: Chrome will not immediately add traditional post‑quantum X.509 certificates to the Root Store and is collaborating on Merkle Tree Certificates (MTCs) via the IETF PLANTS working group to make HTTPS quantum‑safe and CT‑scalable; the CA/Browser Forum and Chrome Root Program are phasing out legacy domain validation methods (phased deprecation through March 2028) to strengthen certificate issuance; Chrome is designing layered defenses (including a user alignment critic) to mitigate indirect prompt‑injection and other risks from
Why it matters
A reviewed impact interpretation has not been published for this record.
Evidence and limitations
- Source ID
- google_security_blog
- Record identifier
- d282c53a7177d1b65e8b0a5fe93a9f193acea991e7223db1aa893cfbd3bb4f19
- Enrichment time
- 2026-03-20T19: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.