Collect evidence to support threat investigation and incident response by creating evidence collection playbooks.
Collect detailed evidence from potentially compromised endpoints for internal investigations
into critical incidents that occurred on your network and may require further attention.
Important
|
Procedure
- Go to .
- On the Playbooks tab, choose .
- Select Incident Response Evidence Collection and click Create Playbook from Template.
- Configure the playbook settings and click Apply.
Note
You must specify a unique name for the playbook. - To customize the name of the trigger node, click the edit icon ().
- Identify target endpoints for evidence collection by endpoint names or IP
addresses.
-
To collect evidence from endpoints by Endpoint name, specify the endpoint names in the Endpoint name text box.
-
To collect evidence from endpoints by IP address, specify the IP address or IP range in the IP address text box.A maximum of 10 IP ranges can be used. Examples of the IP range are as follows:
-
10.1.0.*
-
192.168.1.0/24
-
192.168.1.10–192.168.1.20
In CIDR notation, the prefix length should range from 16 to 32. When using the Start IP–End IP format, the first two octets (representing the network portion) must be identical for all IP addresses within the range. -
-
- Configure the manual approval settings in the first action node (default name:
Notify recipients for manual approval
).- (Optional) Specify a custom Name for the node.
- Select whether to send a notification to request
manual approval to create response actions.
Important
Actions pending manual approval for over 24 hours expire and cannot be performed. - If you require manual approval, configure the
following settings.SettingDescriptionNotification method
-
Email: Sends an email notification to specified recipients
-
Webhook: Sends a notification to specified webhook channels
Subject prefixThe prefix that appears at the start of the notification subject lineRecipientsThe email addresses of recipientsThe field only appears if you select Email for Notification method.WebhookThe webhook channels to receive notificationsThe field only appears if you select Webhook for Notification method.Tip
To add a webhook connection, click Create channel in the drop-down list. -
- Configure evidence collection in the next action node (default name:
Collect evidence
).SettingDescriptionNameThe node nameEvidence typesTypes of evidence to collectNote
Basic information is required.Archive location on endpointLocation of the archive on the local endpointImportant
-
The local archive does not have encryption, and remains on the endpoint until deleted. This may allow access to sensitive information to anyone with access to the file system or reveal the presence of an ongoing investigation.
-
Evidence archives take up hard drive space and may impact endpoint performance.
Upload evidence to Trend Vision OneUploads evidence to the Forensics app in the Trend Vision One consoleImportant
The playbook requires credits to upload the collected evidence to the Forensics app in the Trend Vision One console. Configure the data allowance in Forensics before you set up the playbook to upload evidence.If the data allowance is not configured, all playbooks created before October 13, 2023 with Upload evidence to Trend Vision One turned on will not be able to collect evidence, store it locally, or upload it to the Forensic app.Tip
Find uploaded evidence on the Execution Results page in the Security Playbooks app. -
- Specify how to notify recipients of the playbook results
by configuring the second path selection node.
Note
You can only select one path for notification of results. - For email and webhook notifications, configure the action node (default name:
Send notification of results
).SettingDescriptionNameThe node nameNotification method-
Email: Sends an email notification to specified recipients
-
Webhook: Sends a notification to specified webhook channels
Subject prefixThe prefix that appears at the start of the notification subject lineRecipientsThe email addresses of recipientsThe field only appears if you select Email for Notification method.WebhookThe webhook channels to receive notificationsThe field only appears if you select Webhook for Notification method.Tip
If you need to add a webhook connection, click Create channel in the drop-down list. -
- For ServiceNow ticket notifications, configure the two action nodes.
- Follow Step 7 to configure the first action node (default name:
Notify recipients for manual approval
). - Configure the next action node (default name:
Send ticket notification of results
).SettingDescriptionNameThe node nameNotification methodThe action node can only sendTicket
notificationsTicket profileThe ServiceNow ticket profile to useTip
If you need to add a ticket profile, click Create ticket profile in the drop-down list.Ticket profile settingsThe ticket profile settings for the playbookSelecting a ticket profile automatically loads the settings. Changing the settings overrides the ticket profile for the playbook.-
Assignment group: The ServiceNow assignment group you want to assign the ticket to
-
Assigned to: The ServiceNow user you want to assign the ticket to
-
Short description: A short description of the ticket which displays in ServiceNow
-
- Follow Step 7 to configure the first action node (default name:
- Enable the playbook by toggling the Enable control on.
- Click Save.The playbook appears on the Playbooks tab in the Security Playbooks app.