Study guide

2.8 Security and Risk Management Case Lab

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.8 Security and Risk Management Case Lab

Key Takeaways Explain This Topic AI

Integrated governance cases require separating facts, assumptions, legal constraints, business objectives, risk owners, and control options.

The best CISSP answer usually preserves mission and safety while reducing risk through accountable, documented, and proportionate action.

Risk treatment decisions should connect controls to residual risk, funding, timelines, evidence, and review triggers.

Scenario practice should build a habit of asking who has authority, what obligation applies, what impact matters, and what control fits.

Last updated: May 2026

Integrated Scenario: Meridian Health Logistics

Meridian Health Logistics ships temperature-sensitive medical supplies to clinics. It runs a customer portal, warehouse management system, route planning platform, identity provider, supplier API gateway, and analytics environment. A new executive wants faster partner onboarding, more detailed customer analytics, and lower operating cost. At the same time, the security team found weak vendor access controls, stale procedures, and untested recovery plans.

The case is not solved by choosing one tool. Meridian handles customer information, shipment data, clinic delivery schedules, supplier access, and operational technology in warehouses. Confidentiality matters because customer and route data is sensitive. Integrity matters because incorrect shipment or temperature data can affect patient care. Availability matters because clinics depend on timely delivery. Safety and trust matter because a cyber failure could create real-world harm.

First, establish governance. The CISO should identify business owners for shipping operations, customer portal, analytics, suppliers, identity, and warehouse technology. Legal and privacy should join decisions involving personal data, contractual notice, monitoring, and cross-border processing. Operations should join continuity decisions. Procurement should join vendor decisions. The executive sponsor should define risk appetite and approve tradeoffs that affect mission, cost, and service levels.

Issue Primary owner Risk question Likely evidence

Partner API onboarding Business owner and API control owner Can partners access only their data? Threat model, access tests, logs

Customer analytics expansion Data owner and privacy officer Is new use lawful, necessary, and transparent? Privacy review, data map, retention plan

Vendor support access Vendor manager and IAM owner Is privileged access least privilege and monitored? Contract terms, access logs, approvals

Warehouse recovery Operations owner and DR owner Can critical shipping recover within BIA objectives? BIA, restore test, exercise report

Stale procedures Control owners Are operators following current approved steps? Version history, training, audit evidence

Next, classify the decisions. The partner API is a threat modeling and access control problem. The analytics plan is a privacy and governance problem. Vendor support access is third-party and privileged access risk. Warehouse recovery is business continuity and disaster recovery. Stale procedures are documentation and control ownership failures. Treating all of them as generic security issues would hide the specific authority and evidence each one needs.

A threat model for the partner API should map partners, identities, tokens, order data, shipment status, administrative functions, audit logs, and trust boundaries. Abuse cases include partner impersonation, unauthorized access to another clinic's shipments, tampering with delivery instructions, repudiating an order change, denial of service during urgent supply periods, and using partner credentials to reach internal functions. Controls may include strong authentication, scoped authorization, tenant isolation tests, rate limiting, logging, and anomaly detection.

The analytics expansion should start with purpose and data minimization. If the business wants better demand forecasting, it may not need names, exact addresses, or detailed patient-related notes. Aggregated shipment counts, region, product category, and timing may be enough. Privacy review should evaluate notice, consent where applicable, retention, access, sharing, and whether analytics data can be deidentified or pseudonymized. Security controls do not excuse unnecessary collection.

Vendor support access needs stronger governance. A logistics software provider currently uses one shared administrator account for emergency troubleshooting. That undermines accountability and termination control. Meridian should require named accounts, MFA, just-in-time approval, least privilege, session recording or command logging for high-risk access, support windows, contractual restrictions, and rapid revocation. If the vendor cannot support this immediately, the exception needs compensating controls and executive acceptance.

The BIA may show that warehouse management and route planning have a four-hour RTO during business days and a one-hour RPO for shipment updates. Customer analytics may tolerate several days. Identity and network services may need even faster restoration because many processes depend on them. The recovery plan should restore prerequisites first, then critical shipping functions, then customer communications, then lower-priority analytics and reporting.

Use this integrated decision workflow:

Define the business objective and harm scenario.

Identify data, systems, people, vendors, and jurisdictions in scope.

Map applicable policies, standards, contracts, and legal or privacy duties.

Identify threats, vulnerabilities, likelihood, impact, and existing controls.

Choose treatment options with cost, schedule, owner, and residual risk.

Confirm who can accept residual risk.

Record evidence, exception dates, metrics, and review triggers.

Exercise or test controls where failure would be material.

A risk register entry for the shared vendor administrator account might state: a third-party support user or compromised vendor credential could misuse shared privileged access to alter shipment records, resulting in misdelivery, service outage, privacy exposure, and loss of accountability. Inherent risk is high because access is privileged and activity is hard to attribute. Existing controls include VPN allowlisting and ticket approval, but residual risk remains high without named accounts and session evidence.

Treatment could include mitigation through named accounts, MFA, PAM, logging, and network segmentation; transfer through contractual indemnity or insurance for some financial impact; avoidance by removing vendor interactive access and using a break-glass internal process; or temporary acceptance while a remediation project completes. Security should recommend treatment, but a senior business owner should accept residual operational risk if the vendor cannot meet the control immediately.

A stale procedure finding should become a control ownership issue. If warehouse supervisors use an old manual shipping workaround during outages, recovery may fail even if backups work. The continuity owner should update procedures, train supervisors, store copies in an accessible location, and exercise the manual process. Evidence should include procedure version, attendance, exercise results, defects, and remediation owners.

Personnel security appears in the case too. Partner onboarding staff need training on data classification, social engineering, and approval workflows. Vendor managers need contract and evidence review training. Warehouse staff need continuity drills. Engineers need threat modeling and secure API review. Executives need crisis decision practice. A single annual awareness module is not enough for these role-specific risks.

The final executive memo should avoid unsupported certainty. It should not claim risk is eliminated, that compliance proves safety, or that a vendor contract transfers all accountability. It should state the top risks, affected objectives, recommended treatments, required funding, residual risk, owners, milestones, and decision deadlines. This is the CISSP posture: factual, accountable, ethical, and tied to business impact.