Segmentation guide

WHAT YOU’LL BE ABLE TO DO

Describe who needs to reach what, instead of assuming that separation solves every access problem.

Start with the relationship

List the communicating groups and the service they need. Give each proposed connection a reason that someone else can review.

Staff devices need the application. Guest devices need internet access.

Separate the responsibilities

VLANs define local forwarding boundaries. Routing connects IP networks. Access policy decides which connections are permitted. These are related decisions with different jobs.

Separate groups → provide a route where needed → apply the intended policy

Check both outcomes

Test a connection that should work and one that should be blocked. Success alone does not demonstrate that the intended boundary is enforced.

Can staff reach the service? Can a guest reach something they should not?

PUT THE IDEA TO WORK

Check your reasoning.

Two groups are in different VLANs. What should you avoid assuming?

Before you move on

Use these prompts to decide what to revisit.

I can state the purpose of each segment.I can distinguish routing from permission.My checks include allowed and blocked connections.

0 of 3 reflection prompts checked

FROM EXPLANATION TO EXPLORATION

Now change something.

Change a device’s VLAN, compare the result, and explain which boundary changed.

Explore the VLAN lab

Segmentation has a purpose.

Start with the relationship

Separate the responsibilities

Check both outcomes

Check your reasoning.

Before you move on

Now change something.

Take the next step.

Read the rules in order.

A subnet, one step at a time.