Study guide

5.5 Network Components: NAC, IDS/IPS, Firewalls, and Endpoints

CISSP Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: CISSP Orientation, CAT, and Official Source Control

1.1 Credential Scope, CISSP Mindset, and Search Language 1.2 Exam Outline Effective Date and Eight-Domain Map 1.3 CAT Format, 100-150 Items, and Forward-Only Rules 1.4 Passing Grade, Results, Feedback, and Retake Policy 1.5 Experience, Endorsement, and Associate of ISC2 Path 1.6 Pricing, AMF, CPE, and Maintenance Overview

2 Chapter 2: Security and Risk Management

2.1 Professional Ethics, CIA, and Security Governance 2.2 Policies, Standards, Procedures, Guidelines, and Control Ownership 2.3 Legal, Regulatory, Privacy, and Investigation Context 2.4 Risk Identification, Analysis, Treatment, and Reporting 2.5 Business Continuity, BIA, and Recovery Prioritization 2.6 Personnel Security, Training, Awareness, and Culture 2.7 Threat Modeling, Supply Chain Risk, and Third-Party Governance 2.8 Security and Risk Management Case Lab

3 Chapter 3: Asset Security and Data Lifecycle

3.1 Asset and Data Classification, Ownership, and Roles 3.2 Handling Requirements, Labeling, Privacy, and Cross-Border Data 3.3 Data States and Protection Methods: DLP, DRM, and CASB 3.4 Data Lifecycle, Retention, Remanence, and Destruction 3.5 Secure Provisioning, Inventory, and Asset Management 3.6 Asset Security Case Lab

4 Chapter 4: Security Architecture, Engineering, and Cryptography

4.1 Secure Design Principles and Security Models 4.2 Control Selection, System Security, and Architecture Risk 4.3 Cryptography Foundations: Symmetric, Asymmetric, Hashing, and PKI 4.4 Cryptographic Lifecycle, Key Management, and Attack Patterns 4.5 Cloud, Container, IoT, Edge, and Shared Responsibility Architecture 4.6 Physical Site, Facility, and Environmental Security 4.7 Information System Lifecycle Engineering and Retirement 4.8 Architecture and Engineering Case Lab

5 Chapter 5: Communication, Network Security, and Zero Trust

5.1 Network Architecture, OSI/TCP/IP, and Secure Design 5.2 Secure Protocols, Encryption in Transit, and Channel Protection 5.3 Segmentation, Microsegmentation, SDN, VPC, and Zero Trust 5.4 Wireless, Cellular, Remote Access, and Third-Party Connectivity 5.5 Network Components: NAC, IDS/IPS, Firewalls, and Endpoints 5.6 Monitoring, Observability, Capacity, and Resilient Communications 5.7 Communication and Network Security Case Lab

6 Chapter 6: Identity and Access Management

6.1 Identity Proofing, Authentication, Authorization, and Accountability 6.2 Access Control Models: RBAC, MAC, DAC, ABAC, and Risk-Based Access 6.3 Federation, SSO, MFA, Passwordless, and Session Management 6.4 Provisioning, Deprovisioning, JML, and Access Reviews 6.5 Service Accounts, Non-Human Identities, and Privilege Management 6.6 Physical, Logical, Cloud, and Hybrid Access Boundaries 6.7 IAM Case Lab

7 Chapter 7: Security Assessment, Testing, and Audit Strategy

7.1 Assessment, Test, and Audit Strategy Selection 7.2 Control Testing, Vulnerability Assessment, and Penetration Testing 7.3 Log Review, Code Review, Misuse Cases, and Compliance Checks 7.4 Security Process Data, KPIs, KRIs, and Reporting 7.5 Remediation, Exceptions, Risk Acceptance, and Evidence Quality 7.6 Security Assessment and Testing Case Lab

8 Chapter 8: Security Operations, Incident Response, and Resilience

8.1 Investigations, Evidence, Forensics, and Legal Readiness 8.2 Logging, Monitoring, SOC, and Alert Triage 8.3 Configuration, Change, Patch, and Vulnerability Operations 8.4 Incident Management, Containment, Eradication, and Recovery 8.5 Disaster Recovery, Backup, Availability, and Resilience 8.6 Physical Security Operations and Safety 8.7 Security Operations Case Lab

9 Chapter 9: Software Development Security and DevSecOps

9.1 Secure SDLC Governance and Requirements 9.2 Architecture, Threat Modeling, and Design Review 9.3 Secure Coding, Code Review, and Application Testing 9.4 CI/CD, Source Control, and Environment Separation 9.5 Software Supply Chain, Third-Party Components, and Deployment 9.6 DevSecOps Vulnerability Management and Release Risk 9.7 Software Development Security Case Lab

10 Chapter 10: Integrated CISSP Governance Scenario Labs

10.1 Enterprise Risk Committee Decision Lab 10.2 Cloud Migration Security Architecture Lab 10.3 Ransomware Incident and Business Continuity Lab 10.4 Identity Modernization and Zero Trust Lab 10.5 Third-Party Breach and Contract Governance Lab 10.6 Secure SDLC Transformation Lab 10.7 Full CISSP Manager Simulation

