By
As encryption becomes more ubiquitous, organizations should prepare to react quickly to an increasing number of disruptive events, such as the recent GlobalSign SNAFU. A simple error in root certificate maintenance at GlobalSign last week left organizations everywhere asking, “What happened?” Very quickly, they were also asking “What can I do?” when thousands of sites were identified as insecure and became untrusted.
Even after GlobalSign issued intermediate certificates to rectify the problem, cached certificates could not be updated for up to four days. That’s a long time for a commercial website to be inaccessible to users.
In an article in InfoSecurity Magazine, Venafi Chief Strategy Officer Kevin Bocek talks about the impact of just one disruptive event. “It’s hard to know how many companies have been impacted, but with GlobalSign boasting over 25 million certificates rely on the public trust of the GlobalSign root CA certificate, the impact is undoubtedly huge.”
But the fix is surprisingly huge as well. Before organizations can remediate certificates that have been impacted, they need to identify them, isolate them and, finally, reissue them. Sounds simple, right? But this proves to be more difficult than many organizations anticipate. Most organizations do not have a response plan for an outage of this scale; especially one that originates with a trusted authority
In a world where most large organizations rely on multiple CAs in different regions or departments, they often lack the level of visibility required to make a smooth transition from one CA to another. In Dark Reading, Bocek highlights the questions that may have puzzled many organizations. “Do security operations teams know they use GlobalSign? Do they know where the servers that use GlobalSign certificates are located? Do they know how to add new CA certificates to application trust stores?”
The longer it takes to get the answers to these questions, the more revenue will be lost. Bocek estimates that revenue loss and reputational damage for the businesses affected may run into the millions of dollars.
Because of the potential fiscal impact, it’s important that businesses are adequately prepared to take immediate action when a problem arises. “Businesses must have an automated back-up plan – they cannot be at the mercy of any one CA,” advises Bocek in ComputerWeekly.com. He continues, “These types of issues will continue to happen but, when they do, firms need to be able to take control and immediately and automatically change out affected certificates.”
Was this an isolated event? Bocek responds, “The reality is that failures such as this and breaches involving certificates are becoming more frequent – not surprising, since the world is becoming encrypted. The impact though is completely unacceptable – you can’t have your site being untrusted or taken offline for days on end.”
Lorem ipsum dolor sit amet, consectetur elit.
Thank you for subscription
Scroll to the bottom to accept
VENAFI CLOUD SERVICE
*** IMPORTANT ***
PLEASE READ CAREFULLY BEFORE CONTINUING WITH REGISTRATION AND/OR ACTIVATION OF THE VENAFI CLOUD SERVICE (“SERVICE”).
This is a legal agreement between the end user (“You”) and Venafi, Inc. ("Venafi" or “our”). BY ACCEPTING THIS AGREEMENT, EITHER BY CLICKING A BOX INDICATING YOUR ACCEPTANCE AND/OR ACTIVATING AND USING THE VENAFI CLOUD SERVICE FOR WHICH YOU HAVE REGISTERED, YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU ARE ENTERING INTO THIS AGREEMENT ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY AND ITS AFFILIATES TO THESE TERMS AND CONDITIONS, IN WHICH CASE THE TERMS "YOU" OR "YOUR" SHALL REFER TO SUCH ENTITY AND ITS AFFILIATES. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT AGREE WITH THESE TERMS AND CONDITIONS, YOU MUST NOT ACCEPT THIS AGREEMENT AND MAY NOT USE THE SERVICE.
You shall not access the Service if You are Our competitor or if you are acting as a representative or agent of a competitor, except with Our prior written consent. In addition, You shall not access the Service for purposes of monitoring its availability, performance or functionality, or for any other benchmarking or competitive purposes, and you shall not perform security vulnerability assessments or penetration tests without the express written consent of Venafi.
This Agreement was last updated on April 12, 2017. It is effective between You and Venafi as of the date of Your accepting this Agreement.
The Venafi Cloud Service includes two separate services that are operated by Venafi as software as a service, each of which is separately licensed pursuant to the terms and conditions of this Agreement and each of which is considered a Service under this Agreement: the Venafi Cloud Risk Assessment Service or the Venafi Cloud for DevOps Service. Your right to use either Service is dependent on the Service for which You have registered with Venafi to use.
This License is effective until terminated as set forth herein or the License Term expires and is not otherwise renewed by the parties. Venafi may terminate this Agreement and/or the License at any time with or without written notice to You if You fail to comply with any term or condition of this Agreement or if Venafi ceases to make the Service available to end users. You may terminate this Agreement at any time on written notice to Venafi. Upon any termination or expiration of this Agreement or the License, You agree to cease all use of the Service if the License is not otherwise renewed or reinstated. Upon termination, Venafi may also enforce any rights provided by law. The provisions of this Agreement that protect the proprietary rights of Venafi will continue in force after termination.
This Agreement shall be governed by, and any arbitration hereunder shall apply, the laws of the State of Utah, excluding (a) its conflicts of laws principles; (b) the United Nations Convention on Contracts for the International Sale of Goods; (c) the 1974 Convention on the Limitation Period in the International Sale of Goods; and (d) the Protocol amending the 1974 Convention, done at Vienna April 11, 1980.
In the meantime, please explore more of our solutions
In the meantime, please explore more of our solutions
This site uses cookies to offer you a better experience. If you do not want us to use cookies, please update your browser settings accordingly. Find out more on how we use cookies.