Create a conditional task in a playbook.
Conditional tasks are used for determining different paths for your playbook. You can use conditional tasks for something simple like proceeding if a certain integration exists, or whether a user account has an email address.
Alternatively, you can use conditional tasks for more complex situations. For example, if an indicator was enriched and the verdict was set to malicious, escalate the incident for managerial approval. However, if the indicator reputation is unknown or benign, proceed down a different route.
If the playbook was installed from a content pack, duplicate or detach the playbook, before creating a conditional task.
In a playbook, click + Create Task.
Select the Conditional option.
In the Task Name field, type a meaningful name for the task that corresponds to the data you are collecting.
Select the required option based on the conditional task.
Option
Description
Built-in
Creates a logical statement using an entity from within the playbook. For example, in an access investigation playbook, you can determine that if the Asset ID of the person whose account was being accessed exists in a VIP list, set the incident severity to High. Otherwise, proceed as normal.
Manual
Creates a conditional task that must be manually resolved. For example, a security analyst is prompted to review and validate a suspicious file. The playbook task might involve instructions for the analyst to analyze the file, determine if it is malicious, and provide feedback or take specific actions based on their assessment.
Ask
Creates an Ask tasks, the answer to which determines how a playbook proceeds.
Choose automation
Creates a conditional task based on the result of a script. For example, check if an IP address is internal or external using the IsIPInRanges automation. When using automation, the Inputs and Outputs are defined by the automation script.
Complete the task configuration in the remaining tabs. Some configurations are required, and some are optional.
Click Save.