CISSP domain - 13% of the exam

Security Operations

Security Operations is 13% of the CISSP exam. These are the objectives it covers, each with practice questions, with every answer explained.

The domain in numbers

39
Practice questions
15
Objectives
10
Easy
18
Medium
11
Hard

Where people go wrong

  • Destroying evidence before preserving it

    The wrong answers act on a compromised system in ways that destroy what an investigation needs. Pulling the cable before counsel and the incident plan are engaged, shutting down cleanly, logging in as the user, copying files through the operating system, or re-imaging first all lose volatile memory, timestamps or metadata. The correct answers involve the incident commander and counsel, capture volatile memory before a forensic image or live acquisition under chain of custody, and isolate the host while preserving its running state. Re-imaging comes later, at eradication.

    See it in a sample question
  • Picking a disaster recovery test that does not fit the plan

    The wrong answers choose a test type that does not suit the plan's maturity or the evidence wanted. A structured walkthrough is the first exercise after a new or revised plan, because it checks that procedures are coherent and roles understood without disruption. A simulation assumes the team already knows the procedures. A parallel test, with the alternate site processing a mirrored stream alongside production, gives measurable evidence against the recovery time objective. A full-interruption test carries the highest business risk and comes last.

    See it in a sample question
  • Skipping a step in the change lifecycle

    The wrong answers skip or reorder a step in the change lifecycle. Deploying straight to production, testing before a request is raised, a canary on a live server before pre-production testing, or a hotfix layered on a failed change all bypass a required control. The correct answers raise a documented change request, invoke the emergency change procedure for a critical internet-facing flaw, test the patch in a representative environment with a verified rollback, and execute the approved rollback when a change breaks a service.

    See it in a sample question
  • Automating, tightening or adding before measuring and tuning

    The wrong answers automate, tighten or add before the inputs have been measured or tuned. SOAR on poorly tuned rules, raised thresholds and extra rules leave the alert flood unexplained. Mass re-imaging, removing local admin, or widening the baseline come before drift has been quantified. SOAR rules parsed from emailed indicators, manual review or a broader feed leave intelligence unscored and unintegrated. The correct answers map rules to use cases, monitor against a documented baseline, and push scored indicators from a threat-intelligence platform into the SIEM and IDS/IPS.

    See it in a sample question
  • Stopping a post-incident review at one narrow output

    The wrong answers stop at one narrow output of a review: a blame session on an individual, a technical reconstruction, a single training update, archived evidence, the next routine exercise, or a targeted penetration test. Each captures only part of what the review should yield. The correct answers compare the timeline with the plan to find control, process and detection gaps, then update the plans, procedures, contact lists, controls and training, with owned actions.

    See it in a sample question

Objectives in this domain

What to study

The official documents this domain's practice questions cite most.

Sample questions from this domain

Free sampleSecurity Operationshard

A security analyst at a financial services firm receives an alert that a senior trader's workstation has been communicating with a known command-and-control domain. Counsel has indicated that the matter is likely to result in civil litigation against a former employee. The workstation is still powered on and the user is at lunch. What should the analyst do FIRST?

  • APull the network cable to contain the threat and then image the disk using a write-blocker before counsel arrives on site.
  • BNotify the incident commander and legal counsel, then acquire volatile data and a forensic image under documented chain of custody following the firm's incident response plan. Correct
  • CLog on to the workstation with the trader's account to triage running processes and copy suspicious files to a network share for the forensic team.
  • DReimage the workstation from the gold build to eradicate the malware and restore productivity, then escalate the indicators of compromise to the threat intelligence team.
Recognise that anticipated litigation triggers a legal-hold and evidence-preservation workflow before any containment or remediation action is taken. Once litigation is reasonably anticipated, the duty to preserve evidence attaches. The defensible sequence is to engage the incident commander and counsel so a legal hold is documented, then collect volatile data in order of volatility and a bit-for-bit image with hashes and chain of custody. Containment, eradication and recovery follow only after preservation, otherwise the resulting evidence is open to spoliation challenges and may be excluded.

Why A is wrong: Containment instinct is reasonable, but unilaterally yanking the cable can alert malware to wipe artefacts, destroys volatile state needed for litigation, and bypasses the documented incident response and legal hold workflow that counsel must drive.

Why B is correct: The correct manager-led action is to engage the incident commander and counsel so a legal hold can be invoked, then capture volatile evidence and a forensic image with chain of custody intact, preserving admissibility for the anticipated litigation.

