Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bugfix/XSUP-30713/add-InternalIPRanges-as-playbook-input #31329

Merged
22 changes: 22 additions & 0 deletions Packs/CortexXDR/Playbooks/Cortex_XDR_Alerts_Handling.yml
Expand Up @@ -342,6 +342,9 @@ tasks:
xdr_alert_id:
complex:
root: inputs.alert_id
InternalIPRanges:
complex:
root: inputs.InternalIPRanges
separatecontext: true
continueonerrortype: ""
loop:
Expand Down Expand Up @@ -1459,6 +1462,25 @@ inputs:
required: false
description: Alert ID.
playbookInputQuery:
- key: InternalIPRanges
value:
complex:
root: lists
accessor: PrivateIPs
transformers:
- operator: RegexReplace
args:
action_dt: {}
ignore_case: {}
multi_line: {}
output_format: {}
period_matches_newline: {}
regex:
value:
simple: IANA_Private_Address
required: false
description: 'A list of IP ranges to check the IP against. The list should be provided in CIDR notation, separated by commas. An example of a list of ranges would be: "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 default list provided in the IsIPInRanges script (the known IPv4 private address ranges).'
playbookInputQuery:
outputs:
- contextPath: PaloAltoNetworksXDR.Incident.incident_id
description: Unique ID assigned to each returned incident.
Expand Down
Expand Up @@ -46,6 +46,7 @@ This playbook does not use any scripts.
| --- | --- | --- | --- |
| incident_id | Incident ID. | PaloAltoNetworksXDR.Incident.incident_id | Optional |
| alert_id | Alert ID. | PaloAltoNetworksXDR.Incident.alerts.alert_id | Optional |
| InternalIPRanges | A list of IP ranges to check the IP against. The list should be provided in CIDR notation, separated by commas. An example of a list of ranges would be: "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 default list provided in the IsIPInRanges script \(the known IPv4 private address ranges\). | lists.PrivateIPs | Optional |

## Playbook Outputs

Expand Down
Expand Up @@ -1608,6 +1608,9 @@ tasks:
'#none#':
- "79"
scriptarguments:
InternalIPRanges:
complex:
root: inputs.InternalRange
alert_id:
complex:
root: PaloAltoNetworksXDR.Incident.alerts
Expand Down Expand Up @@ -2013,7 +2016,21 @@ inputs:
description: This input indicates whether the playbook will hunt for related IOCs. Specify Yes/No.
playbookInputQuery:
- key: InternalRange
value: {}
value:
complex:
root: lists
accessor: PrivateIPs
transformers:
- operator: RegexReplace
args:
action_dt: {}
ignore_case: {}
multi_line: {}
output_format: {}
period_matches_newline: {}
regex:
value:
simple: IANA_Private_Address
required: false
description: "A 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 \n\"172.16.0.0/12,10.0.0.0/8,192.168.0.0/16\" (without quotes). \nIf a list is not provided, will use the default list provided in the IsIPInRanges."
playbookInputQuery:
Expand Down
Expand Up @@ -45,7 +45,7 @@ This playbook uses the following sub-playbooks, integrations, and scripts.
| incident_id | Incident ID. | incident.xdrincidentid | Optional |
| LinkSimilarIncidents | This input indicates whether the playbook will link similar incidents. To link similar incidents, specify Yes/No. | Yes | Optional |
| Hunting | This input indicates whether the playbook will hunt for related IOCs. Specify Yes/No. | Yes | Optional |
| InternalRange | A 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 <br/>"172.16.0.0/12,10.0.0.0/8,192.168.0.0/16" \(without quotes\). <br/>If a list is not provided, will use the default list provided in the IsIPInRanges. | | Optional |
| InternalRange | A 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 <br/>"172.16.0.0/12,10.0.0.0/8,192.168.0.0/16" \(without quotes\). <br/>If a list is not provided, will use the default list provided in the IsIPInRanges. | lists.PrivateIPs | Optional |
| CriticalUsernames | A comma-separated list of names of critical users in the organization.<br/>This will affect the calculated severity of the incident. | admin,administrator | Optional |
| CriticalHostnames | A comma-separated list of names of critical endpoints in the organization. This will affect the calculated severity of the incident. | | Optional |
| CriticalADGroups | A comma-separated list of DN names of critical Active Directory groups. This will affect the severity calculated for this incident. | | Optional |
Expand Down
10 changes: 10 additions & 0 deletions Packs/CortexXDR/ReleaseNotes/6_0_8.md
@@ -0,0 +1,10 @@

#### Playbooks

##### Cortex XDR incident handling v3

- Updated the "Port Scan" sub-playbook to get Internal IP ranges from inputs instead of static value.
efelmandar marked this conversation as resolved.
Show resolved Hide resolved

##### Cortex XDR Alerts Handling

- Added a new playbook input for Internal IP ranges.
2 changes: 1 addition & 1 deletion Packs/CortexXDR/pack_metadata.json
Expand Up @@ -2,7 +2,7 @@
"name": "Cortex XDR by Palo Alto Networks",
"description": "Automates Cortex XDR incident response, and includes custom Cortex XDR incident views and layouts to aid analyst investigations.",
"support": "xsoar",
"currentVersion": "6.0.7",
"currentVersion": "6.0.8",
"author": "Cortex XSOAR",
"url": "https://www.paloaltonetworks.com/cortex",
"email": "",
Expand Down