Cortex ASM - ASM Alert
This Playbook is part of the Cortex Attack Surface Management Pack.#
Supported versions
Supported Cortex XSOAR versions: 6.9.0 and later.
This playbook handles ASM alerts by enriching asset information and providing a means of remediating the issue directly or through contacting service owners.
Dependencies#
This playbook uses the following sub-playbooks, integrations, and scripts.
Sub-playbooks#
- Cortex ASM - Jira Notification
- Cortex ASM - Detect Service
- Cortex ASM - Remediation Path Rules
- Cortex ASM - Email Notification
- Cortex ASM - ServiceNow Notification
- Cortex ASM - Remediation
- Cortex ASM - Enrichment
- Cortex ASM - Remediation Guidance
Integrations#
This playbook does not use any integrations.
Scripts#
- GenerateASMReport
- GridFieldSetup
- DeleteContext
Commands#
- closeInvestigation
- setAlert
- send-mail
Playbook Inputs#
| Name | Description | Default Value | Required |
|---|---|---|---|
| OwnerNotificationSubject | Subject of the notification (email or ticket) sent to potential service owner. | A new security risk was identified on an external service owned by your team | Required |
| OwnerNotificationBody | Body of the notification (email or ticket) sent to potential service owner. | Infosec identified a security risk on an external service potentially owned by your team: ${alert.name}<br><br> Description: ${alert.details} <br><br> | Required |
| NotificationTicketType | The ticket type used by ticketing systems. The default is "incident" because ticketing systems such as ServiceNow and Cherwell use it as default. | incident | Required |
| RemediationNotificationSubject | Subject of the notification (email or ticket) sent to the service owner after remediation. | A new security risk was addressed on an external service owned by your team | Required |
| RemediationNotificationHTMLBody | Body of the notification (email or ticket) sent to the service owner after remediation. | <!DOCTYPE html> <html lang="en"> <body> <p> Infosec identified a security risk on an external service potentially owned by your team:<br><b>${alert.name}</b> </p> <p> <b>Alert Details:</b> ${alert.details}<br> <b>Action Taken:</b> ${alert.asmremediation.[0].action}<br> <b>Action Outcome:</b> ${alert.asmremediation.[0].outcome}<br> </p> </body> </html> | Required |
| BypassDevCheck | Determine whether to bypass the Dev Check in automated remediation criteria: https://docs-cortex.paloaltonetworks.com/r/Cortex-XPANSE/Cortex-Xpanse-Expander-User-Guide/Automated-Remediation-Capabilities-Matrix Set to "True" if you want to bypass. Default is "False". | False | Optional |
| AcceptedRiskDs | Comma-separated list of instance/VM IDs that are considered an accepted risk and that should be closed. | Optional | |
| AcceptedRiskProjects | Comma-separated list of projects numbers that are considered an accepted risk and that should be closed. For example, a list of GCP projects and AWS accounts. | Optional | |
| AcceptedRiskOther | Comma-separated list of other items that are considered an accepted risk and that should be closed. For example, a list of folders numbers in GCP and subscription IDs in Azure. | Optional | |
| JiraProjectKey | The Jira project key to associate with the issue. | XPANSE | Required |
Playbook Outputs#
There are no outputs for this playbook.
Playbook Image#
