How a compromised certificate authority birthed the internet's public ledger

How a compromised certificate authority birthed the internet's public ledger
Image: Intellect (generated)

In short: The security of your encrypted web traffic relies on a chain of trust. But what happens when that trust is broken? In 2011, a massive breach exposed a terrifying reality: malicious certificates could be issued in secret. Today, Certificate Transparency ensures no certificate can hide in the shadows.

Certificate Transparency (CT) was born from a crisis of trust. In 2011, the DigiNotar certificate authority was compromised, leading to the issuance of malicious certificates. This vulnerability prompted Google engineers to develop an open-source framework for detecting mis-issued certificates, eventually submitting a draft to the IETF in 2012 under the code-name "Sunlight." The resulting standard, RFC 6962 (published in June 2013), established a system of public, append-only logs. These logs use Merkle trees—data structures where each entry references the hash of the previous one—to create an immutable record of every certificate issued by publicly trusted authorities.

This allows website owners and auditors to detect inappropriately issued certificates that would otherwise remain invisible. The mechanism relies on Signed Certificate Timestamps (SCTs). When a Certificate Authority (CA) issues a certificate, it must receive an SCT from a log operator as a promise to include the certificate within a Maximum Merge Delay. Browsers like Chrome and Apple's system libraries now enforce these requirements. For example, since April 2018, Chrome has required CT for all newly issued certificates. This shift empowers security teams to monitor for suspicious domains—often mimicking legitimate ones for phishing—and issue immediate take-down orders.

While the system is robust, it introduces a trade-off: internal network domain names with public certificates become searchable in these logs. To manage the massive volume of data, techniques like "temporal sharding" (first used by Cloudflare's Nimbus series) divide logs into time periods, such as calendar years, to reduce strain on the infrastructure.

Opens the Intellect+ feed with this card first. Swipe up for the next one.

Sources

To cite this card, link to https://intellectplus.co.uk/app/science-certificate-transparency.

How we source, check and correct cards: Editorial standards.

General information, not professional advice. Spotted an error? Flag the card or see corrections and complaints.

Intellect Plus is a visual educational discovery platform for exploring fascinating facts and ideas. Brain Food, Not Brain Rot. What is Intellect Plus?

Related

Finding something worth knowing…