Study guide
10.3 Ransomware Incident and Business Continuity 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
10.3 Ransomware Incident and Business Continuity Lab
Key Takeaways Explain This Topic AI
Ransomware response integrates incident management, legal coordination, evidence preservation, communications, recovery, and continuity.
Business continuity decisions should be driven by critical process priorities, RTO, RPO, safety, and customer impact.
Backups are useful only when they are protected, restorable, tested, and aligned to business recovery needs.
Management should separate containment, eradication, recovery, and post-incident improvement while maintaining executive decision records.
Last updated: May 2026
Incident Scenario: Encryption Spreads Before Payroll Cutoff
A regional healthcare organization discovers ransomware on file servers, several virtual desktops, and one application server that supports appointment scheduling. The attacker claims to have copied patient data and threatens public release. Payroll processing is due in two days. Clinical care is still operating, but some departments have shifted to downtime procedures. Executives ask whether to pay, whether to shut down the network, and when systems will be restored.
The first priority is safety and critical services. In healthcare, patient care and life safety outrank convenience and normal productivity. The incident commander should coordinate with clinical leadership to identify services that must remain available, systems that can be isolated, and manual processes that can continue. Security should not make isolation decisions without understanding patient care impact, but operations should not keep infected systems online without risk review.
Incident response should follow defined phases while allowing emergency judgment. Preparation includes roles, contacts, playbooks, logging, backup design, legal relationships, and communications templates. Detection and analysis confirm scope, affected assets, data exposure indicators, initial access, and active attacker presence. Containment limits spread. Eradication removes malicious access and persistence. Recovery restores trustworthy service. Lessons learned improves controls.
Legal and privacy counsel should be engaged early because the attacker claims data theft. The organization may have breach notification duties, contractual notice requirements, law enforcement considerations, insurance requirements, and preservation obligations. Counsel can help protect privileged communications where appropriate, but legal involvement should not stop technical teams from preserving evidence and restoring critical services.
Evidence preservation matters. Teams should capture logs, affected host images where feasible, ransom notes, indicators of compromise, authentication logs, endpoint alerts, firewall records, and backup status. However, preservation must be balanced with urgent containment and recovery. A CISSP manager should avoid both extremes: destroying evidence casually or delaying critical restoration for perfect forensics when patient care is at risk.
Business continuity and disaster recovery guide recovery priorities. A business impact analysis should have identified critical processes, maximum tolerable downtime, recovery time objectives, recovery point objectives, dependencies, manual workarounds, and communication paths. If the organization has not done that work, the incident team must rapidly build a priority list with executives. Payroll may be important, but patient scheduling, medication systems, and clinical workflows may outrank it.
Decision point Security question Business continuity question Evidence needed
Network isolation Will connectivity allow spread or attacker control? What critical services fail if isolated? Dependency map, current indicators, executive approval
Backup restoration Are backups clean and protected? Does restore meet RTO and RPO? Backup logs, malware scan, restore test result
Data theft claim Is there evidence of exfiltration? Who must be notified and when? Egress logs, file access logs, legal assessment
Payment discussion Would payment create legal or ethical issues? Are viable recovery options available? Counsel input, insurance terms, recovery estimate
Public communication What is known and confirmed? Who needs timely updates? Approved message, stakeholder list, update cadence
Backups must be handled carefully. Restoring from a backup that contains malware, stolen credentials, or vulnerable configurations can restart the incident. The team should verify backup integrity, scan restored systems, rebuild critical servers where needed, rotate credentials, close initial access paths, and monitor for reentry. Immutable or offline backups are valuable because ransomware often targets backup systems first.
The pay-or-not-pay question is an executive risk decision, not a purely technical decision. It may involve legal restrictions, ethics, insurance, law enforcement guidance, ability to recover independently, credibility of the attacker, possible data release, and public trust. The security leader should present options and consequences. The leader should not promise that payment will restore systems or prevent disclosure.
Communications must be controlled and honest. Internal staff need instructions about downtime processes, suspicious emails, password changes, and who may speak externally. Customers, patients, regulators, partners, and media may need updates depending on facts and legal duties. Messages should avoid speculation. An update cadence helps reduce rumor and keeps leadership aligned.
Recovery should prioritize trustworthy service over fastest boot. Systems should be rebuilt from known-good media or restored from validated backups. Privileged credentials should be rotated. Service accounts should be reviewed. Vulnerabilities used in the attack should be fixed. Monitoring should be heightened during restoration. A phased return reduces the chance that one missed persistence mechanism compromises the rebuilt environment.
Ransomware Executive Action Register
Name the incident commander and executive sponsor.
Confirm safety, critical services, and manual downtime procedures.
Preserve key evidence while containing active spread.
Engage legal, privacy, communications, insurance, and law enforcement contacts as appropriate.
Identify recovery priorities using RTO, RPO, dependencies, and business impact.
Validate backups before restoration and monitor restored systems.
Record major decisions, assumptions, owners, and timestamps.
Conduct lessons learned and assign corrective actions.
After recovery, the organization should not treat the event as closed until root causes and control gaps are addressed. Improvements may include MFA expansion, endpoint hardening, segmentation, privileged access management, email security, vulnerability management, immutable backups, tabletop exercises, and access review. The CISSP view is that resilience is a governance outcome: the organization can absorb, respond, recover, and improve without losing sight of its obligations.