In the early days of the internet, the distinction between public and private networks fostered a false sense of security based on the network perimeter. As technology evolved, the notion of a perimeter providing trust became a cornerstone of early security models. Unfortunately, the industry has witnessed the repercussions of this misplaced trust through a continuous cycle of breaches and security incidents.

The concept of Zero Trust has been refined over the years, focusing on the principle that trust should never be granted implicitly and must be continuously validated. This approach was formalized in John Kindervag's influential Forrester article "No More Chewy Centers: The Zero Trust Model of Information Security." Since then, Zero Trust continues to be further defined by organizations such as NIST, CISA, and the Open Group. Despite the clear definitions, embarking on a Zero Trust journey presents its own set of challenges. 

Zero Trust: Fact or fiction?

Let's explore some common misconceptions about Zero Trust that persist today.

Fiction: Zero Trust is literal

If taken literally, Zero Trust would imply that no one has access to anything, which is neither practical nor feasible. 

Fact: Zero Trust does not mean zero access

Zero Trust approaches aim to minimize implicit trust within the environment by implementing explicit trust through continuous verification and adhering to the principle of least privilege. 

Fiction: Zero Trust is a Product

Purchasing a single product will not enable you to achieve Zero Trust. Given the assumption of pervasive risk, relying on just one angle, approach, or product is counterproductive.

Fact: Zero Trust is a strategy

Zero Trust is a comprehensive security strategy that encompasses identity, device, application, and data security. This holistic approach ensures that every component of the infrastructure is protected and that access is granted based on stringent verification processes.

Fiction: Zero Trust is not possible

There is a common misconception that Zero Trust is overly complicated and not worth the effort. It is important to understand that Zero Trust is a journey. It does not require an all-or-nothing approach from day one.

Fact: Zero Trust is achievable 

With careful planning and a well-defined strategy, implementing Zero Trust is achievable through a risk-based evaluation and prioritization process. Start by applying Zero Trust principles to your most critical applications and gradually expand the implementation over time. This phased approach allows you to address the highest risks first and build a more secure environment incrementally.

Implementing Zero Trust in your organization

Implementing a Zero Trust strategy necessitates a cultural shift within the organization. Success hinges on strong executive sponsorship and the establishment of a governance council to oversee the management and execution of the Zero Trust plan. This plan should be developed and endorsed by the executive leadership team.

Executive sponsorship is crucial for driving the Zero Trust initiative forward, ensuring that it receives the necessary resources and attention. The governance council, composed of key stakeholders from various departments, will provide ongoing oversight, address challenges, and ensure alignment with organizational goals.

One of the primary objectives of Zero Trust is to develop a scalable framework centered on the protection of the organization's most critical data, applications, assets, and services (DAAS). The DAAS elements are used to define each protect surface.

To achieve this objective, use a risk-based methodology:

  • Identify the critical resources and define the protect surface
  • Create a risk score to prioritize the resources
  • Evaluate existing security capabilities already in place for the resource
  • Determine Zero Trust resource prioritization based on the risk score

Then apply the Zero Trust design principles to achieve a scalable framework:

  • Focus on the business outcome
  • Design from the inside out
  • Determine who/what needs access
  • Inspect and log all relevant traffic and activity

The design principles should be implemented using a phased approach that will provide a robust framework that can be applied broadly to the security challenges faced today.

The five steps of the phased Zero Trust approach:

  • Define your protect surface
  • Map the transaction flows
  • Build a Zero Trust Architecture
  • Create Zero Trust Policy
  • Monitor and Maintain the Environment

Finally, develop a maturity model to ensure Zero Trust capabilities and controls continue to advance over time. Zero Trust is a journey that demands continuous improvement and focus.

Conclusion

Do not fall for these misconceptions!  With a well-defined strategy, a commitment to organizational change, strong leadership support, and a willingness to invest, Zero Trust is achievable. Adopting a Zero Trust strategy will enhance your organization's security posture, streamline security architectures and processes, reduce administrative burdens, and support compliance with various regulations and standards.

A commitment to a Zero Trust strategy is a fundamental element for the future cybersecurity. As Gene Spafford once famously said "The only system which is truly secure is one which is switched off and unplugged, locked in a titanium lined safe, buried in a concrete bunker, and is surrounded by nerve gas and very highly paid armed guards. Even then, I wouldn't stake my life on it." 

If you are not ready to implement a comprehensive Zero Trust strategy, start with a practical approach focused on embracing a Zero Trust mindset and consistently apply the design principles to your existing cybersecurity efforts.

For more information on how we can assist you in your Zero Trust journey, contact our team.

References:

  1. https://www.forrester.com/report/No-More-Chewy-Centers-The-Zero-Trust-Model-Of-Information-Security/RES56682
  2. https://www.cisa.gov/sites/default/files/publications/NSTAC%20Report%20to%20the%20President%20on%20Zero%20Trust%20and%20Trusted%20Identity%20Management.pdf