The following example uses alert context data as the playbook input from the Access Investigation - Generic playbook.
Click the top task Playbook Triggered. The playbook is triggered based on incident context data.
Inputs
The first two inputs are SrcIP
, retrieved from the incident.src
key, and DstIP
, retrieved from the incident.dest
key.
Outputs
The Access Investigation - Generic playbook creates an output object that can be used in subsequent playbook tasks.
For example, the Access Investigation - Generic playbook Endpoint.IP
output creates a list of endpoint IP addresses which can later be enriched by an IP enrichment task, and the Endpoint.MAC
output creates a list of endpoint MAC addresses which can be used to get information about the hosts that were affected by the alerts.
For example, the Access Investigation - Generic playbook Endpoint.IP
output creates a list of endpoint IP addresses which can later be enriched by an IP enrichment task, and the Endpoint.MAC
output creates a list of endpoint MAC addresses which can be used to get information about the hosts that were affected by the incidents.
Outputs can also be data that was extracted or derived from the inputs. For example, the Access Investigation - Generic playbook contains the Account Enrichment - Generic v2.1 sub-task, which uses the account username (and optionally domain) as input to Active Directory to retrieve user information as output, such as the user's email address, manager, and any groups to which they belong.
An output can then serve as input for a subsequent task. For example, in the Account Enrichment - Generic v2.1 sub-task, the Get account info from Active Directory task output Account.Username
is used as an input for the Active Directory - Get User Manager Details task to retrieve manager details for that user.