The old way of thinking was: once you're inside the network, you're trusted. Zero trust throws that out. The idea is never trust, always verify, no matter where the request comes from.
Here's how it works.
The old way: a castle and moat
Traditional security put a strong wall around the network and trusted everything inside. The problem? Once an attacker got in, they could move around freely. That movement is called lateral movement.
The zero trust way
Every request gets checked, every time. Who's asking, from what device, from where, and is it allowed? Access is granted for that specific request, with the least privilege needed.
Control plane vs data plane
Security+ splits zero trust into two parts:
- Control plane: makes the decisions. The policy engine decides, and the policy administrator carries out the decision
- Data plane: where the traffic actually flows. The policy enforcement point is the gate that allows or blocks access
Things that support zero trust
- Strong authentication, like MFA
- Microsegmentation, splitting the network into small zones
- Least privilege access
- Checking device health before granting access
Cheat sheet
- Never trust, always verify
- No automatic trust for being inside the network
- Control plane decides, data plane enforces
- Policy enforcement point = the gate
- Supported by MFA, microsegmentation, and least privilege
Common questions
What is zero trust in simple terms?
Never trust, always verify. Every request gets checked, even from inside the network.
What is the policy enforcement point?
The gate in the data plane that allows or blocks access based on the control plane's decision.
Why use zero trust?
To stop attackers from moving freely once they get inside the network.
Studying for Security+?
Security+ Practice Test 701 has 1,100 practice questions with clear explanations, so you know why every answer is right.