Security Incident Playbook

Invoke the security incident playbook flow automatically or manually.

A Playbook is visible only if at least one playbook is associated with a security incident. The playbook component works only for the Process Automation Designer (PAD) built processes and not for the flow designer-built flows. For the existing flow designer enabled flows, it will continue to work, and the activities will be continuing to be rendered as response tasks.

There are two ways of associating playbook with the security incident:

• Automatically invoke playbook
• Manually add playbook

Invoke playbook automatically

For a Playbook to be invoked automatically, a process needs to be defined using Process Automation Designer (PAD), and when the trigger condition is met then automatically the playbook tab is rendered with the playbook activities being displayed.

Add playbook manually

For a Playbook to be invoked manually, navigate to the Form UI action drop down and select Add Playbook. For more information see, Add Playbook

주:

If there is already a playbook available then the new playbooks added will run in parallel to the existing playbooks.

• Within the playbook, the analyst can filter the playbook cards by status.
• The analyst can cancel a playbook by selecting it from the ellipse icon.
• Within each activity, the analyst will be able to perform the actions defined within the activity cards such as Skip, Mark as complete, Cancel, or Orchestration actions such as Submit to sandbox, Search Emails and so on.
• Each of these actions are defined within the activity definition, and the complete card visible is customizable at the time of building the activity definition itself.

주:

All the future activity definitions and the next steps to be performed are displayed with a lock icon and are in read-only mode to the user. The playbook display mode is controlled by a configuration as explained below.

1. Navigate to All > Playbook Experiences.
2. In the Playbook Experiences page, select an SIR Playbook Experience.

   그림 1. Playbook Experience

   

   The Playbook Experience SIR Playbook Experience page is displayed.

   그림 2. Playbook Experience Record

   

3. Click on the Configuration record.

   

4. In the Configuration tab, click the SIR Playbook Experience Configuration.

   그림 3. Playbook Configuration

   

5. Navigate to the Pending Item Visibility field's drop down list, select the desired option and save the record. Choose from the following options:
   • Hide pending activities: Select this option to hide the pending activities that you would like to see on the playbook section of the workspace.

     그림 4. User Reported Phishing Example

     

   • Show pending stages and activities: Select this option to show pending stages and activities that you would to like to see on the playbook section of the workspace.

     그림 5. Show pending stages and activities

     

   • Hide pending activities and stages: Select this option to hide pending activities and stages,that you would like to see on the playbook section of the workspace.

     그림 6. Hide pending activities and stages

     

6. On the Playbook section, use the filter option to filter the activities by Playbook card status (activity definition).

   그림 7. Playbook card status

   

관련 개념

• Working with Security Incident Records
• Prerequisites for the Playbooks
• Rebuilding existing playbooks in Workflow Studio
• Activity Definitions
• Sample Playbooks for SIR Workspace
• Working with MSI Records
• Working with Form UI actions

관련 태스크

• Security Incident Closure workflow
• Handle security incidents using Advanced Work Assignment

Add Playbook

Use this section to add playbook manually.

시작하기 전에

Role required: sn_si.analyst

프로시저

1. Navigate to All > Security Incident > Security Analyst Workspace.
2. Open an incident record.
3. Click Add Playbook.

   

   The Add Playbook dialogue box is displayed.

   

4. Select the playbook template.
5. Click Add Playbook.
   A confirmation message dialogue box is displayed for you to confirm.
6. Click Add Anyway.

   

7. The Playbook gets added next to the Details tab.

   

8. Click the Playbook tab.
   
9. Perform the series of activities as listed to move to the next level.
   주:

   If a Security incident is associated with a playbook, until the associated playbook gets closed or cancelled the user cannot again associate the same playbook to the same security incident.