Study guide

2.7 Threat Modeling, Supply Chain Risk, and Third-Party Governance

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

2.7 Threat Modeling, Supply Chain Risk, and Third-Party Governance

Key Takeaways Explain This Topic AI

Threat modeling identifies what can go wrong, how likely and impactful it is, and which controls should be built or improved before deployment.

Useful threat models are tied to assets, trust boundaries, data flows, abuse cases, and business impact rather than generic fear lists.

Supply chain risk includes software, hardware, cloud services, managed services, subcontractors, open source dependencies, and operational concentration.

Third-party governance requires due diligence, contracts, monitoring, incident terms, exit planning, and risk acceptance by the right business owner.

Last updated: May 2026

Model Threats Before They Become Incidents

Threat modeling is a structured way to ask what can go wrong before a system or process is deployed. It is not only for developers. A privacy workflow, cloud migration, vendor integration, warehouse network, identity redesign, or merger can all benefit from threat modeling. The output should influence design, control selection, testing, monitoring, and risk acceptance.

A practical threat model starts with assets and objectives. What data, service, process, or safety function must be protected? Who uses it? Where are the trust boundaries? What data flows cross networks, accounts, regions, vendors, or privilege levels? What assumptions are being made? The model should be simple enough to use but specific enough to reveal design risk.

Common methods include STRIDE, attack trees, misuse cases, abuse cases, kill chain analysis, and MITRE ATT&CK-informed discussions. STRIDE considers spoofing, tampering, repudiation, information disclosure, denial of service, and elevation of privilege. The method is less important than the discipline: identify credible threats, rank them, choose controls, assign owners, and validate the results.

  • STRIDE category Question to ask Example control direction
  • Spoofing Can an actor impersonate someone or something? Strong authentication, certificate validation
  • Tampering Can data or code be changed without authorization? Integrity checks, signing, change control
  • Repudiation Can actions be denied? Logging, time sync, signed approvals
  • Information disclosure Can data be exposed improperly? Encryption, access control, minimization
  • Denial of service Can service be made unavailable? Rate limiting, redundancy, capacity planning
  • Elevation of privilege Can a lower privilege gain higher privilege? Least privilege, segmentation, hardening

Threat modeling should be scenario-rich. For an API that lets partners submit orders, spoofing may involve stolen partner credentials. Tampering may involve changing quantity or account numbers in transit. Repudiation may involve denying a submitted order. Information disclosure may involve returning another partner's order data. Denial of service may involve flooding the order endpoint. Elevation of privilege may involve using partner access to reach administrative functions.

Supply chain risk extends the model beyond the organization's walls. Software dependencies may contain vulnerabilities or malicious updates. Hardware may arrive with tampered firmware. A managed service provider may hold privileged credentials. A cloud provider region outage may affect availability. A single supplier may create concentration risk. A subcontractor may process regulated data without being visible to the customer.

Third-party governance covers the vendor lifecycle. Before selection, define business need, data involved, criticality, regulatory scope, and risk tier. During due diligence, review security program evidence, certifications or assessment reports, vulnerability management, incident history, privacy practices, subcontractors, financial stability, and business continuity. During contracting, define security requirements, audit rights, notification timing, data return, data deletion, service levels, and liability. After onboarding, monitor performance and risk.

A vendor risk tiering checklist includes:

Does the vendor process confidential, regulated, or personal data?

Does the vendor have production access or privileged access?

Would vendor outage stop critical business processes?

Does the vendor use subprocessors or offshore support?

Is the vendor hard to replace quickly?

Are contractual controls, audit rights, and incident notification terms adequate?

Is there an exit plan, data return plan, and deletion evidence requirement?

Contracts matter because technical controls alone cannot govern an external party. Security addenda, data processing agreements, service level agreements, right-to-audit clauses, breach notification terms, vulnerability disclosure expectations, subcontractor approval, and return or destruction terms create enforceable obligations. Security teams should provide requirements, but procurement and legal usually execute contract language.

Monitoring should continue after signature. Annual questionnaires are not enough for critical suppliers. Depending on risk tier, the organization may review independent audit reports, penetration test summaries, vulnerability remediation, business continuity exercise results, incident notifications, access logs, service performance, subprocessor changes, and financial or geopolitical indicators. Vendor risk changes when services, data, ownership, or threat conditions change.

Scenario: a company wants a payroll SaaS provider. The vendor will process employee personal data, tax identifiers, bank details, and compensation. Risk governance should include privacy review, encryption and access controls, administrator roles, data residency, breach notification, backup and recovery, subcontractors, support access, audit evidence, and exit terms. A low price should not override protection of highly sensitive data.

Scenario: developers want to add an open source package that saves weeks of work. The threat model should consider maintainer reputation, dependency tree, license, known vulnerabilities, update cadence, package integrity, build pipeline controls, and whether the code handles sensitive data. The answer is not automatically reject open source. The answer is to manage dependency risk with policy, tooling, review, and update processes.

Scenario: a managed service provider requires domain administrator access for troubleshooting. That access creates high supply chain and insider risk. A CISSP-oriented design would prefer least privilege, just-in-time access, MFA, session recording, approval workflow, network segmentation, named accounts, contractual limits, monitoring, and rapid revocation. If broad access remains necessary, residual risk needs explicit acceptance.

Threat modeling and vendor governance should feed each other. If a threat model shows that a vendor integration can alter customer balances, vendor due diligence and contract controls must be stronger. If due diligence shows weak incident response, the architecture may need compensating monitoring and tighter data minimization. Risk treatment can be technical, contractual, procedural, or a combination.