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 does a user account have an email address. Alternatively, you can use conditional tasks for more complex situations. For example, if an indicator was enriched and the reputation was set to bad, escalate the incident for managerial approval. However, if the indicator reputation is unknown or good, proceed down a different path.
Create a Conditional Task
In a playbook, click + Create Task.
Select the Conditional option.
Enter a meaningful name for the task that corresponds to the data you are collecting.
Select the option based on which the task is conditional. Valid values are:
- Built-in - create 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 - create a conditional task which must be manually resolved. For example, in an access incident investigation, you might ask the user if they attempted to access their account. A manual task could be to check if the user responded.
Choose automation - create 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 an 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. For detailed information for each configuration tab, see the Playboook Field Reference.