By
Despite previous warnings from Google, it appears that Symantec has once again been issuing unvalidated Transport Layer Security (TLS) certificates. On Thursday, security researcher Andrew Ayer uncovered 108 credentials that violated strict industry guidelines—all issued by Symantec-owned certificate authorities (CAs). Even when quickly revoked, Ars Technica reports that these improperly issued certificates have the potential to be misused until they are blacklisted by browsers. Unfortunately, the blacklisting process does not happen in real time, and it’s certainly not automatic.
This most recent Symantec incident reminds us to consider again how much we actually trust CAs. Every bad certificate erodes digital trust. And the ramifications of undermining this trust will continue to escalate with our growing reliance on encryption. Venafi VP of security strategy Kevin Bocek gazes into that troubling future, “We’ve seen a number of CAs, including WoSign and GlobalSign making errors over the past year, and we should expect to see this trend continue.”
So, what do we do about it? Sitting around waiting for an independent researcher to uncover poorly issued certificates isn’t the best plan. To ensure your status as a trusted organization, you need to take matters into your own hands. You need to maintain rigid control of your encryption assets. You need to be prepared to define your own terms of trust. And you need to enforce them. No one else can do this for you.
According to Bocek, “The troubling trend of breaches and errors at CAs should serve as a wakeup call for all businesses -- to protect themselves and their customers every organization needs to be able to quickly, detect unauthorized certificates issued by any CA and remove or replace it.”
The faster you can mitigate a CA error, the less security risk. However, without an alternate destination, speed means nothing. Having a trusted relationship with multiple CAs will give you the available track you need to move quickly. Bocek advises, “It’s also crucial for businesses to have a plan that does not leave them at the mercy of any one CA. They need to be agile enough to remove, change or add a CA at a moment’s notice and the only way to accomplish this is with automation.”
As Bocek notes, there is another component of speed. Reaction time. The very process of locating risky certificates, revoking them, requesting replacements, then installing and validating new certificates can be rather lengthy. Try to do this manually on a large scale and you’ll quickly become overwhelmed. Automating the process, on the other hand, will help you ensure speed and accuracy.
CAs give you the raw material for trust. But it’s up to you to manipulate and control that trust in a way that best defends your organization. Or it will break. “Businesses that are unprepared to detect and respond to CA errors threaten the integrity of encrypted and authenticated Internet traffic,” concludes Bocek.
How quickly can you detect and replace risky certificates across your organization?
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.