Cultivating a robust and efficient quantum-safe HTTPS
2026-03-04T20:43:19Z•3a220db151306a982f1263df6cb54292dca3fa1889dbc40d45353c49b0583b1b
AICA/Browser ForumIETF PLANTSMTCPKISC-080SC-090SC-091agentic browsingandroidapp ecosystemarm partnership','kernel drivers','UMD','KMD','theft protection'certificate transparencychromechrome root storedomain validationgoogle playgpu securitymali gpumalicious appsmerkle tree certificatespost-quantumprompt injectionscam protectionuser alignment critic
What happened
A set of Google security blog posts announcing multiple defensive initiatives and policy changes across Chrome and Android. Chrome is pursuing a quantum-safe HTTPS strategy: it will not immediately add traditional post-quantum X.509 certs to the Chrome Root Store and is collaborating on Merkle Tree Certificates (MTCs) via the IETF PLANTS working group to address performance and Certificate Transparency scaling for post-quantum cryptography. The Chrome Root Program and CA/Browser Forum are phasing out 11 legacy domain validation (DCV) methods (ballots SC-080, SC-090, SC-091) with a phased depre
Why it matters
A reviewed impact interpretation has not been published for this record.
Evidence and limitations
- Source ID
- google_security_blog
- Record identifier
- 3a220db151306a982f1263df6cb54292dca3fa1889dbc40d45353c49b0583b1b
- Enrichment time
- 2026-03-04T20:43:19Z
- 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.