Question

Difficulty: MediumSecurity Automation and Orchestration (SOAR)

A Security Operations Center (SOC) team is configuring an automated Security Orchestration, Automation, and Response (SOAR) playbook to contain endpoints exhibiting active ransomware encryption behavior. During testing, an automated containment playbook executed on a Domain Controller following a false-positive detection, causing enterprise-wide service disruptions. Which modification to the SOAR playbook logic best balances rapid automated containment with operational risk management for critical infrastructure?

  1. Insert a conditional decision node that routes host isolation actions for critical asset tags to an analyst manual approval step while automatically isolating non-critical endpoints.Answer
  2. B
    Configure the automated playbook trigger to execute full network isolation on all endpoints regardless of asset tags whenever any high-severity endpoint alert is received.
  3. C
    Remove the automated containment playbook entirely and replace it with a detective SIEM dashboard counter to manually log ransomware indicators.
  4. D
    Reconfigure the SOAR platform API integration with the endpoint detection tool from OAuth 2.0 bearer tokens to cleartext basic authentication.

Answer

The correct modification is to insert a conditional decision node that routes host isolation actions for critical asset tags to an analyst manual approval step while automatically isolating non-critical endpoints.
The correct choice implements asset-aware conditional logic within the SOAR playbook. By checking asset tags prior to containment actions, non-critical endpoints can be isolated immediately at machine speed, whereas high-impact assets (such as Domain Controllers or core servers) require a human-in-the-loop approval step to verify the alert before taking disruptive isolation measures.

Step-by-Step Solution

1
Analyze the operational impact of unconstrained automation on critical infrastructure.
Identified that auto-isolating critical systems like Domain Controllers based on unverified triggers introduces unacceptable business outage risks.
SOAR playbooks must balance velocity of response with the operational risk of false positives.
2
Evaluate playbook decision logic modifications.
Adding contextual asset checks (e.g., checking asset tagging or CMDB data) enables granular workflows.
Criticality-aware playbooks can enforce different actions based on host importance.
3
Establish the optimal hybrid response mechanism.
Automate isolation for standard workstations and non-critical hosts, but gate isolation actions on critical servers behind human-in-the-loop analyst approval.
This maintains automated defense speed where acceptable while safeguarding enterprise availability.

Key Concept

SOAR Playbook Triage and Safe Automated Containment Logic
Rate this question