Manually or periodically mitigate risks posed by CVEs detected on your managed internal and internet-facing assets.
A CVE is a vulnerability that may be exploited if not remediated. For more information
                  about CVEs on managed assets, see Vulnerabilities.
|  | ImportantYou must have the Cyber Risk Exposure Management entitlement enabled and the following
                                 required data sources configured to create CVEs with Global Exploit Activity playbooks: 
 | 
Procedure
- Go to .
- On the Playbooks tab, choose .
- On the Playbook Settings panel, select the Vulnerability type, specify a unique name for the playbook, and click Apply.
- On the Trigger Settings panel,
                        select the trigger type and click Apply.- 
Manual: Allows you to start the playbook execution by clicking the Run icon ( ) )
- 
Scheduled: Allows you to schedule the playbook to run daily, weekly, or monthly
 
- 
- On the Target Settings panel,
                        select and configure the Target for the playbook and
                        click Apply.If you need to mitigate risks for more than one target type, use the add node ( ) on the right of the
                           Trigger node. ) on the right of the
                           Trigger node.
- If you need to take actions when specific conditions are
                        met, configure the Condition node.- Click the add node ( ) on the right of the
                              Target node and click
                              Condition. ) on the right of the
                              Target node and click
                              Condition.
- Create a condition setting by specifying the
                              Parameter, Operator,
                              and Value.SettingDescriptionParameterFor more information about the parameters, see the Highly-Exploitable CVEs widget in the Operations Dashboard app.Operator- 
IS: The condition is triggered if any of the values is matched
- 
IS NOT: The condition is triggered if none of the values is matched
 ValueFor more information about the values for each parameter, see the Highly-Exploitable CVEs widget in the Threat and Exposure Management app.
- 
- If you need to configure multiple sets of
                              condition settings, click Add.The condition operator is evaluated using a logical AND.
- Click Apply.
- If you need to add more than one parallel
                              Condition node, click the add node ( ) on the right of the
                              Target node. ) on the right of the
                              Target node.
- If you need to configure action settings for the
                              Condition node, add an
                              Action node by clicking the add node ( ) on the right.For details, see Step 7. ) on the right.For details, see Step 7.
- If you need to configure else-if conditions or
                              else actions, add an Else-If Condition or
                              Else Action node by clicking the add node
                              ( ) under the
                              Condition node.For details, see Step 9. ) under the
                              Condition node.For details, see Step 9.
 
- Click the add node (
- Configure actions by adding an
                        Action node.- Click the add node ( ) on the right of the
                              Condition node and click
                              Action. ) on the right of the
                              Condition node and click
                              Action.
- On the Action Settings panel, select
                              Generate CSV file from the
                              Action drop-down list.The playbook consolidates CVEs detected and generates .CSV files that contain information about the CVEs and the affected assets.
- Select whether you want to get separate .CSV files by CVE.This setting determines whether the playbook sends consolidated or separate notifications if you also configure notification actions in a second Action node.
- Select whether to send a notification to request
                              manual approval to create general actions, and then configure the
                              notification settings if you require manual approval. NoteActions pending manual approval for over 24 hours expire and cannot be performed.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. TipTo add a webhook connection, click Create channel in the drop-down list.
- 
- Click Apply.
- If you need to add more than one parallel action,
                              use the add node ( ) on the right of the
                              Target or Condition
                              node. ) on the right of the
                              Target or Condition
                              node.
 
- Click the add node (
- Configure notification settings by adding the second
                        Action node.- Click the add node ( ) on the right of the first
                              Action node and click
                              Action. ) on the right of the first
                              Action node and click
                              Action.
- On the Action Settings panel, specify how to notify recipients of the playbook results.
- For email and webhook notifications, configure the
                              following settings.SettingDescriptionSubject 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. TipTo add a webhook connection, click Create channel in the drop-down list.
- For ServiceNow ticket notifications, configure the
                              following settings.SettingDescriptionTicket profileThe ServiceNow ticket profile to use TipIf 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
 
- 
- If you require manual approval for sending playbook results, follow
                              Step 7.d to configure the notification
                              settings. NoteThis setting is available only to ticket notification action.
- Click Apply.
 
- Click the add node (
- Configure Else-If Conditions or
                        Else Actions if necessary.- Click the add node ( ) below the Condition node and click Else-If Condition or Else Action. ) below the Condition node and click Else-If Condition or Else Action.
- Configure a Condition node by following Step 6 or an Action node by following Step 7 or Step 8.
  Note- 
The nodes that can be added by using an add node ( ) vary depending on the
                                                preceding node. For example, an Action
                                                node can only be possibly followed by another
                                                Action node; a
                                                Condition node can be followed by an
                                                Action node or have an
                                                Else-If Condition or Else
                                                   Action attached to it. ) vary depending on the
                                                preceding node. For example, an Action
                                                node can only be possibly followed by another
                                                Action node; a
                                                Condition node can be followed by an
                                                Action node or have an
                                                Else-If Condition or Else
                                                   Action attached to it.
- 
When a condition is false, the playbook performs the Else Action or checks if its Else-If Condition is met. If the Else-If Condition is met, the playbook continues to perform the corresponding Else Action.
- 
Multiple Action nodes configured in a serial mode are taken sequentially.
 
- Click the add node (
- Enable the playbook by toggling the Enable control on.
- Click Save.The playbook appears on the Playbooks tab in the Security Playbooks app.
 
		