General Concept

A playbook consists of a sequence of steps, designated as "playbook steps", that are designed to ultimately automate tasks and achieve specific goals. Playbook steps can be used as building blocks, allowing you to quickly iterate new flows that suit your needs for investigation and response.

Designing a Playbook

When designing a playbook, consider the following:

• What are the critical actions you wish to accomplish?

• What are the triggers/conditions needed to execute your actions?

• Do you require loops (playbook feature that repeats a set of actions)?

• Do you have any time related requirements for your triggers/conditions/actions?

• What remediation actions are needed?

General Step By Step Process

A playbook is created on a visual canvas, called the Playbook Designer. You start with a Trigger Step, which you must define and save. Next, take a connection point and drag-and-drop to an empty area to create a placeholder step, which opens the Select Step pane. Available playbook steps will appear. Configure it according to your requirements, then save it. This step is now connected to the Trigger step. Continue adding and configuring steps based on your use case to complete the playbook workflow. A playbook ends when no further steps remain.

Detailed Playbook Information

Click on any of the following links to get more information on Playbook designer, Playbook steps, or a specific type of Playbook steps.

Playbook Designer: Explains the functions available in Playbook Designer to create/modify a playbook.

Playbook Steps: Explains functions and actions available when adding/editing a playbook step.

• Trigger Steps: The starting point of a playbook. All steps follow after a Trigger Step.

• Core Steps: Create and store contextual information relevant to the playbook.

• Evaluate Steps: Define logical flows within the playbook. These include decision points, time delays, and user input.

• Execute Steps: Perform automated operations.

• References Steps: Utilize other playbook(s), forming a chain of playbooks.

• Email Steps: Automatically send email to users identified in the step with either specific static criteria or record-relevant data using dynamic values.