Study guide
Zero Trust, SASE, and Trusted or Untrusted Zone Decisions
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
Zero Trust, SASE, and Trusted or Untrusted Zone Decisions
Key Takeaways Explain This Topic AI
Zero trust assumes no network location is automatically trusted and requires continuous verification and least privilege.
SASE combines networking and security services such as SD-WAN, secure web gateway, CASB, firewall as a service, and ZTNA.
Trusted and untrusted zones are design labels that influence policy, not guarantees that devices are safe.
Network+ scenarios often ask which access path, zone boundary, or control best reduces implicit trust.
Zero trust designs use identity, posture, segmentation, logging, and policy enforcement together.
Last updated: June 2026
Zero Trust and SASE in Network Decisions
Zero trust is a security model that avoids automatic trust based on network location. A device on the internal LAN must still be authenticated, authorized, monitored, and limited to the access it needs. It does not mean every packet is blocked — it means access is explicit, contextual, and continuously evaluated. N10-009 added zero trust, SASE, and SSE as named objectives, so expect at least one scenario cue per concept.
Zero Trust Principles
- Principle Network implication
- Verify explicitly Use identity, MFA, certificates, device posture, and context
- Use least privilege Grant only the required applications, ports, or resources
- Assume breach Segment networks, monitor east-west traffic, limit lateral movement
- Continuous evaluation Reassess risk when posture, location, or behavior changes
- Strong logging Record who accessed what, from where, and when
Key zero-trust vocabulary the exam may use: the policy decision point (PDP) evaluates the request, the policy enforcement point (PEP) allows or blocks it, and microsegmentation narrows trust to individual workloads. A traditional flat network might let any corporate-LAN user reach many internal servers. A zero trust design narrows that: the user authenticates through an identity-aware proxy or ZTNA service, and the device passes posture checks before reaching one specific application.
SASE and SSE Components
Secure access service edge (SASE) combines network connectivity and security functions, often delivered from cloud points of presence. Security service edge (SSE) is the security-only subset of SASE (the SWG, CASB, FWaaS, and ZTNA pieces without SD-WAN).
- Component Function
- SD-WAN Steers branch traffic across multiple links by policy and performance
- Secure web gateway (SWG) Controls and inspects web access
- Cloud access security broker (CASB) Applies policy to cloud application use
- Firewall as a service (FWaaS) Delivers firewall policy from cloud service edges
- Zero trust network access (ZTNA) Identity-aware access to private apps without broad network access
- DLP-style inspection Helps detect sensitive data movement where supported
SASE fits scenarios with many branches, remote users, cloud applications, and a goal to avoid backhauling all traffic through one data center. It still requires policy design, identity integration, logging, and resilience planning — it is not a single appliance.
Trusted and Untrusted Zones
Trusted and untrusted are relative labels. The Internet is commonly untrusted; a management network is more trusted than a guest VLAN. Zero trust thinking avoids assuming that internal means safe.
- Zone label Practical treatment
- Untrusted Require strong filtering and authentication before access
- Semi-trusted Permit limited, inspected access to specific services
- Trusted Still enforce least privilege, logging, and change control
- Management Restrict to admins, jump hosts, secure protocols, MFA
- Partner Treat as external or semi-trusted with explicit allowed flows
The best answer in a zone question usually permits the business need with the smallest trust expansion. A partner should not get VPN access to the whole internal LAN when they only need one application; a ZTNA or reverse-proxy path fits better.
Design Examples
- Requirement Better design direction
- Remote contractor needs one private web app ZTNA or identity-aware reverse proxy to that app only
- Branch users need SaaS and security without backhaul SASE with secure web gateway and SD-WAN policy
- Admins manage network devices Management zone, MFA, jump host, SSH, logging
- IoT devices send telemetry to a controller IoT zone with explicit controller, DNS, and NTP access
- Guest users need Wi-Fi Guest zone, Internet-only access, client isolation
- Common Traps
Zero trust is not a single product or a replacement for basic network hygiene.
SASE does not remove the need for clear access policy and identity integration.
A trusted zone still needs least privilege and monitoring.
A VPN that grants broad network access may be weaker than application-specific access.
Treating cloud applications as automatically trusted ignores account, posture, and data-movement risk.
Exam Focus
For N10-009, connect the concept to an operational decision. If a question asks for reduced lateral movement, think segmentation, least privilege, and identity-aware access. If it describes remote users, branches, SaaS, and cloud-delivered inspection, SASE is the cue. If it describes avoiding automatic trust based on network location, zero trust is the answer.
Worked Scenario
A company is closing a regional data center and moving its applications to SaaS and cloud platforms. Branch offices currently backhaul all Internet traffic over MPLS to that data center for inspection, which is slow and is now disappearing. The right direction is a SASE architecture: deploy SD-WAN at each branch to break out Internet and SaaS traffic locally over broadband, and route that traffic through a cloud secure web gateway and CASB for inspection and policy. Remote employees connect to the few remaining private applications through ZTNA rather than a full-tunnel VPN, so a compromised laptop cannot scan the whole internal network.
The wrong answers in this kind of item usually rebuild the old hub-and-spoke model (more MPLS, a bigger data-center firewall) or grant broad VPN trust — both expand implicit trust and reintroduce the backhaul bottleneck. The exam reasoning chain is consistent: distributed users plus SaaS plus a desire to drop backhaul points to SASE, and per-application private access points to ZTNA, while the phrase 'never trust, always verify' or 'internal is not automatically safe' points to zero trust as the umbrella model.