Study guide
Firewall Filtering and Traffic Policy
CCST Networking Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Orientation, Official Sources, and Exam Strategy
Official Exam Profile and Source Hierarchy Registration, Delivery, Attempts, and Results Using the Six Official Topic Areas Building a Practical Study Plan Exam Strategy Without Unsupported Shortcuts Ethical Preparation and Path Forward
2 Network Standards, Models, and Common Protocols
Network Building Blocks OSI and TCP/IP Models Frames, Packets, Segments, and Data Flow Network Types and Scope Cloud, On-Premises, Protocols, and Ports Bandwidth, Throughput, Latency, and Jitter
3 Chapter 3: IPv4, IPv6 Addressing, and Subnet Formats
3.1 Public, Private, and Local Addressing 3.2 IPv4 Dotted Decimal and Binary Basics 3.3 Subnet Masks, CIDR, and Prefix Lengths 3.4 Subnet Logic, Host Ranges, and Gateways 3.5 IPv6 Address and Prefix Formats 3.6 MAC vs IP in Addressing Troubleshooting
4 Endpoints, Media, Cabling, and Client Connectivity
Endpoint Devices and Network Roles Network Interface Cards and Link Status Copper, Fiber, Coax, and Connector Basics Wired, Wi-Fi, and Cellular Access Methods Interference, Signal Quality, and Physical Reliability Client Connectivity Checks by Operating System
5 Infrastructure Devices, Ports, and Physical Installation
Infrastructure Device Roles Ports, Connectors, and Device Identification Cisco Device LEDs and Status Checks Network Diagrams and Cabling Instructions Power over Ethernet and Powered Devices Racks, Patch Panels, and Installation Basics
6 Switching, Routing, and Network Services
Basic Switching and MAC Learning VLANs and Local Boundaries Routing, Default Gateway, and ARP DNS, DHCP, and NAT Services Transport-Layer Services Small Network Traffic Flow
7 Troubleshooting Methodology, Ticketing, and Documentation
Help Desk Intake and Information Gathering Scope, Impact, and Prioritization Reproduce, Isolate, and Escalate Ticket Quality and Operational Documentation User Communication and Change History Physical, Data Link, and Network Layer Triage
8 Diagnostic Commands, Packet Capture, and Device Data
Command-Line Triage and Ping Path and Client Configuration Commands DNS and Socket Diagnostics Wireshark Capture and Save Device Access and Data Collection Basic Cisco Show Commands
9 Security, Firewalls, Wireless, and Safe Defaults
Firewall Filtering and Traffic Policy Least Privilege, AAA, Passwords, and MFA Wireless Security, WPA2, WPA3, and WPAx Guest Networks, Segmentation, and Shared Devices Common Threats and Safe User Practices Secure Home Router Baseline
10 Integrated Small Network Build and Repair Labs
Lab 1: Build a Basic Office LAN Lab 2: Repair No Internet After an Office Move Lab 3: Wireless Clients Cannot Reach Local Resources Lab 4: DHCP, DNS, and Default Gateway Symptoms Lab 5: Switch, Router, and Service Boundaries Lab 6: Escalation, Documentation, and Handoff
11 CCST to CCNA Career Path and Operational Readiness
Entry-Level Networking Roles and Expectations CCST vs CCNA and the Cisco Roadmap NetAcad 70-Hour Path and Study Plan Lab Habits for Real Operational Readiness Ethical Preparation, Portfolio, and Logbook Exam Scheduling Calendar and Readiness Check
12 Final Review, Exam Day, and Remediation Plan
Final Review Map to Official Objectives 50-Minute Exam Day Timing Unsupported Facts and Ethical Preparation Retake Planning Before the First Attempt Post-Fail Remediation Workflow Post-Pass Next Steps and Validity
Firewall Filtering and Traffic Policy
Key Takeaways Explain This Topic AI
Firewalls compare each packet or session to an ordered rule set and permit, deny, log, or inspect it.
Match criteria include source IP, destination IP, protocol, TCP/UDP port, interface, zone, direction, and connection state.
Stateful firewalls auto-permit return traffic for sessions the inside host initiated; inbound access needs an explicit rule or NAT.
Most policies use first-match top-down evaluation with an implicit deny at the bottom, so rule order is decisive.
Before blaming a firewall, separate reachability, name resolution, service availability, and policy filtering.
Last updated: June 2026
How Firewalls Filter Traffic
The Cisco Certified Support Technician (CCST) Networking exam (exam code 100-150 , 50 minutes, a question count Cisco says varies by exam form, no publicly published passing score, US $125 through Certiport) lists "describe how firewalls filter traffic" as a skill. At technician depth you do not design enterprise security; you explain what a firewall is doing when a user reaches one resource but not another, or when a new device needs only narrow access.
A firewall is a policy-enforcement device that sits between networks, interfaces, or security zones (named trust levels such as inside , outside , DMZ ). Each rule lists match conditions and an action. A rule might read: permit inside hosts to initiate HTTPS to any outside host . Another: deny guest VLAN to the 192.168.10.0/24 office subnet .
What rules match on
- Criterion Example Why it matters
- Source IP / subnet 192.168.20.0/24 (guest) Same service can be allowed from IT VLAN, denied from guest
- Destination IP / FQDN 10.1.1.50 file server Limits which hosts are reachable
- Protocol TCP, UDP, ICMP ICMP-only rules block ping but allow web
- Port TCP 443, UDP 53 A server on 8443 fails if only 443 is allowed
- Direction / interface inbound on WAN Inbound from Internet is the high-risk path
- State new vs. established Drives stateful return-traffic behavior
Ports matter because most apps use well-known transport ports. HTTPS is TCP 443 , plain HTTP is TCP 80 , DNS is UDP 53 (TCP 53 for zone transfers and large answers), and DHCP uses UDP 67 (server) and 68 (client) . If a web server listens on TCP 443 but the policy permits only TCP 80, users report "the site is down" while the cable, route, and server are perfectly healthy.
Stateful vs. stateless
Most modern firewalls are stateful : they record each session in a connection (state) table, so when an inside laptop opens an HTTPS session outbound, the matching return packets are permitted automatically because they belong to an established connection. This is fundamentally different from opening inbound access from the Internet to an internal host, which normally requires a deliberate rule plus, on small networks, NAT port forwarding . A stateless access list, by contrast, inspects each packet in isolation and would need explicit return-direction entries.
Rule order and default deny
Policies usually evaluate top to bottom, first match wins , ending in an implicit deny : if nothing permits the traffic, it is dropped. So a broad deny placed above a narrow allow silently breaks access, and a broad allow placed too high creates risk. Apply least-access thinking: permit only the source, destination, protocol, and port the use case requires.
Worked troubleshooting example
A user on the guest SSID cannot reach the wiki at https://wiki.corp.local but a teammate on the wired LAN can. Steps: (1) confirm the guest client has an IP, mask, gateway, and DNS; (2) test by IP to bypass DNS; (3) confirm the wiki listens on the expected port; (4) compare the two clients — they differ only by source subnet. Conclusion: a boundary rule denies guest-to-internal, working as designed , not a fault.
Common traps
Assuming every failure is the firewall — most are DNS, addressing, or a stopped service.
Forgetting the implicit deny when a rule "should" match but does not.
Ignoring that a firewall log can show the dropped rule name, zone, and reason even when you cannot change policy.
Good escalation notes: source IP, destination IP/FQDN, protocol, port, timestamp, exact error, and whether the issue is new or follows a recent change.
Where firewalls live in a small network
In a home or small office, the firewall is usually built into the same box that does NAT and Wi-Fi. NAT itself provides a side effect of inbound protection: because internal hosts use private RFC 1918 addresses (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) that are not routable on the public Internet, unsolicited inbound connections have nowhere to land unless a port-forward maps them in. This is not a substitute for a real firewall policy, but on the exam you should connect the ideas: a default home setup blocks most inbound traffic largely because of stateful NAT, while outbound traffic flows freely.
Larger sites place a dedicated next-generation firewall (NGFW) at the perimeter that can match on application identity and user identity, not just IP and port — so it can permit "Salesforce" while denying "BitTorrent" even when both ride TCP 443. A CCST technician does not configure these but should recognize the terms when reading a ticket or a vendor screen.
Reading a deny in a log
A single log line typically shows the action (built/teardown/deny), the source and destination IP and port, the protocol, the interface or zone pair, and the matching rule or ACL name. If a user's traffic appears in the log with a deny against a named rule, you have proof the firewall is the cause and a precise rule to hand to the security engineer. If the traffic never appears in the log at all, the packet may be lost earlier — at addressing, routing, or DNS — and the firewall is likely not the problem. Always reason in that order: reachability first, then name resolution, then the listening service, then the policy.