See if this sounds familiar…
There’s a Sev1 outage. Bridge lines are open. Cell phones are ringing off the hook. The CIO is demanding answers for why the bank’s online banking system is down. Somebody finally comes on the bridge and announces it’s an expired certificate. Everyone groans.
The PKI team is brought onto the call and dressed down by management for letting another certificate expire. There’s no opportunity for them to ask any questions. Their first priority is to make sure a new certificate is issued as quickly as possible for the downed application.
After the application is back up and running, the PKI team takes some time to look at their records and find that they had, in fact, sent multiple emails to the team responsible for the application. Nobody had responded or taken action. They try to communicate that up the chain of command but by that time nobody cares.
The resulting perception left in everybody’s mind is that the PKI team fell short again—even if nothing could be further from the truth.
Sadly, in most organizations, this isn’t an isolated incident. It’s been going on for years.
In addition to the ongoing expensive and sometimes disastrous outages illustrated above, however, this dysfunctional situation creates significant security risks. While PKI teams are responsible for the official CAs that issue certificates within organizations, they don’t hold and manage the certificates and associated private keys; systems administrators do. With the lack of perceived sense of responsibility and knowledge these system administrators have for certificates (illustrated in the story above), you can imagine how well they typically secure the private keys used with certificates.
Coming back to the context of an enterprise, where there are typically thousands of certificates and tens or hundreds of administrators, you start to get an appreciation for the security and operational risks organizations face.
That’s why I’ve started this blog series. This is where I’ll share knowledge gained through working with lots of large enterprises in improving the management and security of certificates and private keys. (In my day job, I focus on developing technologies to help with securing and managing certificates and private keys). But in this blog, I will primarily focus on how keys and certificates impact people and processes, and vice versa.
I’ll actually spend a good amount of time digging into the risks because I’ve found that if organizations don’t understand the risks, they don’t see a reason to actually work on improving their management of certificates and keys.
We’ll talk a lot about best practices. One of the most important best practices we will start with is proper governance, which is a fundamental element in successful management of certificates and private keys. We’ll talk about policies (ugh) and roles/responsibilities (eek!). And we’ll dig into the more hands on best practices like inventory, validation, enrollment, dual control, and more.
Because everyone learns differently, this written blog will be accompanied by some video blogs. I can’t guarantee that every written blog will have a corresponding video, or vice versa, but we’ll do our best to provide as much content as possible via both mediums.
Stay tuned.
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.