Certificate Transparency

Certificate Transparency (CT) is an experimental IETF open standard[1] and open source framework for monitoring and auditing digital certificates. Through a system of certificate logs, monitors, and auditors, certificate transparency allows website users and domain owners to identify mistakenly or maliciously issued certificates and to identify certificate authorities (CAs) that have gone rogue.

Background

Flaws in the current system of digital certificate management were made evident in high-profile security and privacy breaches caused by fraudulent certificates. In 2011 Dutch certificate authority DigiNotar filed for bankruptcy after intruders successfully created more than 500 fraudulent digital certificates using its infrastructure. [2] Ben Laurie and Adam Langley conceived certificate transparency and an implementation of the framework was developed as an open source project.

Advantages

One of the problems with digital certificate management is that fraudulent certificates take a long time to be spotted, reported and revoked by the browser vendors. Certificate transparency would help by making it impossible for a certificate to be issued for a domain without the domain owner knowing. Certificate transparency does not require side channel communication to validate certificates as do some competing technologies such as Online Certificate Status Protocol (OCSP) and Convergence. Certificate transparency also operates without the need to trust a third party.

Certificate transparency logs

Certificate transparency depends on verifiable Certificate transparency logs. A log appends new certificates to an ever-growing Merkle hash tree.[1]:Section 3 To be seen as behaving correctly, a log must:

A log may accept certificates that are not yet fully valid and certificates that have expired.

Certificate transparency monitors

Monitors act as clients to the log servers. Monitors check logs to make sure they are behaving correctly. An inconsistency is used to prove that a log has not behaved correctly, and the signatures on the log's data structure (the Merkle tree) prevent the log from denying that misbehavior.

Certificate transparency auditors

Auditors also act as clients to the log servers. Certificate transparency auditors use partial information about a log to verify the log against other partial information they have.[1]:Section 5.4

Certificate Authority Implementation

Google launched its first certificate transparency log in March 2013.[3] In September 2013, DigiCert became the first certificate authority to implement certificate transparency.[4]

Google Chrome began requiring certificate transparency for newly issued Extended Validation Certificates in 2015.[5][6]

References

  1. 1 2 3 Laurie; et al. (June 2013). "RFC 6962 - Certificate Transparency". The Internet Engineering Task Force. Retrieved 2013-11-20.
  2. ↑ Kim Zetter (2011-09-11). "DigiNotar Files for Bankruptcy in Wake of Devastating Hack". Wired. Retrieved 2014-11-14.
  3. ↑ "Known Logs - Certificate Transparency". certificate-transparency.org. Retrieved 2015-12-31.
  4. ↑ "DigiCert Announces Certificate Transparency Support". Dark Reading. Archived from the original on October 10, 2013. Retrieved 2013-11-12.
  5. ↑ Woodfield, Meggie (December 5, 2014). "Certificate Transparency Required for EV Certificates to Show Green Address Bar in Chrome". DigiCert Blog. DigiCert.
  6. ↑ Laurie, Ben (February 4, 2014). "Updated Certificate Transparency + Extended Validation plan". cabfpub (Mailing list). Archived from the original on 2014-03-30.

External links

This article is issued from Wikipedia - version of the Friday, March 11, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.