Study guide

8.7 Security Operations 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

8.7 Security Operations Case Lab

Key Takeaways Explain This Topic AI

Security operations decisions become stronger when evidence, business impact, control ownership, and recovery objectives are considered together.

A single incident often touches logging, IAM, vulnerability management, legal readiness, communications, backup, and physical or supplier controls.

The best manager-level answer usually defines authority, prioritizes risk, preserves options, and assigns accountable follow-up.

Case analysis should produce decisions, not only observations.

Last updated: May 2026

Integrated Scenario: Compromised Supplier Access and Service Outage

A regional healthcare services company uses a managed billing platform hosted by a third-party provider. The company also runs its own identity provider, endpoint management, SOC tooling, and backup environment. On Monday morning, the SOC receives alerts for unusual VPN activity from a contractor account, several failed privileged login attempts, and a new mailbox forwarding rule for a finance manager. At the same time, the billing platform becomes slow and then unavailable for two clinics.

The first leadership task is to avoid treating the signals as unrelated noise. The incident commander should establish a trusted channel, assign a scribe, identify the business owner for billing, involve legal and privacy contacts, and direct the SOC to preserve logs. The team should not wait for perfect certainty before protecting the environment. It should declare a severity based on potential patient billing disruption, suspected credential compromise, possible data exposure, and third-party dependency.

Evidence preservation starts immediately. Identity provider logs, VPN logs, mailbox audit events, endpoint telemetry, service desk tickets, cloud or SaaS audit logs, and supplier status messages should be retained. The contractor account should be reviewed for recent access, group membership, MFA events, device posture, and sponsor status. If mailbox rules suggest business email compromise, finance processes may need temporary verification steps to prevent fraudulent payments.

Containment should be proportionate. The team might disable the contractor account, revoke active sessions, rotate related credentials, block suspicious IP addresses, and require step-up authentication for finance and administrator actions. It should also contact the billing provider through the contractual incident channel. If the provider hosts the affected service, the organization needs evidence and impact statements without assuming it can directly image provider systems.

Workstream Immediate question Likely owner Evidence or output

Identity Was the contractor account compromised or misused? IAM and SOC Login timeline, MFA data, session revocation

Email Did mailbox rules or payment workflows change? Messaging and finance Audit logs, rule inventory, payment hold decisions

Supplier Is the billing outage related to security or availability? Vendor manager and legal Provider notices, SLA data, incident updates

Business continuity Can clinics continue critical billing workflows? Clinic operations Manual procedure status and backlog estimate

Vulnerability operations Was an exposed weakness exploited? Infrastructure and app owners Scan data, patch records, configuration review

Communications Who needs accurate status updates? Incident command and communications Internal briefings, customer or regulator assessment

The investigation should separate facts from assumptions. A login from a new location is a fact. Compromise is a conclusion supported by other facts such as impossible travel, successful MFA fatigue, device mismatch, suspicious token activity, or actions inconsistent with the contractor role. The billing outage may be caused by the supplier, a network problem, a security event, or a normal operational failure. The team should keep hypotheses open and update them as evidence arrives.

Business continuity actions should not wait for the technical root cause. Clinics may need manual intake, delayed batch submission, alternate contact with the billing provider, or temporary prioritization of urgent cases. The business owner should decide acceptable degraded operations, while security ensures workaround channels do not create new exposure. If manual forms contain sensitive data, storage, access, and later reconciliation need controls.

Eradication and recovery depend on findings. If the contractor account was compromised through weak MFA, the organization may require stronger authentication, review sponsor approvals, remove stale access, and verify all contractor entitlements. If mailbox rules were abused, the team should remove rules, review delegated access, search for similar patterns, and confirm no payments were redirected. If the supplier outage is security-related, contractual notification, evidence sharing, and service recovery obligations matter.

Decision Register for the Case

  • Decision Criteria Accountable role
  • Declare incident severity Potential data exposure, service outage, privileged attempts Incident commander
  • Disable contractor account Suspicious access and low tolerance for continued risk IAM lead
  • Preserve supplier evidence Contract terms and outage relationship to incident Legal and vendor manager
  • Invoke manual clinic process Billing RTO and patient-service impact Business continuity lead
  • Notify external parties Legal threshold, confirmed facts, contractual duties Legal and communications
  • Close incident Recovery validated, monitoring stable, follow-up assigned Executive sponsor

Recovery should restore trust, not just availability. The billing platform may come back online, but the organization still needs to confirm data integrity, reconcile manual work, validate no unauthorized changes, and monitor for repeated account abuse. If the provider cannot explain the outage, leadership may enter the uncertainty in the risk register and require a service review. Supplier resilience is part of security operations, not a procurement afterthought.

The after-action review should produce concrete improvements. Possible actions include enforcing phishing-resistant MFA for contractors and administrators, reducing contractor standing access, adding mailbox rule detections, improving supplier log clauses, testing manual billing procedures, shortening alert escalation paths, and adding a runbook for simultaneous identity and vendor events. Each action should have an owner, due date, and risk acceptance path if deferred.

This case shows why CISSP security operations is managerial and technical at the same time. A purely technical response might disable accounts but miss clinic continuity or contract evidence. A purely business response might pressure the provider but leave identity compromise active. The stronger answer coordinates evidence, containment, legal readiness, supplier management, recovery, and control improvement in a sequence that reduces harm while preserving defensible decisions.