11 Chapter 11: Final Review, Endorsement, CPE, and Test-Day Strategy

11.1 Final 45-Day CISSP Study Plan 11.2 CAT Timing and Forward-Only Decision Workflow 11.3 Mixed-Domain Remediation and Manager Mindset Review 11.4 Test-Day Checklist and Pearson VUE Readiness 11.5 Endorsement, Associate Path, and Work Experience Documentation 11.6 CPE, AMF, and Three-Year Maintenance Plan 11.7 CISSP Final Mixed Review

5.5 Network Components: NAC, IDS/IPS, Firewalls, and Endpoints

Key Takeaways Explain This Topic AI

Network components enforce different control objectives, so security leaders must understand where prevention, detection, inspection, and endpoint enforcement fit.

NAC controls who and what can attach to a network, but it requires reliable identity, device posture, exception handling, and operational ownership.

Firewalls, IDS, IPS, WAF, proxies, and load balancers must be configured around application risk and monitored for rule drift.

Endpoint controls are part of network defense because compromised clients and servers often initiate trusted-looking traffic.

Defense in depth combines network and endpoint telemetry so teams can detect both blocked attacks and allowed-but-abnormal behavior.

Last updated: May 2026

Component roles and control objectives

A firewall filters traffic based on policy. A traditional stateful firewall tracks sessions and allows return traffic for approved flows. A next-generation firewall may add application awareness, user awareness, intrusion prevention, URL filtering, malware inspection, and TLS inspection. A web application firewall focuses on HTTP and API traffic patterns. A proxy intermediates client requests and can enforce egress policy. A load balancer distributes traffic and may terminate TLS. None of these controls is the whole security program.

NAC, or network access control, governs devices before or when they attach to the network. It may use 802.1X, certificates, device posture, MAC authentication bypass for constrained devices, guest registration, and dynamic VLAN assignment. NAC can reduce unauthorized access, but poor implementation can disrupt operations. Printers, cameras, medical devices, industrial systems, and emergency devices often need exception processes. Exceptions should be documented, segmented, and reviewed.

IDS and IPS controls compare traffic or behavior to signatures, heuristics, protocol rules, or anomaly baselines. IDS detects and alerts; IPS can block or modify traffic inline. The business tradeoff is false positive tolerance. A blocking IPS in front of a revenue service can reduce exploit risk but can also create outages if tuned poorly. Detection-only placement may be safer during early deployment but requires response capacity.

  • Component Primary role Key management issue
  • NAC Control network attachment Device identity, posture, and exceptions
  • Stateful firewall Enforce port and address policy Rule recertification and shadowed rules
  • NGFW Add application and user-aware inspection TLS visibility, privacy, and tuning
  • IDS Detect suspicious traffic Alert quality and response ownership
  • IPS Block suspicious traffic inline False positives and availability impact
  • WAF Protect web and API traffic App change coordination and bypass paths
  • Endpoint EDR Detect and contain host behavior Coverage, tamper resistance, and response

Placement, drift, and endpoints

Control placement follows traffic flow and business criticality. Internet-facing applications need edge filtering, DDoS planning, WAF or API protection where appropriate, secure load balancing, and backend segmentation. East-west data center traffic may need internal firewalls, microsegmentation, or host controls. Management traffic should use separate paths, bastion access, privileged access management, and strong logging. Egress traffic should be controlled because compromised systems often call out to command infrastructure or unsanctioned storage.

Rule drift is a common long-term failure. Emergency changes, temporary partner access, broad any rules, and undocumented migrations accumulate until policy no longer matches the risk model. Mature firewall governance includes request justification, owner, source, destination, service, expiration, testing, recertification, and removal. A rule that nobody owns is a business risk because nobody can explain the consequence of keeping or deleting it.

Endpoint controls matter because the network often sees traffic from trusted addresses. EDR, host firewalls, secure configuration, patching, application control, disk encryption, and local privilege management reduce the chance that a permitted flow is abused. If a user workstation is allowed to reach a file share, endpoint compromise can still become data theft. If a server is allowed to reach a database, server compromise can still become data manipulation. Defense in depth assumes permitted paths can be misused.

Firewall and detection governance workflow:

Define the application owner, data classification, allowed users, and required flows.

Place controls at ingress, egress, management, and lateral movement points based on the threat model.

Start with least privilege rules and document temporary exceptions with end dates.

Tune IDS and IPS alerts using business impact and incident response capacity.

Review rules, blocked traffic, allowed anomalies, and endpoint telemetry on a recurring schedule.

Test fail-open and fail-closed behavior so availability decisions are explicit.

A CISSP-level decision does not ask whether a firewall is good or bad in isolation. It asks what risk the component reduces, what risk it introduces, what team owns it, how it is monitored, and how it behaves under failure. The answer should connect technical placement to business outcomes such as fraud prevention, patient care continuity, manufacturing uptime, customer privacy, and regulatory evidence.