Playbook for Child Security Incident Automation

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Playbook for Child Security Incident Automation

    The Child Security Incident Automation playbook is designed to streamline the investigation and closure of duplicate security incidents, termed as child security incidents. By automatically consolidating relevant information into the parent security incident, this playbook significantly reduces response time and enhances efficiency in security operations.

    Show full answer Show less

    Key Features

    • Incident Management: Transitions child security incidents to the Analysis stage.
    • Duplication Elimination: Rolls up affected users and configuration items (CIs) from child incidents to the parent incident.
    • Observable Management: Integrates observables from child incidents into the parent incident.
    • Closure Automation: Automatically closes or cancels child incidents once the parent incident is resolved.

    Key Outcomes

    By utilizing this playbook, organizations can expect quicker resolution of security incidents, improved accuracy in incident reporting, and a more streamlined approach to managing security threats. This playbook requires the installation of the Security Operations Spoke and specific user roles to function effectively.

    Getting Started

    To implement the playbook:

    • Log in with the required roles (snsi.user and flowdesigner).
    • Access the Flow Designer and copy the Child Security Incident Automation playbook for customization if needed.
    • Activate the playbook for immediate use.

    The playbook executes when a parent security incident exists and is in certain states (Draft, Analysis, Contain, or Eradicate), allowing it to efficiently manage and consolidate incident data.

    Duplicate security incidents are categorized as child security incidents and are rolled up to the parent security incidents.

    The Child Security Incident Automation playbook helps reduce the time required to investigate and close duplicate security incidents. This playbook automatically rolls up specific unique artifacts of the child security incident (observables, affected users, CIs) to the parent security incident.

    Prerequisites

    Role required:
    • sn_si.admin
    • flow_designer

    Spoke: Install Security Operations Spoke (sn_sec_spoke)

    Key capabilities

    The Child Automation playbook covers the following capabilities:

    1. Moves the security incident to the Analysis stage.
    2. Eliminates duplicates and adds (rolls up) the affected users and CIs to the parent security incident.
    3. Adds observables from the child incident to the parent security incident.
    4. Closes or cancels the child security incident when the parent security incident is closed.

    Capabilities required

    For more information, see the ServiceNow store.

    Security analyst experience

    To understand how to resolve security threats in a step-by-step manner, see Resolve security threats with the playbook.

    Deeper understanding of the Child Security Incident Automation playbook with Flow Designer capabilities

    Getting Started
    1. Login as a user with sn_si.user and flow_designer roles.
    2. Navigate to Flow Designer > Designer and click on the Failed Login playbook.
    3. Make a copy of the Child Security Incident Automation playbook and make the necessary modifications. (This is an optional step. Follow this step only if you plan to customize or make specific changes to the flow).
    4. Make the necessary modifications according to your requirement. (This is an optional step. Follow this step only if you plan to customize or make specific changes to the flow).
    5. Activate the playbook.
      • Activate the main flow to use the playbook available with the base system.
      • Activate the copied flow after making any modifications according to your requirements.
    The following image shows a copy of the Child Security Incident Automation playbook. Review the steps below to get an understanding of the various actions in the playbook.
    Child Automation Flow:Overview
    This playbook is triggered when:
    • The parent security incident field isn’t empty.
    • The parent security incident is in Draft, Analysis, Contain, or Eradicate state.

    Child Automation playbook: Trigger

    The following steps walk you through the actions and tasks that are available in the Child Security Incident Automation playbook.

    1. When the playbook starts executing, in Step 1, if the security incident is in a Draft state, it’s updated and set to the Analysis state.
      Child Automation playbook: step 1
    2. In steps 2 and 3, affected users for the security incident are retrieved and rolled up to the parent security incident. Any duplicate users are eliminated.
    3. In steps 4 and 5, configuration items associated with the child security incident are retrieved and unique CIs are rolled up to the parent security incident.
      Child automation playbook: step 5
    4. In steps 6 and 7, observables associated with the child security incident are retrieved and unique observables are rolled up to the parent security incident.
      Child automation playbook: step 7
    5. In steps 8 and 9, automated worknotes are posted to the parent and child security incidents indicating that the affected users, configuration items, and observables have been rolled up from the child to the parent security incident.