Tutorial 1: Segmentation, Firewalls, and Zero Trust

Unit 4 ยท Network security

Objectives

Traditional perimeter security assumes an internal network is trusted. Enterprise environments contain remote workers, cloud services, contractors, and compromised endpoints, so location alone is weak evidence. Zero-trust architecture continuously evaluates identity, device, resource, action, and context.

subject + device + action + resource + context -> policy decision
allow only required flow; log decision; re-evaluate sensitive actions

Segmentation separates systems by sensitivity, function, or tenant. Firewalls enforce traffic policy, but a firewall cannot compensate for weak application authorization. Rules should be narrow, ordered, documented, reviewed, and observable.

Exercises

  1. Segment public web, API, database, and administration networks.
  2. Write three deny-by-default rules and their business justification.
  3. Identify what happens if one segment is compromised.

Self-check

  1. Why is an internal network not automatically trusted?
  2. What does segmentation limit?
  3. Why log policy decisions?

Self-Check Quiz

1. What is the purpose of segmentation?

AnswerTo limit reachable attack paths and reduce the blast radius of compromise.

2. What should default network policy do?

AnswerDeny traffic unless a specific, necessary, and reviewed rule allows it.

Homework

  1. Design a zero-trust access path for an administrator.
  2. Produce a segmented network diagram.
  3. Explain one control that remains necessary after segmentation.
Sample answerRequire authenticated, managed-device administrator access to a narrowly scoped management service, with step-up MFA, time-limited elevation, and audit logs. Application authorization remains necessary because network reachability does not prove permission to view or change a record.