Study guide
Firewalls, IDS, IPS, Security Zones, and Screened Subnets
CompTIA Network+ N10-009
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
Current Exam Facts and Applied Networking Judgment Official Domain Weights and an 8-12 Week Study Plan How to Use Labs, Practice, and PBQ Workflow Missed-Question Notebook and Final Readiness Metrics
2 Domain 1: Networking Concepts (23%)
OSI and TCP/IP Models with Device and Protocol Mapping Networking Appliances and Where They Operate Ports and Protocol Decision Table Traffic Types and Encapsulation Flow
3 Domain 1: Media, Connectors, Transceivers, and Network Architectures
Copper, Fiber, Coax, and DAC Media Connector and Transceiver Selection Network Topologies and Design Patterns Cloud and Virtual Networking Concepts
4 Domain 1: IP Addressing and Subnetting Mastery
IPv4 Classes, Private/Public, APIPA, and Loopback CIDR, VLSM, and Subnet Math IPv6 Address Types and Notation Routing Basics and Longest Prefix Match
5 Domain 2: Network Implementation - Routing
Static vs Dynamic Routing and Route Selection OSPF, EIGRP, and BGP Basics at Network+ Depth NAT/PAT, VIP/FHRP, and Subinterfaces Routing PBQs and Troubleshooting Route Table Clues
6 Domain 2: Network Implementation - Switching
VLANs, Access Ports, Trunks, and Native VLAN STP/RSTP Loop Prevention and Bridge Roles Port Aggregation/LACP, MTU, Jumbo Frames, and Interface Settings Switch Implementation PBQs and Common Misconfigurations
7 Domain 2: Network Implementation - Wireless and Physical Implementation
Wi-Fi Standards, Bands, and Channels SSID Security, Guest Networks, and Authentication Antennas, Coverage, Roaming, Interference, and Site Surveys Physical Installation Implications
8 Domain 2: Network Implementation - Services Implementation
DNS Record Types and Troubleshooting Cues DHCP, DHCPv6, SLAAC, Scopes, Leases, and Relay NTP, PTP, NTS, and Time-Sensitive Networking Service Implementation PBQs: DNS, DHCP, VLANs, and Firewall Direction
9 Domain 3 Part A: Network Operations Documentation and Governance
Physical, Logical, Rack, Cable, Wireless Diagrams, and IPAM Asset Inventory, Baselines, SLAs, SOPs, and Runbooks Change Management and Request Tracking Lifecycle, EOL, EOS, Decommissioning, and Configuration Management
10 Domain 3 Part B: Monitoring, Remote Access, and Resilience
SNMP, Flow, Syslog, Packet Capture, Log Aggregation, APIs, and Port Mirroring Baselines and Performance Metrics Remote Access, Management Paths, and Secure Admin Habits DR and HA Concepts: RPO, RTO, MTTR, MTBF, Sites, Failover, and Testing
11 Domain 4: Logical Security and Secure Access (14%)
Encryption in Transit, Encryption at Rest, PKI, and Certificates IAM, MFA, SSO, Directory Services, and AAA Authorization, Least Privilege, RBAC, Geofencing, and Time-Based Access VPNs and Secure Management Design
12 Domain 4: Segmentation, Risk, and Network Attacks (14%)
Segmentation for Guest, BYOD, IoT, IIoT, SCADA, ICS, and OT Risk, Compliance, Audit, Data Locality, PCI, and GDPR Network Attacks and Scenario Cues Attack-to-Mitigation PBQ Tables
13 Domain 4: Security Controls and Hardening (14%)
Firewalls, IDS, IPS, Security Zones, and Screened Subnets ACLs, Filtering, NAC, Hardening, and Key Management Deception Technologies and Physical Security Zero Trust, SASE, and Trusted or Untrusted Zone Decisions
14 Domain 5: Troubleshooting Methodology and Tools (24%)
Official Troubleshooting Methodology and Evidence Handling Command-Line Tools: ping, traceroute, nslookup, dig, ipconfig, ifconfig, ip, arp, netstat, ss, and route Packet, Protocol, and Wi-Fi Analyzers Choosing the Right Tool by Symptom PBQs
15 Domain 5: Physical, Interface, and Wireless Troubleshooting (24%)
Cable Issues: Type, Attenuation, Crosstalk, Termination, and TX/RX Interface Issues: Errors, Discards, Duplex, Speed, Port Status, and PoE Transceiver, Fiber, and Signal Strength Troubleshooting Wireless Troubleshooting: Interference, Channels, Roaming, RSSI/SNR, Security, and Captive Portals
16 Domain 5: Network Services, Switching, Routing, and Performance Troubleshooting (24%)
DHCP, DNS, NTP, and IP Addressing Issues VLAN, STP, Trunk, Native VLAN, and ACL Issues Routing, Default Gateway, Route Table, and NAT Issues Congestion, Latency, Jitter, Packet Loss, and Application Performance Clues
17 Performance-Based Question Labs
Subnetting and VLSM Design Lab VLAN, Trunk, Router-on-a-Stick, and Firewall Rule Lab Wireless Deployment and Troubleshooting Lab Monitoring, Log Triage, and Route or Service Troubleshooting Lab
18 High-Yield Reference and Final Study Plan
High-Yield Ports and Protocols Table Wi-Fi, Cabling, Connectors, and Transceivers Quick Table Acronyms and Command-Line Tool Quick Table Final 7-Day Review Plan and Readiness Checklist
19 Final Synthesis: Strategy, Remediation, and Readiness
Mixed-Set Decision Strategy for Qualifiers and Close Answers Missed-Question Remediation Notebook by Error Type Exam-Day Time Management and PBQ Order 100-Question Readiness Simulation Blueprint Mapped to N10-009 Weights
Firewalls, IDS, IPS, Security Zones, and Screened Subnets
Key Takeaways Explain This Topic AI
Stateful firewalls track connection state, while stateless filters evaluate packets against rules without session awareness.
NGFW platforms add application awareness, identity-aware policy, content inspection, and threat intelligence features.
IDS detects and alerts; IPS can block, reset, or drop traffic inline.
Proxy servers and load balancers improve control, visibility, availability, and traffic steering when placed correctly.
Security zones and screened subnets separate public, internal, management, and partner traffic by trust level.
Last updated: June 2026
Security Devices and Zone Design
Domain 4, Network Security , is 14% of the N10-009 exam (down from 19% on N10-008). With a maximum of 90 questions in 90 minutes and a passing score of 720 on a 100–900 scale, expect roughly 12–13 scored security items. Network+ rewards placement reasoning: a firewall rule, IDS sensor, IPS device, proxy, or load balancer is useful only when it sees the right traffic and enforces the right policy. The exam describes a business need, a traffic path, or a symptom, then asks which device or design best fits.
Firewall Types
A firewall filters traffic between zones. The exam contrasts how each type makes its decision.
Firewall type How it decides Common use Limitation
Stateless firewall Evaluates each packet against rules (source, destination, port, protocol) Router ACLs, high-speed edge filtering No awareness of established sessions
Stateful firewall Tracks sessions in a state table Perimeter, internal segmentation, data center zones Needs state capacity and symmetric-routing design
Next-generation firewall (NGFW) Adds application awareness, user identity, URL filtering, malware inspection, threat intel User Internet edge, data center, cloud perimeter More complex policy, higher resource cost
Host-based firewall Runs on an endpoint or server Protects a host even off-network Must be managed consistently
A stateless ACL can drop obviously unwanted inbound traffic before it reaches a stateful firewall , but it cannot automatically permit return traffic for an established session — you must add explicit rules. Stateful firewalls are preferred between zones because they allow return traffic for sessions they already permitted without opening broad inbound access.
Proxy, IDS, IPS, and Load Balancer Roles
- Control Traffic position Primary function
- Forward proxy Between clients and external services Controls and logs outbound user access
- Reverse proxy In front of internal web applications Publishes apps, hides internal server details
- Intrusion detection system (IDS) Out of band, passive tap/SPAN Detects suspicious traffic and alerts
- Intrusion prevention system (IPS) Inline Detects and blocks, resets, or drops traffic
- Load balancer In front of a service pool Distributes client traffic, supports availability
An IDS is safer to deploy because it sits out of band, but it cannot directly block traffic — an alert is not prevention. An IPS is inline and can block, but poor tuning interrupts legitimate service. A load balancer is not a firewall; however, it can terminate TLS, run health checks, support session persistence, and steer traffic only to healthy nodes.
Security Zones
A security zone groups systems by trust level and policy. A typical design uses an untrusted Internet zone, a screened subnet, an internal user zone, a server zone, a management zone, and sometimes partner or guest zones.
- Zone Typical contents Policy idea
- Untrusted Internet or external networks Never trusted by default
Screened subnet Public web, VPN, reverse proxy, mail relay, DNS Limited inbound from Internet, limited outbound to internal
- Internal user Managed laptops and desktops Permit business services, restrict server admin
- Server App, database, directory, file services Permit required flows, deny unneeded user access
Management Admin workstations, jump hosts, monitoring, backup Highly restricted access to management interfaces
Guest Visitor devices Internet only, no internal access
A screened subnet (historically a DMZ) prevents public-facing systems from sitting directly on the internal LAN. If a public web server is compromised, the attacker should still face firewall policy before reaching database, directory, management, or user systems.
Placement Examples
- Requirement Good placement
- Block malicious inbound before it reaches web servers IPS or NGFW inline before screened-subnet services
- Alert on east-west traffic without risking outage IDS sensor on a tap or SPAN port near server traffic
- Control employee web browsing Forward proxy or NGFW egress policy at the edge
- Publish an internal web app to the Internet Reverse proxy or load balancer in the screened subnet
- Restrict administration of routers and switches Management zone with firewall rules, named admin access
- Common Traps
A firewall rule that allows any-to-any is not segmentation.
A stateless ACL may block return traffic unless explicit rules are added.
An IDS alert is detection, not prevention.
An IPS must be tuned to avoid blocking legitimate business traffic.
A screened subnet should have limited paths into internal systems, not unrestricted access.
A load balancer improves distribution and availability, but it does not replace zone policy.
Worked Scenario
A help-desk ticket reports that external users cannot reach a newly published web app, while internal users can. The web server sits in the screened subnet. The NGFW permits inbound TCP 443 from the Internet to the reverse proxy, and the reverse proxy forwards to the web server on TCP 8443. The web server, in turn, needs to reach a database in the server zone on TCP 1433. Tracing the path: the inbound rule works (internal users reach it through internal routing), so the failure is the screened-subnet-to-server-zone flow — the firewall is dropping TCP 1433.
Adding a tightly scoped permit from the web server's IP to the database IP on TCP 1433 (and nothing else) fixes the app while preserving zone isolation. This is the recurring Network+ pattern: identify which zone boundary the symptom crosses, then write the narrowest rule that satisfies the business need. Resist the tempting wrong answer of permitting the entire screened subnet to the entire server zone — that collapses the segmentation the screened subnet exists to provide.