Study guide

9.2 Architecture, Threat Modeling, and Design Review

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

9.2 Architecture, Threat Modeling, and Design Review

Key Takeaways Explain This Topic AI

Threat modeling helps teams reason about likely abuse before the architecture becomes expensive to change.

Design review should evaluate trust boundaries, data flows, identity paths, privileged operations, failure modes, and operational dependencies.

Security architecture decisions should be justified by risk and documented so later teams understand why patterns were approved.

A manager-level review focuses on residual risk, compensating controls, and accountable decisions, not only diagram correctness.

Last updated: May 2026

Designing For Misuse And Failure

Architecture review asks whether the system can meet its security objectives before the organization commits to implementation. A design may use modern services and still be unsafe if trust boundaries are unclear, privileged operations are hidden, logs are missing, or sensitive data flows through services that were never approved for that data. Threat modeling gives the review structure.

Threat modeling is not a paperwork exercise reserved for large projects. It is a way to ask what can go wrong, why it matters, what controls reduce the risk, and who accepts what remains. It should be scaled to the system. A small internal workflow may need a short abuse-case review. A payment, medical, identity, or safety-related platform may require a formal model, architectural signoff, and repeated updates as the design changes.

A useful threat model starts with assets and objectives. What data, transactions, identities, processes, and service dependencies matter? Then it maps data flows and trust boundaries. A trust boundary is a point where assumptions change, such as a browser entering an API, a service calling a database, a cloud workload using a managed identity, or a partner system connecting through an integration layer. Boundary crossings are where controls often belong.

Review focus Questions to ask Control examples

Identity Who or what can act, and how is identity proven? MFA, federation controls, workload identity, session controls

Authorization Can users or services exceed intended privileges? Central authorization, deny by default, policy testing

Data flow Where does sensitive data move and persist? Encryption, tokenization, minimization, approved storage

Input and output Can untrusted data change execution or disclosure? Validation, encoding, parameterization, safe serialization

Logging Can important actions be investigated? Tamper-resistant logs, time sync, event standards

Resilience What happens when dependencies fail? Timeouts, circuit breakers, queues, rollback, fail-safe defaults

Operations Can the system be patched and recovered? Observability, configuration management, runbooks

Common threat modeling methods include STRIDE, attack trees, misuse cases, and data-flow-based analysis. CISSP scenarios usually care less about naming a method and more about applying the discipline. STRIDE can help structure thinking about spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege. Misuse cases help product teams see malicious or careless behavior that normal user stories omit.

Design review should be collaborative. Security teams bring threat knowledge and control patterns. Architects know dependencies and constraints. Developers know implementation realities. Product owners know customer and regulatory expectations. Operations teams know monitoring, recovery, and deployment limits. Privacy and legal teams may be needed when data use, notice, jurisdiction, or contractual commitments are affected.

Scenario: a company is moving a claims-processing application to cloud containers. The proposed design places public APIs, internal services, queues, object storage, and analytics jobs in the same network segment. The threat model identifies broad service account permissions, missing egress controls, unencrypted object storage events, and no separation between production and analytics identities. The right management response is not to reject cloud. It is to require segmentation, least-privilege identities, approved encryption, monitoring, and risk acceptance for any remaining exposure.

Architecture principles guide design choices. Defense in depth avoids dependence on one control. Least privilege limits what an identity can do. Fail-safe defaults deny access when policy cannot be evaluated. Economy of mechanism favors simpler designs that can be understood and tested. Complete mediation checks authorization for each protected action. Separation of duties prevents one role from building, approving, and operating sensitive paths without oversight.

Threat modeling should include privacy and data lifecycle risk. A design may protect confidentiality in transit but still collect excessive data, retain it longer than policy permits, or replicate it to analytics platforms without a clear business purpose. A CISSP should ask whether data is minimized, classified, retained appropriately, and deleted or anonymized when no longer needed. Security and privacy are related but not identical.

Design review should also examine negative space: what the system will not do. Will the API reject unsupported methods? Will file uploads be scanned and type checked? Will administrative functions be isolated? Will secrets be stored outside code and images? Will the system fail closed if an authorization service is unavailable? Will logs avoid sensitive values while still supporting investigation? These questions prevent controls from becoming aspirational.

Use this threat modeling workflow:

Define the business process, critical assets, and security objectives.

Draw data flows, trust boundaries, identities, stores, and external dependencies.

Identify threats using a consistent method such as STRIDE, misuse cases, or attack trees.

Rate threats by business impact, likelihood, exploitability, and exposure.

Select controls, design changes, or compensating controls.

Assign owners, due dates, and validation evidence.

Record accepted residual risk and review triggers.

Review triggers are important. A threat model should be revisited when data classification changes, new external connectivity is added, authentication patterns change, privileged workflows are introduced, critical dependencies change, or production incidents reveal a missed assumption. Treat the model as design evidence, not a static artifact.

The CISSP mindset is to prefer early, documented, risk-based design decisions. A late vulnerability can often be patched, but a flawed trust model may require rearchitecture. Leaders reduce cost and risk by making threat modeling part of normal architecture work and by ensuring unresolved design risk is visible to the people authorized to accept it.