CC ยท Network security architecture
Zero trust
Never trust, always verify, continuous verification, least privilege and policy enforcement points.
Key points
- Never trust, always verify: no user or device is trusted just because it sits inside the corporate network.
- Every request is authenticated and authorized using identity, device health and context, access is limited to the minimum needed (least privilege), and trust is re-evaluated continuously.
- A policy engine decides, and a policy enforcement point allows or blocks the connection to the resource.
Source: https://csrc.nist.gov/pubs/sp/800/207/final
Practice questions
Which phrase sums up the zero trust principle?
- Never trust, always verify
- Trust the internal network
- Verify once, trust forever
- Trust devices that the company owns
Show answer
Answer: A. Never trust, always verify
Zero trust removes implicit trust based on location or ownership and verifies each request. Trusting the inside or verifying once are the legacy perimeter assumptions it replaces.
Which practices fit a zero trust approach?
- Continuously re-evaluating trust during a session
- Granting only the access a task needs
- Checking device posture before allowing access
- Trusting any device inside the firewall
- Using one long-lived shared account for all admins
Show answer
Answer: A. Continuously re-evaluating trust during a session, B. Granting only the access a task needs, C. Checking device posture before allowing access
Continuous verification, least privilege and posture checks are core ideas. Implicit trust inside the firewall and shared long-lived accounts contradict it.
Under zero trust, a device on the corporate network is trusted automatically.
Show answer
Answer: False
Zero trust specifically rejects trust based on network location. Each access request must still be verified.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