Why C is wrong: Logging in as the user contaminates the evidence by writing new timestamps, swapping memory pages and modifying registry hives, and copying files over SMB destroys metadata that a defensible image would have preserved.

Why D is wrong: Reimaging is an eradication step that must come after evidence preservation; doing it first destroys the disk artefacts and volatile memory that counsel and any subsequent civil action depend on.

Free sampleSecurity Operationsmedium

A payments processor has run successful walkthrough and simulation exercises against its disaster recovery plan for the past two years, and the board now wants objective evidence that the alternate processing site can actually meet the recovery time objective for the authorisation platform. The CISO must recommend the next test type that produces this evidence while keeping customer-facing production transactions running. Which approach should the CISO recommend?

  • ARepeat the simulation exercise with a more aggressive injected scenario and measure how quickly the team declares a disaster
  • BConduct a parallel test in which the alternate site processes a mirrored transaction stream alongside production and reconciles results Correct
  • CSchedule a full-interruption test that shuts down the production authorisation platform and relies solely on the alternate site for several hours
  • DCommission an external auditor to review the DRP documentation and recent test reports and issue an attestation against the RTO
Choose the DRP test type that produces operational evidence of meeting the recovery time objective while preserving production availability. Walkthroughs and simulations validate plans and people but not infrastructure performance. A parallel test activates the alternate site and runs production-like transactions through it in parallel with the live environment, allowing the organisation to measure actual recovery and processing times against the RTO and to compare outputs for correctness. Because production continues uninterrupted, customer service is preserved while management gains defensible evidence of recoverability, which is the next logical maturity step before any full-interruption test is considered.

Why A is wrong: Repeating simulations refines team response but still exercises only decisions and paperwork, not the actual recovery infrastructure; it cannot produce defensible evidence that the alternate site meets the RTO for the authorisation platform.

Why B is correct: A parallel test brings the alternate site fully online and processes real or mirrored transactions concurrently with production, which provides measurable evidence that the recovery environment can meet the RTO and produce correct results without interrupting live customer service.

Why C is wrong: A full-interruption test is the most authoritative form of validation, but it directly exposes customer-facing transactions to recovery-environment risk and therefore conflicts with the requirement to keep production running; it is appropriate only once parallel testing has built sufficient confidence.

Why D is wrong: A documentation review and attestation may satisfy a compliance checkbox, but it relies on prior evidence rather than generating new operational proof; the board has asked for objective evidence that the site actually meets the RTO, which only an executed test against real workload can supply.

Free sampleSecurity Operationseasy

A network engineer at a mid-sized insurer needs to push a firewall rule update to allow a new claims portal to reach a back-end database. The change is technically simple and the engineer can deploy it in under a minute. According to the organisation's change management process, what should the engineer do FIRST?

  • ADeploy the rule change immediately in production and document it in the change log afterwards so the portal launch is not delayed.
  • BSubmit a formal change request through the change management system describing the change, business reason, risk, and rollback plan for approval by the change advisory body. Correct
  • COpen a peer-review ticket asking another firewall engineer to sanity-check the rule syntax before pushing it live to the production firewall later that afternoon.
  • DApply the firewall change in the test environment first to validate connectivity and then promote the same configuration into production once it works.
Identify that a formal, documented and approved change request is the first action in a controlled change management process. Change management is built around request, review, approval, implementation, and verification. Even small or seemingly low-risk changes must enter through the formal request channel so that the change authority can assess risk, confirm a rollback plan, and create an auditable record before any production work is performed.

Why A is wrong: Skipping authorisation and going straight to production is tempting when a change feels trivial, but bypassing the formal request and approval step removes the risk review, peer scrutiny, and audit trail that change management exists to provide.

Why B is correct: The first step in a controlled change process is raising a documented request that captures scope, justification, risk, and rollback so the change advisory board or equivalent authority can review and approve it before any work begins.

Why C is wrong: Peer review of the technical detail is useful, but it is not a substitute for the formal request and approval workflow; a colleague is not the authorising body and cannot accept the risk on behalf of the business.

Why D is wrong: Testing in a lower environment is a valid part of the change lifecycle, but it happens after the change request has been raised and approved; jumping into test work first still circumvents formal authorisation.

Free sampleSecurity Operationshard

