Study guide

IAM, MFA, SSO, Directory Services, and AAA

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

IAM, MFA, SSO, Directory Services, and AAA

Key Takeaways Explain This Topic AI

IAM identifies users, devices, and services, authenticates them, and feeds authorization decisions.

MFA must combine different factor types (know, have, are, do, somewhere); two passwords are not MFA.

SSO centralizes login through an identity provider, which raises the value of protecting that IdP with MFA and break-glass plans.

SAML carries XML assertions for browser-based enterprise SSO; LDAP queries directory users and groups over TCP 389/636.

RADIUS (UDP) handles network access AAA; TACACS+ (TCP 49) handles granular device administration; 802.1X uses supplicant, authenticator, and authentication server.

Last updated: June 2026

Identity and Access Management

Identity and Access Management (IAM) is the combined set of processes and technologies used to establish who or what is requesting access and what that identity may do. Network+ keeps the focus operational: how identities are checked, how network devices make access decisions, and which protocol fits a given scenario.

Authentication, Authorization, and Accounting

The AAA triad is the backbone of Domain 4 access control.

  • AAA function Question answered Example
  • Authentication Who are you? Username/password plus an MFA push
  • Authorization What may you do? Permit VPN access but deny firewall admin
  • Accounting What did you do? Log every config command on a router

AAA applies to people, devices, services, and administrators alike. A Wi-Fi user joining an SSID, a switch port running 802.1X, and an engineer logging into a router can all flow through one AAA server.

MFA Factors

Multi-factor authentication (MFA) requires two or more different factor categories.

  • Factor Meaning Example
  • Something you know Knowledge Password, PIN
  • Something you have Possession Hardware token, phone authenticator, smart card
  • Something you are Biometric Fingerprint, face recognition
  • Somewhere you are Location On the corporate network or in an approved country
  • Something you do Behavior Typing cadence, gesture pattern

Two passwords are not MFA because both are the know factor. A password plus an authenticator approval is MFA because it joins know and have . For high-risk access, phishing-resistant MFA such as FIDO2/WebAuthn security keys or smart cards beats SMS one-time codes, which are vulnerable to SIM swapping and interception.

SSO and Federation

Single sign-on (SSO) lets a user authenticate once to an identity provider (IdP) and then reach many applications without re-entering credentials. Federation extends trust between an IdP and a relying service, often across companies or clouds.

  • Term Network+ meaning Cue
  • SSO One login reused across services User signs in once, launches several apps
  • SAML XML assertions for enterprise browser SSO IdP posts an assertion to a service provider
  • OAuth 2.0 Delegated authorization framework An app gains permission to a resource
  • OpenID Connect Identity layer atop OAuth 2.0 An ID token proves the user authenticated
  • LDAP Directory access protocol (TCP 389; LDAPS 636) App queries directory users and groups

SSO improves usability and centralizes control, but it concentrates risk: if the IdP is compromised or offline, every connected app is affected. Strong MFA on the IdP, conditional access, thorough logging, and a break-glass emergency account are core to the design.

RADIUS, TACACS+, and 802.1X

  • Technology Use Key detail
  • RADIUS VPN, wireless, 802.1X, network-access AAA Bundles authN and authZ; uses UDP (1812/1813)
  • TACACS+ Network device administration AAA Separates authN, authZ, accounting; uses TCP 49; Cisco-originated
  • 802.1X Port-based network access control Three roles: supplicant, authenticator, auth server
  • EAP Authentication framework for 802.1X Methods include EAP-TLS (certs) and PEAP (credentials)

In 802.1X , the supplicant is the client device or software requesting access, the authenticator is the switch port or wireless access point gatekeeping the connection, and the authentication server is usually a RADIUS server validating credentials or certificates. Until the supplicant authenticates, the port passes only EAP traffic and blocks everything else. Memorize those three roles in order, because exam stems often hand you one piece ("the switch acts as the...") and expect you to name the role.

The switch or access point is always the authenticator; it never makes the credential decision itself, it merely relays EAP between the supplicant and the RADIUS server.

Directory services tie this together. Most organizations store users and groups in a directory such as Active Directory and expose it over LDAP . RADIUS, SSO portals, and applications all query that single directory so that disabling one account removes access everywhere. That central directory is also why an offline or compromised directory becomes a single point of failure, reinforcing the need for redundancy and monitoring.

Scenario: Secure Wired Access

A company wants conference-room ports to block unknown devices: managed laptops get normal access, contractor laptops land on a restricted network, and failed attempts are logged. A solid design is 802.1X on access switches, RADIUS as the authentication server, EAP-TLS certificates for managed laptops, dynamic VLAN assignment to steer devices into the correct VLAN based on the RADIUS reply, and accounting logs for audit. A guest or remediation VLAN catches devices that fail authentication without giving them internal reach.

If a device cannot do 802.1X at all - such as a printer or IP camera - MAC Authentication Bypass (MAB) lets the switch authorize it by its hardware address as a fallback, which the exam may contrast with full 802.1X.

Common Traps

SSO does not remove the need for MFA; it raises the stakes for protecting the IdP.

LDAP queries a directory; it does not encrypt a VPN tunnel.

RADIUS fits network access; TACACS+ is preferred for command-level device administration.

802.1X is not a firewall; it only decides whether a device joins the network at the edge.

Accounting logs are worthless without reliable timestamps, identities, and synchronized clocks (NTP).