By
If you’re an IT or InfoSec executive in an enterprise that relies on secure communications to protect its data and operation, you need to read NIST Special Publication 1800-16, which provides essential guidance for managing TLS (Transport Layer Security) certificates and was recently published for public review.
If you’re wondering, “What is he talking about? We use TLS but what’s the big deal?”, the NIST guidance is for you.
Whatever business you’re in, your organization relies on TLS and TLS certificates to secure nearly ALL your communications and authenticate nearly ALL servers inside and outside your network boundaries. If you don’t have a formal TLS certificate management program in place, your organization is at risk of outages and breaches.
There are three major risks you face if you don’t effectively manage TLS certificates across your enterprise:
Unlike most security technologies that are deployed and managed by central InfoSec teams, TLS is individually implemented and managed on each system where it is used; and each system requires a unique cryptographic credential, called a TLS certificate. This means every department that deploys/manages systems is deploying and managing TLS certificates themselves. Many organizations have a central team responsible for certificates (typically called the PKI team) but these teams are typically understaffed and, more importantly, don’t have the right processes and technology in place to effectively support all of the teams using TLS certificates to ensure that security and operational risks are mitigated.
Even if you’ve already invested in establishing a formal TLS certificate management program and feel like you’re doing pretty well, the NIST guidance can still help you. Because the use of TLS to secure communications is rapidly increasing to encompass all major business applications in organizations, this guidance will help you ensure your TLS certificates management program will effectively scale with the expanded use of TLS to address outages and security threats.
To make sure the guidance is clear and comprehensive, NIST has released it for public review and feedback. Considering the central role TLS plays in your organization’s security, it’s critical that the guidance provide your organization everything needed to effectively manage TLS certificates and contain risk. NIST needs your feedback on whether it meets that objective.
I recommend executives read 1800-16 Volume A. It provides a high-level view of TLS certificate risks and outlines an action plan for addressing them. Volume B provides more detailed background on TLS, TLS certificates, risks, and effective strategies for effectively managing TLS certificates across your enterprise. You should ask your team (security directors, managers, and architects) to read that volume and come back to you with a plan for how your organization will implement an effective TLS certificate management program.
As a result of poor TLS certificate management, many organizations are experiencing outages, finger pointing, and undetected pivoting by attackers because nearly all traffic is encrypted with TLS and InfoSec groups can’t see malicious traffic between systems. This guidance from NIST is designed to help you eliminate these issues. Read it, start implementing, and provide your feedback on anything you feel is missing.
In addition to the new SP 1800-16 guidance, NIST has been busy updating their other key and certificate management guidance and happen to have recently released a second draft of 800-57 Part 2 (Recommendation for Key Management, Part 2: Best Practices for Key Management Organizations) for public review. I’ll provide background on that in a separate post.
Related Posts
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.