Defining the Zero Trust Protect Surface
Released: 03/05/2024
Enterprise adoption and implementation of Zero Trust is broad and growing. Venture Beat reports that 90% of organizations moving to the cloud are adopting a Zero Trust strategy, while Gartner predicts that 10% of large enterprises will have a mature and measurable Zero Trust security program in place by 2026. How is a mature Zero Trust program achieved? The NSTAC Report to the President on Zero Trust and Trusted Identity Management outlines a five-step process.
This publication by the CSA Zero Trust Working Group provides guidance on iteratively executing the first step of the Zero Trust implementation process, “Defining the Protect Surface.” Defining the protect surface entails identifying, categorizing, and assessing an organization's data, applications, assets, and services (DAAS); business risk; and current security maturity. In this document, readers will find valuable guidance that starts their Zero Trust security journey on the right path.
Key Takeaways:
- The definition of Zero Trust and the Zero Trust protect surface
- How to initiate the Zero Trust implementation process by defining, analyzing, and prioritizing the organization’s protect surfaces
- How to identify the DAAS elements to be protected
- The risks and potential impacts of protect surface compromises
- The difference between the attack surface and the protect surface
Download this Resource
Best For:
- Zero Trust Architects and Implementation Teams
- CISOs and other CxOs
- Information Security Managers and Analysts
- Privacy and Compliance Officers
- IT Auditors and Assessors
- Software Developers
- Network Security Engineers
