• Google is Sun-Setting SHA-1 in Upcoming Chrome Releases

    On September 5, 2014, Google announced that they will sunset SHA-1 by providing security warnings through the Chrome browser. How will this change affect your organization and the website security it provides your customers? We explain in detail.

        in Alerts, Certificate Management, Digital Certificates, SSL
    0
  • Do You Need SHA-2 Signed Root Certificates?

    We have discussed the SHA-1 deprecation policy and why you should move to SHA-2. The certification authorities (CAs) have provided methods to have your certificates issued and signed using a SHA-2 hashing algorithm. As we move ahead, you will see the CAs changing the default signing algorithm from SHA-1 to SHA-2. It’d be sound strategy to move all of your

        in SSL, SSL Deployment
    0
  • Always-On SSL

    Always-On SSL is an approach to securing your website to mitigate attacks against your users. When I think of Always-On SSL, I think of three concepts: SSL across your entire site, SSL deployed to the best practices, and SSL with leading technology. SSL across Your Entire Site The approach to Always-On SSL is to avoid hijacking of the sessions with

        in EV SSL, SSL, SSL Deployment
    0
  • Why We Need to Move to SHA-2

    Previously, we advised that the SSL industry must move to the SHA-2 hashing algorithm for certificate signatures. We thought it would be helpful to provide the reasoning behind the position. In the context of SSL, the purpose of a hashing algorithm is to reduce a message (e.g., a certificate) to a reasonable size for use with a digital signature algorithm.

        in Public Key Infrastructure, SSL, SSL Deployment
    0
  • Always-On SSL

    Always-On SSL is an approach to securing your website to mitigate attacks against your users. When I think of Always-On SSL, I think of three concepts: SSL across your entire site, SSL deployed to the best practices, and SSL with leading technology. SSL across Your Entire Site The approach to Always-On SSL is to avoid hijacking of the sessions with

        in EV SSL, SSL, SSL Deployment
    0
  • Why We Need to Move to SHA-2

    Previously, we advised that the SSL industry must move to the SHA-2 hashing algorithm for certificate signatures. We thought it would be helpful to provide the reasoning behind the position. In the context of SSL, the purpose of a hashing algorithm is to reduce a message (e.g., a certificate) to a reasonable size for use with a digital signature algorithm.

        in Public Key Infrastructure, SSL, ...
    0
Page 1 of 212