Skip to main content

Cortex ASM - ASM Alert

This Playbook is part of the Cortex Attack Surface Management Pack.#

Supported versions

Supported Cortex XSOAR versions: 6.8.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 - Detect Service
  • Cortex ASM - Remediation Guidance
  • Cortex ASM - Remediation Path Rules
  • Cortex ASM - Remediation
  • Cortex ASM - Enrichment

Integrations#

  • ServiceNow v2

Scripts#

  • GridFieldSetup
  • GetTime
  • GenerateASMReport

Commands#

  • setAlert
  • send-mail
  • servicenow-create-ticket
  • closeInvestigation

Playbook Inputs#


NameDescriptionDefault ValueRequired
OwnerNotificationSubjectSubject of the notification (email or ticket) sent to potential service owner.A new security risk was identified on an external service owned by your teamRequired
OwnerNotificationBodyBody 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
RemediationNotificationSubjectSubject 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 teamRequired
RemediationNotificationHTMLBodyBody 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
BypassDevCheckDetermine 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".
FalseOptional
AcceptedRiskDsComma-separated list of instance/VM IDs that are considered accepted risk and should be closed.Optional
AcceptedRiskProjectsComma-separated list of projects numbers that are considered accepted risk and should be closed. For example, a list of GCP projects and AWS accounts.Optional
AcceptedRiskOtherComma-separated list of other items that are considered accepted risk and should be closed. For example, a list of folders numbers in GCP and subscription IDs in Azure.Optional

Playbook Outputs#


There are no outputs for this playbook.

Playbook Image#


Cortex ASM - ASM Alert