Supported Cortex XSOAR versions: 6.8.0 and later.
This playbook investigates a “Possible External RDP Brute Force” XDR Alert by gathering user, IP, and hostname information, and investigating if the following suspicious elements exists:
- "IP Reputation" - Dbot Score is 2-3
- "Source geolocation" - RDP Connection made from rare geo-location
- Related to campaign - IP address is related to campaign, based on TIM module
- Hunting results - the hunt for indicators related to the source IP and the related campaign returned results
- XDR Alert search - XDR Alerts that related to the same username and endpoint, and to the MITRE tactics that comes after "Credential Access", were found.
- Risky User - The user that was identified in the attack was given a medium or high score by XDR's ITDR module.
- Risky Host - The destination host that was identified in the attack was given a medium or high score by XDR's ITDR module.
Set verdict method:
Critical Element - The "Critical Element" input allows you to select a specific element that, if identified as suspicious, the investigation's final verdict will be deemed a "True Positive".
Final Verdict - Each suspicious element is being added to an array called "Suspicious Elements", which is used to count potential security threats. The array size will be compared to a final threshold. If the size is greater than or equal to the threshold, the investigation's final verdict will be deemed a "True Positive".
User Engagement - The "UserEngagementThreshold" input allows you to set the number of suspicious elements that trigger user engagement. When this threshold is met, an email will be sent to the user and their manager asking for authorization of RDP activity. If the RDP activity is not authorized by the user, the investigation's final verdict will be deemed a "True Positive".
This playbook uses the following sub-playbooks, integrations, and scripts.
- User Investigation - Generic
- Cortex XDR - Possible External RDP Brute-Force - Set Verdict
- Threat Hunting - Generic
- Account Enrichment - Generic v2.1
- Block Indicators - Generic v3
- Cortex XDR - Isolate Endpoint
- TIM - Indicator Relationships Analysis
- Cortex XDR - Get entity alerts by MITRE tactics
- Endpoint Enrichment - Generic v2.1
|Username||RDP connection username.||Optional|
|ExternalIP||Source external IP address.||Optional|
|AutoRemediation||Set this value to "true" to enable auto remediation (IP Block and User Block).||false||Optional|
|FinalThreshold||The threshold number of suspicious elements required to determine a 'True Positive' verdict.||3||Optional|
|CriticalElement||You can select a specific element that, if identified as suspicious, will automatically set the final verdict as true positive. The following options are available:|
NOTE: You can read about the meaning of every element in the playbook description.
|UserEngagementThreshold||The threshold number of suspicious elements that will trigger a user engagement. Set to 0 to disable user engagement.|
NOTICE: If this threshold is equal to or higher than "FinalThreshold", the final verdict will be deemed by the user response and not by the FinalThreshold calculation.
|Hostname||RDP connection destination hostname.||Optional|
|EndpointID||RDP connection destination endpoint ID.||Optional|
|Country||Source external IP country.||Optional|
|IsolateEndpoint||Set this value to "true" to enable endpoint isolation in case of a true positive.||false||Optional|
|SOCEmailAddress||The SOC email address to use for the user engagement section.||Optional|
|EarlyContainment||Set this value to "true" to allow early containment when the IP is known to be malicious.||true||Optional|
There are no outputs for this playbook.