Skip to main content

Cortex XDR incident handling v3

Supported versions

Supported Cortex XSOAR versions: 6.0.0 and later.

This playbook is triggered by fetching a Palo Alto Networks Cortex XDR incident. The playbook syncs and updates new XDR alerts that construct the incident and triggers a sub-playbook to handle each alert by type. Then, the playbook performs enrichment on the incident’s indicators and hunts for related IOCs. Based on the severity, it lets the analyst decide whether to continue to the remediation stage or close the investigation as a false positive. After the remediation, if there are no new alerts, the playbook stops the alert sync and closes the XDR incident and investigation. For performing the bidirectional sync, the playbook uses the incoming and outgoing mirroring feature added in XSOAR version 6.0.0. After the Calculate Severity - Generic v2 sub-playbook’s run, Cortex XSOAR will be treated as the single source of truth for the severity field, and it will sync only from Cortex XSOAR to XDR, so manual changes for the severity field in XDR will not update in the XSOAR incident.

Dependencies#

This playbook uses the following sub-playbooks, integrations, and scripts.

Sub-playbooks#

  • Palo Alto Networks - Hunting And Threat Detection
  • Cortex XDR Alerts Handling
  • Block Indicators - Generic v2
  • Cortex XDR device control violations
  • Calculate Severity - Generic v2
  • Entity Enrichment - Generic v3

Integrations#

  • CortexXDRIR
  • Cortex XDR - IR

Scripts#

This playbook does not use any scripts.

Commands#

  • linkIncidents
  • xdr-update-incident
  • closeInvestigation
  • xdr-get-incident-extra-data

Playbook Inputs#


NameDescriptionDefault ValueRequired
incident_idIncident ID.incident.xdrincidentidOptional
similarIncidentFieldsA comma-separated list of similar incident field keys.xdrdescriptionOptional
LinkSimilarIncidentsThis input indicates whether the playbook will link similar incidents. To link similar incidents, Specify Yes/No.YesOptional
HuntingThis input indicates whether the playbook will hunt for related IOCs. Specify Yes/No.YesOptional
InternalRangeA comma-separated list of internal IP ranges to check IP addresses against. The list should be provided in CIDR notation. An example of a list
"172.16.0.0/12,10.0.0.0/8,192.168.0.0/16" (without quotes).
If a list is not provided, will use the default list provided in the IsIPInRanges,
Optional
CriticalUsernamesA comma-separated list of names of critical users in the organization.
This will affect the calculated severity of the incident.
admin,administratorOptional
CriticalHostnamesA comma-separated list of names of critical endpoints in the organization. This will affect the calculated severity of the incident.Optional
CriticalADGroupsCSV of DN names of critical Active Directory groups. This will affect the severity calculated for this incident.Optional
InternalHostRegexThis is provided for the script IsInternalHostName that checks if the detected host names are internal or external if the hosts match the organization's naming convention. For example, the host testpc1 will have the following regex \w{6}\d{1}.Optional
InternalDomainNameThe organizations internal domain name. This is provided for the script IsInternalHostName that checks if the detected host names are internal or external if the hosts contain the internal domains suffix. For example, xsoar.com. If there is more than one domain, use the | character to separate values such as (xsoar.com|test.com).Optional
TimeStampTimestamp in relative date format for query device control events from Cortex XDR.10 daysOptional
AutoRemediationWhether remediation will be run automatically or manually. If set to "True" - remediation will be automatic.FalseOptional

Playbook Outputs#


There are no outputs for this playbook.

Playbook Image#


Cortex XDR incident handling v3