Skip to main content
Skip table of contents

My First Playbook

LAST UPDATED: JAN 8, 2025

In D3, playbooks provide a structured and automated approach to handling security incidents, ensuring workflow consistency, efficiency, and reliability. An incident playbook (now investigation playbook) is one that is used for automating the analysis and response of incidents.

Building the Playbook

  1. Navigate to the Incident Playbooks module.

    ClickIncidentPlaybooks.gif
  2. Click on the + Playbook button.

    Frame 34 (7)-20241129-162149.png
  3. Set up the incident playbook via the New Playbook popup.

    Frame 35 (5)-20241129-163134.png
    1. Enter a playbook name.

    2. Click on the OK button.

Testable vs Combined
  • In step 7, input values are entered for the (Send Email) command. The Testable radio option uses the newer UI for the process of inputting dynamic values, while the Combined radio option uses legacy UI from vSOC version 12.7.

  • By default, the Dynamic Input Method section is not visible, and the newer UI is used.

  1. Drag a Send Email command task onto the header branch of the initial playbook node.

    DragSendEmailToTrigger2.gif
    1. Click on the Command item within the task menu.

    2. Click on the Utility Commands tab within the popup.

    3. Type in Send Email within the search field, then press the Enter key.

    4. Drag the Send Email command onto the header branch of the playbook node.

  2. Assign a display name to the command.

    Frame 37 (9)-20241129-170443.png
    1. Enter the name to be displayed on the command node after the configuration popup is closed.

    2. Click on the image 31 (1)-20241129-170731.png button.

    3. Observe the node’s name change (in this case from "New Command Task 97" to "Send Email").

  3. Click back into the Send Email node, then click on the View Sample Data button.

    Frame 46 (11)-20241129-183529.png

    This popup displays the sample data formats for the inputs and outputs of this command task.

  4. Provide a valid email address within the first input parameter field, and enter a sample subject line and email body for the second and third input parameters.

    Frame 40 (8)-20241129-173049.png
How to input dynamic values?

In playbook workflows, values are often dynamic. Instead of manually entering text in the Email Body field, users can use the icon located at the right end of the field to select from available properties.


Testable (default)

Frame 81 (3)-20241212-003229.png
  1. Click on the icon.

  2. Click on the icon.

  3. Expand the field of interest.

  4. Expand the nested field of interest.

  5. Select the exact field of interest.

  6. Click on the Generate button.

  7. Exit the Format Builder popup.

    Frame 82 (3)-20241212-004031.png
  1. Ensure a placeholder has been inserted.

  2. Click on the Save button.

Combined

Frame 78 (12)-20241211-231013.png
  1. Click on the icon.

  2. Click on the + Insert Input Field button.

  3. Provide a descriptive name (of only letters and numbers, beginning with a letter) for the type of dynamic data to be retrieved.

  4. Click on the Add button.

Frame 79 (5)-20241212-000157.png
  1. Click on the relevant incident property.

  2. Click on the Finish button.

Frame 80 (5)-20241212-000652.png
  1. Ensure a placeholder has been inserted.

  2. Click on the Save button after customizing the Email Body.

  1. Ensure that the Auto Run checkbox beneath the last input parameter is selected.

    Frame 39 (8)-20241129-172508.png
  2. Click on the image 31 (1)-20241129-170731.png button to save the task configurations.

SUCCESS

This incident playbook is now ready to be linked to event playbooks (i.e. preprocessing playbooks).

Testing the Playbook

  1. Click on the Test Playbook button.

    Frame 42 (8)-20241129-173926.png
  2. Click on the Run Test button within the popup.

    Frame 43 (12)-20241129-174111.png
  3. Access the email account specified in the To Addresses parameter to verify that the email was received.

    Frame 41 (13)-20241129-174827.png
    mail.google.com_mail_u_0_ (6) 1-20241129-174953.png
JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.