Study guide

Risk, Compliance, Audit, Data Locality, PCI, and GDPR

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

Risk, Compliance, Audit, Data Locality, PCI, and GDPR

Key Takeaways Explain This Topic AI

Asset, vulnerability, threat, exploit, and risk are distinct terms the exam tests with precise wording.

Risk = likelihood x impact; CVSS scores (0.0-10.0) help prioritize but the org sets the scoring method.

Audits produce evidence; passing an audit proves a point-in-time state, not the absence of all risk.

Data locality and data sovereignty govern where data is stored, processed, replicated, and legally controlled.

PCI DSS protects cardholder data; GDPR protects EU residents' personal data with up to 4% global-revenue fines.

Last updated: June 2026

Risk and Compliance Language

Objective 4.2 expects you to separate security terms that sound similar but mean different things, then apply them to a scenario. Memorize the precise definitions; the exam loves to swap vulnerability for exploit in a distractor.

Core Terms

  • Term Meaning Example
  • Asset Something of value Customer database, edge router, WAN circuit
  • Vulnerability A weakness that could be used Unpatched VPN appliance
  • Threat A potential cause of harm Attacker, malicious insider, storm, fat-finger config
  • Threat actor The entity behind a threat Nation-state, hacktivist, script kiddie, insider
  • Exploit A method/code that abuses a vulnerability Public proof-of-concept against the VPN flaw
  • Risk Loss from a threat exploiting a vulnerability VPN compromise leading to internal access
  • Likelihood Probability of occurrence Higher when Internet-facing and actively targeted
  • Impact Harm if it occurs Data exposure, outage, unsafe process, fine

Risk = likelihood x impact. A critical, Internet-exposed system with active exploit activity outranks a low-impact internal issue with no realistic path to harm. The CVSS (Common Vulnerability Scoring System) rates severity from 0.0 to 10.0 (Critical = 9.0-10.0), a common input to that prioritization, though each organization still sets its own risk-acceptance method.

CIA Impact Mapping

  • CIA area Network scenario
  • Confidentiality Packet capture reveals clear-text credentials
  • Integrity DNS poisoning silently redirects users to a fake site
  • Availability DDoS traffic blocks customers from reaching a service

Many incidents touch more than one pillar; the question wording points to the primary impact. "Users cannot connect" = availability. "Records were altered" = integrity. "Sensitive data was read" = confidentiality.

Audit and Compliance

An audit checks whether controls, processes, or evidence meet a requirement. Compliance means the organization meets a defined standard, regulation, contract, or policy at a point in time. Security is broader than compliance, yet compliance drives much of the documentation a network team must produce.

  • Evidence type Example artifact
  • Access User access review, group export, VPN approval record
  • Configuration Firewall rule review, secure baseline, change ticket
  • Logging Retention settings, sample events, admin activity logs
  • Vulnerability Scan results, remediation tickets, exception approvals
  • Segmentation Network diagrams, ACL/rule tables, validation test results
  • Data Locality, Sovereignty, PCI DSS, and GDPR

Data locality means data is stored or processed in a specific physical/legal location. Data sovereignty is the principle that data is subject to the laws of the jurisdiction where it resides or where the subject lives. These shape cloud region choices, backups, logging, replication, and remote support.

  • Requirement cue Network implication
  • PCI DSS Segment the cardholder data environment, restrict access, log, encrypt transmission
  • GDPR Protect EU personal data; lawful basis, retention limits, cross-border transfer rules
  • Data locality Pin cloud regions and backup targets to approved geographies
  • Audit request Produce evidence the controls were in force during the review window

GDPR can levy fines up to EUR 20 million or 4% of global annual revenue , whichever is higher, so a backup replicated to an unapproved region is a real compliance event, not a footnote. Do not treat regulation names as magic answers: read what the scenario asks. Card systems on a flat network with guest Wi-Fi point to segmentation ; backups landing in the wrong country point to data locality .

Worked Example: Prioritizing Two Findings

A quarterly scan returns two items. Finding A is a critical-severity flaw (CVSS 9.8) on an Internet-facing load balancer with a public exploit in the wild. Finding B is a medium flaw (CVSS 5.4) on an isolated lab server with no inbound path from the Internet and no exploit available. Risk = likelihood x impact tells you to remediate A first: high impact (perimeter compromise) and high likelihood (exposed plus active exploitation). B may even be a candidate for a documented risk acceptance with a compensating control such as keeping it off the routed network.

The exam frequently presents exactly this two-finding choice and expects the exposed, actively-exploited asset to win.

How PCI DSS Shapes the Network

PCI DSS is the most concrete compliance cue on the exam because its requirements translate directly into network controls. A merchant must isolate the CDE (cardholder data environment) with firewalls and segmentation so that systems handling primary account numbers do not share a broadcast domain with general workstations or guest Wi-Fi. Effective segmentation also reduces audit scope : only the in-scope CDE segment must meet the full control set, which is both a security and a cost argument.

Other PCI-driven network controls include restricting inbound and outbound traffic by least privilege, logging access to cardholder data, and encrypting transmission across open or public networks. When a scenario describes payment terminals reachable from the same VLAN as the lobby kiosk, the intended answer is segmentation plus access control, not a vague "improve security."

Common Traps

A vulnerability is the weakness; the exploit is the method that abuses it.

A threat can exist before it ever succeeds.

Passing an audit does not eliminate risk; it documents a point in time.

Data locality applies to logs and backups, not just production databases.

A higher CVSS number does not automatically mean "fix first" if there is no path to the asset; weigh exposure too.

Sound risk decisions weigh asset value, exposure, likelihood, impact, and compensating controls together.