Multiple External EDR Alerts by Host
This rule detects multiple external EDR alerts on the same host, indicating a potential compromise, by analyzing alert data from various EDR solutions like CrowdStrike, SentinelOne, and M365 Defender to identify hosts triggering multiple alerts, enabling prioritization of investigation and response.
This detection rule identifies hosts triggering multiple alerts from external Endpoint Detection and Response (EDR) solutions, indicating a potential compromise. It aggregates alert data from sources such as CrowdStrike, SentinelOne, and Microsoft 365 Defender to identify hosts exhibiting a high volume or diversity of security alerts. The rule aims to detect coordinated attacks across multiple hosts, warranting prioritized investigation and response. It prioritizes hosts that trigger a specific threshold of unique alert rules, different alert severities, or have repetitive patterns involving file paths, command lines, or processes. This approach allows security analysts to focus on systems with a higher likelihood of compromise, reducing the time to detect and respond to potential threats.
Attack Chain
- Initial Access: An attacker gains initial access to a host through various means, such as exploiting a vulnerability or using stolen credentials.
- Malware Deployment: The attacker deploys malware onto the compromised host. This could be achieved through techniques like phishing or exploiting software vulnerabilities.
- Execution: The malware executes on the host, initiating malicious activities. This may involve running malicious scripts or binaries.
- Persistence: The malware establishes persistence on the host to maintain access even after a reboot. This can be achieved by creating scheduled tasks or modifying registry keys.
- Lateral Movement: The attacker attempts to move laterally to other hosts on the network. This can involve using techniques like pass-the-hash or exploiting network vulnerabilities.
- Command and Control: The malware establishes communication with a command and control (C2) server to receive instructions and exfiltrate data.
- Privilege Escalation: The attacker attempts to escalate privileges to gain higher-level access to the system.
- Impact: The attacker achieves their objective, such as stealing sensitive data or disrupting system operations.
Impact
A successful attack resulting in multiple EDR alerts can lead to significant disruption and data loss. Depending on the attacker’s objectives, this could include the exfiltration of sensitive data, ransomware deployment, or system downtime. The compromise of multiple hosts can indicate a widespread and coordinated attack, potentially affecting a large number of users and systems. Organizations may experience financial losses due to incident response costs, legal liabilities, and reputational damage.
Recommendation
- Deploy the Sigma rule
Multiple External EDR Alerts by Hostto your SIEM and tune for your environment. - Enable logging for CrowdStrike, SentinelOne, and M365 Defender to ensure the Sigma rule can ingest the appropriate logs, as outlined in the rule’s query.
- Prioritize investigation of hosts identified by the rule with high alert counts or diverse alert severities to minimize potential damage.
- Review and exclude known benign activities from triggering the rule, as detailed in the false positive analysis section of the rule documentation.
- Correlate alert data with other logs (process creation, network connections, file modifications) to provide better context for detected hosts.
- Block the C2 domains/IP addresses if they are found to be related to the alerts from the affected hosts.
Detection coverage 3
Multiple External EDR Alerts by Host
highDetects hosts with multiple alerts from external EDR solutions, indicating a potential compromise.
Suspicious Process Executables Triggering EDR Alerts
mediumIdentifies potentially malicious processes associated with EDR alerts.
EDR Alert Triggered by Network Connection to Known Bad IP
highDetects network connections to known malicious IPs that trigger EDR alerts.
Detection queries are kept inside the platform. Get full rules →