Study guide

5.1 Network Architecture, OSI/TCP/IP, and Secure Design

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.1 Network Architecture, OSI/TCP/IP, and Secure Design

Key Takeaways Explain This Topic AI

Network architecture is a business risk decision because availability, confidentiality, and operational recovery depend on how traffic is placed, routed, filtered, and monitored.

OSI and TCP/IP models are decision aids for fault isolation and control placement, not just memorization charts.

Secure design uses defense in depth across physical, data link, network, transport, session, application, identity, monitoring, and governance layers.

Resilient architectures reduce single points of failure with redundant paths, controlled routing, capacity headroom, and tested failover procedures.

A CISSP-level answer explains why a network control fits the asset value, threat model, compliance obligation, and business tolerance for interruption.

Last updated: May 2026

Architecture before devices

A secure network is not a shopping list of routers, firewalls, and switches. It is a design that moves business traffic in predictable ways, protects valuable data, keeps critical services available, and gives operations enough visibility to detect failure or attack. CISSP judgment starts with business context: which services generate revenue, which data creates regulatory exposure, which partners need access, and how long the organization can tolerate degraded communications.

The OSI and TCP/IP models help translate that context into control placement. Physical controls protect rooms, racks, circuits, and cabling. Data link controls govern switching, VLAN tagging, media access, and local broadcast behavior. Network controls address IP routing, packet filtering, path selection, and address management. Transport controls handle ports, sessions, reliability, and encryption endpoints. Application controls deal with protocol behavior, input validation, authentication handoffs, and business logic.

A layered model also helps during incidents. If users cannot reach a payment system, the problem could be DNS, route convergence, firewall policy, TLS negotiation, certificate expiration, application load, or identity provider failure. A disciplined team works layer by layer and avoids changing several controls at once. That discipline protects availability because troubleshooting itself can become a business risk.

Layer view Typical controls Risk question

Physical Locks, cages, redundant power, diverse circuits Can a facility or carrier issue disconnect the business?

Data link VLANs, port security, 802.1X, switch hardening Can a local device join or observe traffic it should not see?

Network Routing, ACLs, firewalls, anti-spoofing Can traffic reach only approved destinations by approved paths?

Transport TLS, port policy, session handling Are services exposed only on necessary ports with protected sessions?

Application WAF, API gateway, protocol validation Does the application enforce business rules after the packet is allowed?

Secure topology choices

Common topology patterns include flat networks, tiered networks, hub-and-spoke, mesh, spine-leaf, and hybrid cloud connectivity. Flat networks are simple but dangerous for high-value environments because one compromised endpoint can often scan or reach many systems. Tiered designs separate user, application, data, management, and security services so a failure or compromise has a smaller blast radius. Hub-and-spoke designs centralize inspection, shared services, and egress controls while allowing business units to operate separate environments.

Redundancy must be intentional. Dual links do not create resilience if both links share the same conduit, provider, power source, or routing failure domain. High availability pairs do not protect the business if change procedures update both devices with the same bad policy at the same time. Defense in depth therefore includes technical diversity, operational controls, and rollback plans. A mature design asks how a failure will be detected, who can make the failover decision, and whether the failover path has enough capacity.

Addressing and routing are governance topics as much as engineering topics. Overlapping private address ranges complicate mergers, cloud migrations, partner connections, and incident containment. Poor route summarization can make networks fragile and difficult to audit. Weak egress routing allows systems to reach unsanctioned services and weakens data loss prevention. A security leader should insist on an address management process, documented route ownership, and review of routes that bypass inspection.

Secure design checklist:

Define business services, owners, data classifications, and recovery targets before drawing the network.

Identify trust boundaries such as internet edge, user access, partner access, cloud account, production, and management plane.

Place preventive controls close to the boundary they enforce and detective controls where they can observe meaningful traffic.

Remove unnecessary any-to-any paths and document approved exceptions with expiration dates.

Validate that monitoring, logging, time synchronization, backup access, and emergency administration still work during failover.

The CISSP mindset is not to maximize restriction blindly. A hospital, manufacturer, bank, or software platform may need different latency, uptime, privacy, and inspection tradeoffs. The right architecture is the one that reduces material risk while supporting the mission. Network design succeeds when business leaders understand the remaining risk and operations teams can run the design consistently.

Architecture decision checkpoint

Before approving a topology, ask whether the design supports the most important business processes during both normal operations and failure. A design that depends on a single inspection point, one identity provider path, one DNS service, or one undocumented route can look secure in a diagram while creating unacceptable outage risk. The security leader should require evidence that critical traffic paths are known, least privilege is enforced where it matters most, and operational teams can recover without bypassing controls.