Challenges of implementing a Zero Trust model
As we explained in part 1, the perimeter of a corporate network has changed. The old model of securing corporate networks is no longer robust enough to fight off more sophisticated cyber-attacks and protect increasingly complex cloud environments, where a leaked credential is an open door for criminals. The Zero Trust model of ‘never trust, always verify’ is the solution. While it has huge benefits, it is not without challenges.
Complex deployments
While Zero Trust is a single term, it is made up of multiple technologies. If a new company was starting up a greenfield IT environment, Zero Trust could be achieved relatively simply by choosing a technology stack that is designed to work together.
However, most organisations already have multiple technologies in place that are not designed to talk to each other. Zero Trust requires a lot of proactive planning, coordination, and integration across different systems, devices, and networks to overcome this. It involves changing the existing network architecture and security infrastructure, which can be costly and time-consuming. And it needs compatibility and interoperability with legacy systems and applications that may not support Zero Trust protocols or standards.
These companies will first need to get an overview of the tools already in use, identify where there are gaps or duplication of functions, design a structure that meets Zero Trust requirements, and marry all the technologies all together. This will take additional resources and the creation of new policies.
Total network visibility
Having a clear understanding of all devices and users connected to the network as well as data flows is crucial to a successful Zero Trust architecture. This complete visibility enables better anomaly detection and faster response to potential threats.
However, gaining this visibility can be challenging to many enterprises who have fragmented and out-of-date solutions that don’t speak to each other. Tools like Azure Sentinel or Defender for Cloud provide a single pane of glass for full visibility of their organisation’s posture, while doing away with outdated, fragmented tools.
Cultural shifts
Zero Trust goes beyond a shift in technology; it takes a complete change in the mindset and behaviours of users. Employees need to get used to more restrictive access controls, which can prompt scepticism as to why things have changed. This is particularly noticeable with senior executives who question why their previous unrestricted access has been limited.
Organisations need to build education and training for employees into the plan, emphasising best practices, the benefits it brings to the company and how it can improve the way everyone works. When employees - and senior execs - understand why it is being rolled out, it is easier to enforce compliance and accountability.
Continuous management
Zero Trust demands ongoing management and adjustment of security policies. For example, if two teams need to work together for a limited period, a policy needs to be created enabling people from the respective teams to access shared resources or files. However, once the project is over, the policy needs to be updated again. This takes constant monitoring but can be automated to reduce the burden on IT teams.