Supported Cortex XSOAR versions: 6.6.0 and later.
This playbook handles external and internal scanning alerts.
Adversaries may attempt to get a listing of services running on remote hosts, including those that may be vulnerable to remote software exploitation. Methods to acquire this information include port scans and vulnerability scans using tools that are brought onto a system.
Investigate the scanner IP address using:
- IP enrichment:
- NGFW Internal Scan playbook
- Endpoint Investigation Plan playbook
- Entity enrichment
The playbook's response actions are based on the initial data provided within the alert. In that phase, the playbook will execute:
- Automatically block IP address
- Report IP address to AbuseIPDB (If configured as true in the playbook inputs)
When the playbook executes, it checks for additional activity using the Endpoint Investigation Plan playbook, and another phase, which includes the Containment Plan playbook, is executed. This phase will execute the following containment actions:
- Auto endpoint isolation
- Manual block indicators
- Manual file quarantine
- Manual disable user
- Click on the Incident Response icon on the left menu.
- Under Automation click on Incident Configuration.
- Select Playbook Triggers on the left panel.
- Click on New Trigger.
- Choose a trigger name e.g. Scanner Response.
- Under Playbook To Run, select NGFW Scan.
- Add trigger description - optional.
- Create a filter for the playbook trigger.
- Click on 'select field'.
- Choose 'Alert name'.
- Fill the value with 'Scan' and keep the 'contains' condition.
- Click Create
- Note that the playbook triggers are executed according to its order. Consider changing the trigger position for the execution order as intended. If not, other trigger may override the new trigger.
Before executing the playbook, please review the inputs and change them default values if needed.
Important playbook inputs you should pay attention to:
blockKnownScanner: Whether a benign IP address that has been previously seen in more than 5 alerts should be blocked.
reportIPAddress: (Relevant for an enabled AbuseIPDB integration) Whether to report the IP address to AbuseIPDB.
AutoContainment: Whether to execute the following response actions automatically or manually:
- Block indicators
- Quarantine file
- Disable user
HostAutoContainment: Whether to execute Endpoint Isolation automatically or manually.
In this playbook the remediation plan happens in two different phases:
- At an early stage of the playbook execution, if the IP address verdict is malicious, the IP is blocked using the Block IP - Generic v3 playbook.
- At a later stage, the playbook executes the Endpoint Investigation Plan, which searches for additional activity involving the scanner IP address. In this phase, based on the results of the Endpoint Investigation Plan playbook, the SOC is notified, and the Containment Plan playbook will be executed.
This playbook uses the following sub-playbooks, integrations, and scripts.
- Handle False Positive Alerts
- NGFW Internal Scan
- Containment Plan
- Recovery Plan
- Block IP - Generic v3
- Endpoint Investigation Plan
|scannerIP||The IP address of the scanner.||alert.hostip||Optional|
|blockKnownScanner||Whether to block the IP address based on previously seen scanning alerts.||true||Optional|
|AutoCloseAlert||Whether to close the alert automatically or manually, after an analyst's review.||false||Optional|
|AutoRecovery||Whether to execute the Recovery playbook.||false||Optional|
|SOCEmailAddress||The email address of the SOC.||Optional|
|reportIPAddress||Whether to report the IP address to AbuseIPDB.||false||Optional|
|AutoContainment||Whether to execute automatically or manually the containment plan tasks:|
* Block indicators
* Quarantine file
* Disable user
|HostAutoContainment||Whether to execute endpoint isolation automatically or manually.||false||Optional|
There are no outputs for this playbook.