A regional bank's SIEM is flooding the SOC with 18,000 alerts per day, and analysts have begun closing entire categories without investigation to keep the queue manageable. The CISO asks the SOC manager to propose the BEST first action to restore meaningful monitoring without losing detection coverage. Which approach should the SOC manager recommend?

  • AProcure a SOAR platform and migrate the noisiest categories of SIEM alerts into automated playbooks so analysts no longer see them.
  • BIncrease SIEM correlation thresholds and raise the severity floor analysts are required to investigate, so that low and medium alerts are suppressed for the next quarter.
  • CReassign two engineers to write new correlation rules against the latest threat-intelligence feed indicators so analysts see fresher, more relevant alerts.
  • DRun a tuning exercise that maps existing detection rules to specific risk scenarios and threat-informed use cases, then retire or reweight rules that do not support a defined use case. Correct
Recognise that resolving SIEM alert fatigue starts with use-case-driven rule tuning, not automation or threshold suppression. Alert fatigue is fundamentally a signal-to-noise problem rooted in detection rules that are not tied to a defined risk or threat scenario. A use-case catalogue (often aligned to MITRE ATT&CK or to specific risk statements) lets the SOC justify each rule's existence, retire orphaned detections, and reweight overlapping ones. Only once the catalogue is rational does SOAR automation or new threat-intel content yield durable improvement; otherwise the underlying noise is hidden, not removed.

Why A is wrong: SOAR amplifies the existing detection logic. Automating responses to poorly tuned rules industrialises the noise problem and can mask attacker activity behind auto-close playbooks; automation is the second step after the underlying use cases are sound.

Why B is wrong: Raising thresholds reduces visible volume but silently drops detection coverage, including the low-severity precursors of multi-stage attacks. It addresses the symptom (queue length) rather than the cause (unfocused rules) and is hard to defend to an auditor or regulator.

Why C is wrong: Adding more rules on top of an untuned ruleset increases volume and overlap. Threat-intel-driven detections only help once the existing use-case catalogue is rationalised; otherwise the SOC drowns faster, just in newer noise.

Why D is correct: Correct. Alert fatigue is a use-case problem first and a technology problem second. Mapping rules to defined detection use cases (often driven by a threat-led framework such as MITRE ATT&CK) lets the organisation justify what stays, what is reweighted, and what is retired, restoring meaningful triage without blindly silencing categories.

Free sampleSecurity Operationsmedium

Two weeks after a successful failover and restoration following a ransomware incident, a healthcare provider's CISO is planning the post-incident activities required by the DR plan. Systems are stable, services have been returned to the primary site, and the incident response team's technical report is complete. Which activity should the CISO prioritise NEXT to satisfy the DR process?

  • AArchive the incident response report and DR activation logs in the evidence repository so that they are available for any future regulatory enquiry.
  • BSchedule the next annual DR tabletop exercise so that the recovery teams remain trained on the existing runbooks for the coming year.
  • CCommission an external penetration test focused on the ransomware entry vector so that the underlying vulnerability cannot be exploited again.
  • DConvene a lessons-learned review with response, business, and communications stakeholders and feed the findings into updated DR plans, controls, and training. Correct
Identify the lessons-learned review as the DR process step that converts incident experience into updated plans, controls, and training. Disaster recovery is a cycle, not a one-off event. After response, assessment, and restoration, the lessons-learned phase brings together technical responders, business owners, and communications staff to examine what worked, what failed, and what surprised them. The outputs feed directly into revised DR plans, control changes, updated runbooks, and refreshed training, which is how the organisation actually becomes more resilient. Skipping straight to archiving, retesting, or scheduling the next exercise bypasses that feedback loop.

Why A is wrong: Archiving the evidence is part of good records management and supports regulatory defence, but it is a custodial step; on its own it does not feed improvements back into the DR plan, training, or controls and so does not close out the DR process.

Why B is wrong: Maintaining a regular exercise cadence matters, but scheduling the next routine tabletop before lessons learned have been captured risks rehearsing the same gaps that the recent incident exposed, rather than testing the improved plan.

Why C is wrong: A targeted penetration test may follow from the review's findings, but jumping straight to it skips the structured lessons-learned step and risks fixing one technical vector while leaving process, communications, and training gaps unchanged.

Why D is correct: The DR process explicitly includes a lessons-learned phase: a structured review with technical, business, and communications stakeholders converts the incident into updates to plans, controls, runbooks, and training, which is the mechanism that improves resilience over time.

Other domains in this exam

See also the CISSP cert hub, the study guide, and the cheat sheet.

Examworthy is not affiliated with or endorsed by ISC2. Original, blueprint-aligned practice material only.