Advanced Foundations of Cyber Security
Zero Trust Architecture
Beyond the Castle Walls
For decades, network security followed the 'castle-and-moat' model. A strong perimeter, like a firewall, protected a trusted internal network. If you were inside the castle walls, you were trusted. But this model breaks down in a world of remote work, cloud services, and mobile devices. The perimeter is no longer clear, and threats can come from inside just as easily as from outside.
This reality led to a new philosophy: Zero Trust. It operates on a simple, powerful principle: never trust, always verify.
Instead of a trusted internal network, Zero Trust assumes that a breach is always possible. Every request for access must be treated as if it comes from an untrusted network. This means we must authenticate and authorise every user and device for every resource they try to access, every single time. There are no more trusted zones.
Zero Trust is a security concept centered on the belief that organizations should not automatically trust anything inside or outside its perimeters and instead must verify anything and everything trying to connect to its systems before granting access.
This concept isn't just an idea; it's a formal architectural model. The U.S. National Institute of Standards and Technology (NIST) published Special Publication 800-207, which provides a detailed blueprint for a Zero Trust Architecture (ZTA).
How It Works
A Zero Trust Architecture has two core components that work together to manage access: the Policy Decision Point (PDP) and the Policy Enforcement Point (PEP).
Policy Decision Point (PDP): This is the brain of the system. It takes a request for access and compares it against the organisation's security policies. It considers multiple signals, such as user identity, device health, location, and the sensitivity of the data, to make a decision.
Policy Enforcement Point (PEP): This is the gatekeeper. It's a system that sits in front of a resource, intercepting access requests. It sends the request details to the PDP for a decision and then enforces that decision, either granting or denying access.
This continuous loop of request, verification, and enforcement happens for every access attempt. Trust is never assumed from a previous interaction. This brings up an important trade-off: security versus productivity. Overly aggressive verification, like constant re-authentication prompts, can frustrate users. A well-designed ZTA finds the balance, using passive signals and risk-based policies to verify trust without constantly interrupting work.
The Five Pillars of Zero Trust
To help organisations implement this model, the US Cybersecurity and Infrastructure Security Agency (CISA) developed the Zero Trust Maturity Model, built upon five key pillars. These pillars are the foundational elements you must secure to achieve a true Zero Trust environment.
| Pillar | Focus |
|---|---|
| Identity | Verifying users are who they say they are, often using multi-factor authentication (MFA). |
| Device | Ensuring every device connecting to resources is healthy, patched, and secure. |
| Network | Isolating systems and encrypting all traffic to prevent attackers from moving freely. |
| Application | Securing access to applications and workloads, whether on-premise or in the cloud. |
| Data | Classifying data by sensitivity and controlling access based on user and device attributes. |
A critical concept within the Network pillar is micro-segmentation. Traditional security used network segmentation, often with VLANs, to create large, trusted zones. For example, the entire finance department might be on one segment.
Micro-segmentation takes this much further. It creates tiny, isolated security zones, sometimes around a single application or workload. If one workload is compromised, the attacker is trapped within that tiny segment and cannot move laterally to attack other systems on the network. This drastically reduces the 'blast radius' of an attack.
The move to a Zero Trust model is a shift from implicit trust to explicit trust. We no longer implicitly trust a user just because they are on the corporate Wi-Fi. We must explicitly verify their identity, their device's security posture, and their authorisation for the specific data they are requesting, right at that moment. Google's implementation, known as BeyondCorp, is a famous real-world example of this principle in action, securing their corporate network by moving access controls from the perimeter to individual users and devices.
What is the fundamental principle of the Zero Trust security model?
How does micro-segmentation enhance security within a Zero Trust network?
This approach represents a fundamental change in how we think about securing our digital environments, adapting to the reality that threats are everywhere, and trust must be earned, not given.