STUDENT LAB GUIDE — Lesson 9
Firewall Architecture and Rule Design
Your step-by-step walkthrough for every hands-on activity today, plus the “why this matters” framing for each one.
What you’re doing today
Three hands-on activities + one Challenge. All inside Cisco Packet Tracer — Cisco’s free network simulator, the same one used by CCNA students worldwide. You’ll work with a pre-built network called the Meridian DMZ topology (4 subnets behind a perimeter router).
| # | Activity | Time | Difficulty | What you earn |
| Quick-win | Open Packet Tracer + load Meridian topology | ~2 min | ★ | First progress point |
| Lab 9.1 | Build a Segmented Network with Firewall Rules | ~25 min | ★★★ | Progress points |
| Lab 9.2 | Rule Order Troubleshooting | ~15 min | ★★ | Progress points |
| Challenge | Close the Open Door | ~25 min | ★★★★ | [Firewall-Architect-Foundations] badge |
If you don’t finish all of these in class, that’s fine — the onyxium platform saves your progress and the lab environment stays available. Finish at home.
Today’s environment: Cisco Packet Tracer
What it is: A free Cisco network simulator. You drag routers, switches, PCs, and servers into a workspace and wire them together; you can then configure each device with the same CLI commands you’d type on real Cisco hardware.
Why this tool: Real firewalls (Cisco ASA, Palo Alto, FortiGate) cost thousands of dollars and live in production networks. Packet Tracer gives you the same rule-writing experience, with full multi-device topologies, in a safe sandbox. The Cisco IOS ACL syntax you learn here transfers directly to most Cisco firewall products and is conceptually identical to all major vendors.
References: – Cisco Packet Tracer download (free; requires NetAcad account): https://www.netacad.com/courses/packet-tracer – Cisco ACL command reference: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/security/m1/sec-m1-cr-book.html – Network Security Essentials (W. Stallings) Ch. 9 — Firewalls – ISC2 CC Self-Study Guide, Domain 4 — Network Security
The Meridian DMZ topology (memorize this — every lab uses it)
[Internet — simulated as a router]
│
▼
╔══════════════════════╗
║ R1 — Perimeter FW ║ ← ACL 100 lives here
╚══════════════════════╝
┌────────────┬─────────────┬─────────────┐
▼ ▼ ▼ ▼
DMZ Internal-Users Internal-Servers Management
10.10.100.0/24 10.10.20.0/24 10.10.40.0/24 10.10.10.0/24
───────────── ───────────── ────────────── ────────────
web-server PC-Alice file-server IT-admin1
(.10:443) PC-Bob (.10) (.5)
mail-server intranet
(.20:25) (.20:443)
Trust levels (from least to most trusted): Internet → DMZ → Internal-Users → Internal-Servers → Management. Rules should reflect this.
Quick-win lab — “Open Packet Tracer + Load Meridian Topology” (~2 min)
Topic coverage
Orientation to today’s environment. No firewall concept yet.
Why you need this as a cyber professional
Every job interview for a network/security role asks “what tools have you used?” Packet Tracer is on every CCNA résumé and is universally recognized as proof that you know how to work with multi-device networks. By the end of today you will have built a segmented enterprise network from scratch — that’s a real, demonstrable skill.
Steps
- Open the onyxium L9 → Quick-win tile. The browser launches Packet Tracer (or asks you to launch the local install).
- From the onyxium tile, click “Load Meridian Topology” — the .pkt file opens in Packet Tracer.
- You should now see four labeled subnets connected to a central router labeled R1 — Perimeter FW.
- Click any router and explore the CLI tab. Type enable and then show running-config to see the device’s current configuration. You should see a partial configuration with some interfaces and IP addresses, but no ACL yet.
- Hit Ctrl+S in Packet Tracer to save your work to the onyxium-tracked file.
What to expect
- Packet Tracer opens to a topology view with 4 subnets, ~10 devices total.
- The CLI on R1 shows R1> and R1# prompts (user mode and privileged mode).
- The Quick-win is graded on file save — not on any configuration. The point is: you can open the tool.
If you get stuck
- Packet Tracer not launching? Switch to the in-browser version from the onyxium tile.
- No CLI tab? You may have clicked a PC. Click the central router labeled R1.
Lab 9.1 — “Build a Segmented Network with Firewall Rules” (~25 min · Core)
Topic coverage
- 5-field firewall rule anatomy (source/destination/port/protocol/action)
- Default-deny + allowlist policy
- Rule order (top-to-bottom, first-match)
- DMZ segmentation pattern
Why you need this as a cyber professional
Writing firewall rules is one of the most universally required SOC-analyst and network-defender skills. You will do this on day 1 of nearly any cyber operations role. Auditors will read your rules — they need to be tight, ordered, and documented. Today you write your first.
References
- Cisco IOS ACL config guide: https://www.cisco.com/c/en/us/support/docs/security/ios-firewall/23602-confaccesslists.html
- NIST SP 800-41r1 Guidelines on Firewalls and Firewall Policy, §4 — Policies and Best Practices
The goal
Write an extended ACL named/numbered 100 on R1’s Internet-facing interface, applied inbound, that implements this policy:
| Source | Destination | Port | Action | Reason |
| Any (Internet) | 10.10.100.10 (web-server) | TCP 443 | Permit | Public web |
| Any (Internet) | 10.10.100.20 (mail-server) | TCP 25 | Permit | Public mail |
| Any (Internet) | 10.10.20.0/24 (Internal-Users) | any | Deny | Block internet → users |
| Any (Internet) | 10.10.40.0/24 (Internal-Servers) | any | Deny | Block internet → servers |
| 10.10.10.0/24 (Management) | any | any | Permit | Admin override |
| any | any | any | Deny + log | Default-deny terminator |
Steps
Step 1 — Open the perimeter router CLI. Click R1 → CLI tab. Type:
enable
configure terminal
Expected: prompt changes to R1(config)#.
Step 2 — Write the ACL, line by line, in correct order.
access-list 100 remark === ACL 100: perimeter, inbound from Internet ===
access-list 100 permit tcp any host 10.10.100.10 eq 443
access-list 100 permit tcp any host 10.10.100.20 eq 25
access-list 100 deny ip any 10.10.20.0 0.0.0.255
access-list 100 deny ip any 10.10.40.0 0.0.0.255
access-list 100 permit ip 10.10.10.0 0.0.0.255 any
access-list 100 deny ip any any log
Expected: no errors. If you typo a wildcard mask, IOS rejects the line.
Step 3 — Apply the ACL to the Internet-facing interface, inbound. Identify the Internet-facing interface (look at R1’s interface list — it’s the one connected to the simulated Internet router, typically GigabitEthernet0/0).
interface GigabitEthernet0/0
ip access-group 100 in
end
write memory
Expected: Building configuration… [OK].
Step 4 — Verify with show access-list 100. You should see your 6 lines listed with hit counters (initially 0).
Step 5 — Test from the simulated Internet PC. – From the Internet-PC (placed outside R1), open the command prompt and try ping 10.10.20.10 → expected Request timed out (blocked). – Try a Web Browser → http://10.10.100.10 → expected page loads (port 80 NOT permitted by your ACL → should FAIL; we only opened 443. This is intentional — confirms your rule is precise). – Try https://10.10.100.10 → expected page loads (443 permitted). – From an Internal-Users PC (10.10.20.5), ping 10.10.100.10 — expected success (the ACL is inbound from Internet only, not blocking internal traffic).
Step 6 — Re-run show access-list 100. Hit counters should be non-zero on the lines your tests exercised. Read your rules carefully and confirm each test exercised the line you expected.
Step 7 — Save. write memory and Ctrl+S the Packet Tracer file. The onyxium grader picks up your saved .pkt.
What to expect at each step
- After Step 2: 6 lines added; IOS does NOT auto-reorder them — they stay in your typed order.
- After Step 3: traffic from the simulated Internet starts hitting the ACL. Your tests in Step 5 should produce the predicted allow/deny behavior.
- The grader checks: (a) all 6 lines present in correct order, (b) ACL applied to correct interface in correct direction, (c) tests pass.
Common stuck points
- Applied to wrong interface. Look at R1’s show ip interface brief — find the interface whose IP is in the Internet subnet, not in 10.10.x.x.
- Applied in wrong direction. in means traffic ENTERING the router via this interface. From the Internet → R1, that’s in on G0/0.
- Forgot the Management override. If you place the Management permit AFTER the default-deny, it never matches.
- Wildcard masks reversed. 0.0.0.255 is correct for a /24. 255.255.255.0 is the subnet mask and is wrong as a wildcard.
Lab 9.2 — “Rule Order Troubleshooting” (~15 min · Core)
Topic coverage
- Rule shadowing (an earlier rule preventing a later rule from ever matching)
- Diagnostic flow: read top-to-bottom, find the first rule that matches the offending traffic
Why you need this as a cyber professional
“My change isn’t taking effect” is the most common firewall ticket in the industry. 80% of the time, it’s a shadowing problem: a broader rule earlier in the list is matching first. Diagnosing this in 5 minutes vs 45 minutes is a real differentiator on the job.
The scenario
The onyxium grader loads a broken version of the topology onto R1’s ACL 110 (a different ACL, scoped to internal segments). Symptom: Internal-Users PCs cannot reach the intranet server at 10.10.40.20:443, but they should be able to. Your job: diagnose why and fix it.
Steps
Step 1 — Read the symptom. Try the failing action first. From PC-Alice (10.10.20.5), open Web Browser → https://10.10.40.20. Confirm it fails.
Step 2 — Read the rules. On R1: show access-list 110. Read each line top to bottom. Write down which line your traffic would match first.
Step 3 — Identify the shadowing rule. You’ll find a rule that looks like deny ip 10.10.20.0 0.0.0.255 10.10.40.0 0.0.0.255 above the intended permit tcp 10.10.20.0 0.0.0.255 10.10.40.0 0.0.0.255 eq 443. The deny matches first → permit never reached.
Step 4 — Fix the order. Cisco ACLs don’t support easy reordering. Best practice: rewrite the ACL with the lines in the right order. Quickest fix in Packet Tracer:
configure terminal
no access-list 110
access-list 110 remark === Internal Users → Servers ===
access-list 110 permit tcp 10.10.20.0 0.0.0.255 10.10.40.0 0.0.0.255 eq 443
access-list 110 deny ip 10.10.20.0 0.0.0.255 10.10.40.0 0.0.0.255
access-list 110 permit ip any any
end
write memory
Now the more-specific permit matches first.
Step 5 — Re-test. From PC-Alice: https://10.10.40.20 — expected page loads.
Step 6 — Verify you didn’t open new attack paths. show access-list 110 and read your rules out loud. Specifically: does anything you added now allow traffic from Internet-Users to Internal-Servers on ports OTHER than 443? No — your only permit is eq 443. Good.
What to expect
- The fix takes 2 minutes once you spot the shadow.
- The diagnostic — reading top-to-bottom and matching by hand — is the muscle this lab builds.
Challenge — “Close the Open Door” (~25 min · Badge: [Firewall-Architect-Foundations])
Your brief
The Meridian perimeter firewall has ONE rule in ACL 100 that exposes an internal service to the public internet — a service that should NEVER be reachable from outside. A scheduled scanner-PC outside the perimeter probes this exposure every minute. Find the rule, fix it (remove or tighten the source), verify the exposure is closed AND that legitimate Management-segment access still works, and submit the ULC{…} flag.
What you know
- The exposure is in access-list 100 on R1.
- The exposed service is on TCP port 3389 (RDP) — Windows Remote Desktop. It should never be open to 0.0.0.0/0.
- Legitimate access from the Management subnet (10.10.10.0/24) must keep working.
- After you fix the rule, run the Packet Tracer Simulation Mode scenario titled Verify-3389-Closed — it sends a probe from the scanner-PC; if the probe is blocked AND the management-PC probe succeeds, validation returns the flag.
How to approach
- show access-list 100 on R1. Read every line. Find the line with eq 3389 or eq rdp.
- Decide: should this exist at all? If management needs RDP into a server, scope the source — don’t allow ANY.
- Fix the rule. Remember: ACLs aren’t easily editable line-by-line; rewrite the ACL if needed.
- Open Packet Tracer’s Simulation Mode, load scenario Verify-3389-Closed, click Run. Watch the packet animation.
- If the scanner’s probe is dropped at R1 AND the management probe reaches the destination, validation passes — flag appears in the console output.
What you won’t get from us
No step-by-step. This is the assessment.
If you’re really stuck (use tiered hints sparingly)
- Concept: “There’s a too-broad permit somewhere. Find it.”
- Tool: “Run show access-list 100 on R1. Read top-to-bottom.”
- Near-spoiler: “Look for permit tcp any any eq 3389 (or eq rdp). Scope source to 10.10.10.0/24 only.”
Submitting the flag
Paste the ULC{…} flag into the onyxium Challenge submission box. Correct = [Firewall-Architect-Foundations] badge + skill on your profile.
“Why all this matters” — the big picture
Today you wrote the rules that decide what traffic can enter and move within a corporate network. In a real SOC, every alert eventually leads back to a question: did our firewall rule allow this, and should it have? You are now equipped to read, write, and audit those rules. In Module 5 (SOC operations), you’ll re-meet firewall logs in a SIEM. In your first defender job, you will be asked to review and approve firewall change requests. The skill starts here.