Run the automated phishing response playbook flow

Freigeben Version: Australia

Aktualisiert 12. März 2026

6 Minuten Lesedauer

Using the flow designer, you can define and automate tasks in the playbook to analyze and resolve phishing attacks against your organization.

Vorbereitungen

Role required: sn_si.admin, flow_designer, and action_designer
Install and configure the following integrations with the right credentials:
- Block Request (Security Operations Palo Alto Networks NGFW Integration)
- Observable Enrichment
- Sighting search
- Threat Lookup
- Microsoft Office Exchange

Warum und wann dieser Vorgang ausgeführt wird

When employees receive a suspicious email that contains the common signs of a phishing attack (as defined by your security policies), they can send it as an .EML attachment to the phishing email address defined by your organization. Using the tasks defined in the automated phishing playbook flow, you can triage, analyze, contain, and eradicate a phishing threat. These tasks can be invoked as part of different incident states (for example, Analysis, Contain, and so forth). When a phishing security incident is created, the automated phishing flow can be automatically triggered. Using flow designer, you can view the details of the various incident response actions as they are invoked.

Hinweis:

The Security Incident - Automated Phishing Response Template V1 playbook flow is Read Only. You can make a copy of the flow and make changes as required.

The following steps describe how to make a copy of the phishing playbook template and walks you through some of the tasks in the flow.

Prozedur

Navigate to All > Flow Designer > Designer to view the flows available with the Security Operations Spoke.
Click the Security Incident - Automated Phishing Response Template VI link.
In the Flow page, click the more icon , make a copy of the flow and open it for your use.
You can modify the trigger conditions, add or remove actions, and make other changes to the flow.
This image shows the trigger conditions, and the steps that the flow executes. The right-hand panel shows the data flow. Click an icon to expand the step and view the details.
Click the Trigger icon.
In the first step, you define or set the trigger for the flow. Specify the conditions for the trigger and how often you want the flow to execute the trigger.
When the conditions defined in the flow (Category is Phishing and Source is Email) are met in the incident record, the tasks in the automated phishing flow start executing sequentially. You can modify the trigger, add annotations, add or delete conditions, and so on.
Click the Update Security Incident Record link.

The Update Security Incident Record is the first step in the flow. Click the annotation icon to add a note to the security analyst indicating that a phishing incident has occurred, and the automated phishing playbook flow has begun executing.
Proceed with the step 2 in the flow, and click the Create Response Task link.

In this step, the flow creates an automated response task to acknowledge receipt to the submitter of the incident or the affected user.

Notice the Parent Task [Security Incident] field references the parent record associated with this step. You can pick any reference record by using the data pill picker icon or drag the relevant reference item from the right-hand panel. Notice the lock icon . The lock icon indicates that step does not require any user intervention.
In step 3, the flow collects additional details of the affected user (typically the user who submitted the incident) to ensure that it can send a notification successfully.
You can specify conditions to check if the affected user's status is active and the user is able to receive notifications.
Notice the conditional step icon in step 3. The flow executes the next step (3.1) only if the specified conditions are met.

When the conditions defined in step 3 have been met successfully, the email is sent.
In step 4, after the email has been sent, the response task is marked as closed.
In step 5, all the observables involved in the incident (such as email subject, email address from which the phishing email was sent, phishing URL) or observables belonging a selected category (hash, file, or domain) are collected to perform additional automated actions in the subsequent playbook steps.

Click the action designer icon to see a detailed view of the action.

To view the Action Designer page, expand a step in the flow and click the action designer icon.
In step 6, an automated response task is created.
This task captures the beginning of process of getting the reputation of all observables and performing enrichment with configured integrations.
In step 7, two subflows are called:
- Run Threat Lookups for Observables: This subflow is used to get the reputation of all observables using threat look up implementations.
- Enrich Observables: This subflow is used perform enrichment of observables with configured implementations.
Notice the icons for this task. The parallel operations icon indicates that both the tasks will be performed in parallel and the subflow icon indicates that the task being performed is a subflow as shown below:

Notice the number 5 in the observables field. This indicates that the threat lookup will be run on observables retrieved in step 5. This subflow in turn calls existing workflows and actions as shown in the Subflow Designer.
In step 8, after the subflows have been completed, the response task is marked as Closed.
In step 9, the Confirm Threat from Observable Triage subflow is called.
This subflow is used to confirm the presence of a threat indicator in the incident. If the threat is confirmed, an 'IOC Detected' flag is added to the incident.
When the threat is confirmed, in step 10, you update the security incident and add a note indicating that threat containment tasks will be launched.
Step 11 is an automated response task that captures the start and completion of the task used to assess the impact of the phishing emails.
In step 12, the Assess Phishing Email Impact subflow is called.
This subflow is used to search for users who have received the phishing email using supported implementations.
In step 13, the task is marked as closed to indicate that the Assess Phishing Email Impact subflow has been executed.
Step 14 is used to retrieve all observables that have been marked as malicious.
Step 15 is an automated response task that captures the start and completion of the sighting search of observables task.
In step 16, the Run Sightings Search on Observables subflow is called.
This subflow performs a sightings search using the configured implementation.
In step 17, the task is marked as closed to indicate that the Run Sightings Search on Observables subflow has been completed.
After you have identified the malicious observables, in step 18, you update the security incident record to indicate that the containment actions will now commence.
Step 19 is an automated response task that captures the start and completion of the block requests task.
In step 20, the Create Block Requests subflow is called.
This subflow is used to block malicious observables.
In step 21, the task is marked as closed to indicate that the Create Block Requests subflow has been completed.
In step 22, the Eradicate Phishing Emails subflow is called.
This subflow is used to delete phishing emails from user mailboxes.
After the phishing emails have been deleted, in step 23, you update the security incident record to indicate that the incident status needs to be reviewed.
In the last step, the flow creates an automated response task.
This task is used to send a reminder to the security analyst to save all the incident response actions for future reviews.

Nächste Maßnahme

You can click Test to simulate the actions in the flow before you publish it. After testing the flow, click Activate to activate the flow and execute it.

Click Executions to view the execution details of the flow.

Automated phishing flow: execution