Over the last few years the SSL/TLS industry has moved from MD5 to SHA-1 hashing algorithm and has moved from 1024-bit to 2048-bit RSA key lengths. The industry has adopted the CA/Browser Forum Baseline Requirements. We have also created best practices to mitigate vulnerabilities such as BEAST, CRIME, Heartbleed and POODLE.

But what is next? What do we know about? Who needs to do what?

Entrust is providing the SSL Server Compliance Timeline. This timeline will inform you of modifications to the SSL/TLS industry. How is the industry changing? When do we need to move to SHA-2 signing? When do we have to remove unregistered domain names from our certificates?

What about vulnerabilities and attacks? How do we mitigate them? Who has the action?

The SSL Server Compliance Timeline will track industry compliance issues from the CA/Browser Forum and the browser manufacturers. The timeline will track attacks and vulnerabilities. For each item, the timeline will also advise who will take the action and when it has to be addressed.

If you are looking for new SSL/TLS to-do items, check out our SSL Server Compliance Timeline now.

Bruce Morton

Bruce Morton

Bruce Morton has worked in the public key infrastructure and digital certificate industry for more than 15 years and has focused on SSL and other publicly trusted certificates since 2005. He has been an active member of the CA/Browser Forum that released guidelines for extended validation (EV) certificates and Baseline Requirements for SSL certificates. Bruce oversees the governance and compliance of Entrust’s publicly trusted PKI.