The Old Way: Perimeter Security
For decades, network security was built like a medieval castle. You had a strong outer perimeter — firewalls and VPNs — acting as the castle walls and moat. The security model was simple and spatial:
- Outside the walls (the internet): Dangerous, untrusted.
- Inside the walls (the corporate network or VPC): Safe, trusted.
Once someone (a user via VPN) or something (an application server) got past the firewall into the "internal network," they were broadly trusted. They could often talk to any other system on that network without further challenge.
Why the Perimeter Model Fails Today
In the modern cloud era, this model has collapsed under three structural pressures:
-
The perimeter has dissolved. Applications run across multiple clouds, users work from home and coffee shops, and critical data lives in SaaS products like Salesforce or Snowflake. There is no single wall to defend. The "inside" and "outside" distinction no longer maps to reality.
-
Attackers move laterally. If an attacker compromises one weak server that happens to be "inside" the network — perhaps through a phishing email or an unpatched vulnerability — the castle-and-moat model gives them a free pass to roam. They can probe databases, internal APIs, and secrets stores because everything inside trusts everything else inside. This lateral movement is the defining characteristic of major breaches like the 2020 SolarWinds attack.
-
Credentials are the new perimeter. Stolen VPN credentials, leaked API keys, or a compromised service account can grant an attacker the same "inside" status as a legitimate employee. Network location is a terrible proxy for identity.
The New Way: Zero Trust
Zero Trust is a security philosophy built on one maxim: "Never Trust, Always Verify."
It assumes there is no trusted network. Every connection — whether user-to-server or machine-to-machine — must be authenticated (prove who you are), authorized (prove you are allowed to do this specific thing), and encrypted (ensure no one can read or tamper with the data in transit), regardless of where the connection originates. The internal network is treated as just as hostile as the public internet.
Zero Trust is not a single product you buy. It is an architectural philosophy implemented through a combination of tools and policies. The rest of this lesson covers the three core technical pillars that make Zero Trust real: mTLS for machine-to-machine encryption and authentication, SPIFFE/SPIRE for automated workload identity, and Boundary for human access control.