Scenario: segment the network
0 of 7Make all seven statements true. The checks rerun every time you change a rule.
Security Playground
Five systems, one firewall and a set of sample rules. Switch rules on and off, change their order, and test connections to see exactly why traffic is allowed or blocked.
Educational simulationRuns entirely in your browser. No traffic leaves your device, and the addresses come from ranges reserved for documentation.
Pick a source, a destination and a service, then send a test connection. Right now the rules allow everything: a flat network.
Make all seven statements true. The checks rerun every time you change a rule.
Read from top to bottom. The first rule that matches decides. If none match, the connection is denied.
How it works
The firewall reads its rules in order and stops at the first one that fits the connection. A broad rule near the top can silently override every careful rule below it.
When no rule matches, the connection is refused. Good segmentation lists what is needed and lets the default block everything else.
This model assumes a stateful firewall tracks allowed connections and permits their replies. You only write rules for who may start a conversation.
Real networks add address ranges, NAT, application-layer inspection, logging, and more than one firewall. Segmentation also does not replace patching, strong authentication or monitoring. The lab models one idea well: which zones may talk, on which service, and why.
Tell us about your zones, services and constraints.