|
| 1 | +[metadata] |
| 2 | +creation_date = "2025/12/10" |
| 3 | +integration = ["endpoint", "suricata"] |
| 4 | +maturity = "production" |
| 5 | +updated_date = "2025/12/10" |
| 6 | + |
| 7 | +[rule] |
| 8 | +author = ["Elastic"] |
| 9 | +description = """ |
| 10 | +This detection correlates Suricata alerts and events with Elastic Defend network events to identify the source process |
| 11 | +performing the network activity. |
| 12 | +""" |
| 13 | +from = "now-9m" |
| 14 | +index = ["logs-endpoint.events.network-*", "logs-panw.panos-*"] |
| 15 | +language = "eql" |
| 16 | +license = "Elastic License v2" |
| 17 | +name = "Suricata and Elastic Defend - Command and Control Correlation" |
| 18 | +references = [ |
| 19 | + "https://attack.mitre.org/tactics/TA0011/", |
| 20 | + "https://www.elastic.co/docs/reference/integrations/panw", |
| 21 | + "https://www.elastic.co/docs/reference/integrations/endpoint" |
| 22 | +] |
| 23 | +risk_score = 47 |
| 24 | +rule_id = "9edd000e-cbd1-4d6a-be72-2197b5625a05" |
| 25 | +severity = "medium" |
| 26 | +tags = [ |
| 27 | + "Domain: Endpoint", |
| 28 | + "OS: Linux", |
| 29 | + "OS: Windows", |
| 30 | + "OS: macOS", |
| 31 | + "Use Case: Threat Detection", |
| 32 | + "Tactic: Command and Control", |
| 33 | + "Data Source: Elastic Defend", |
| 34 | + "Data Source: Suricata", |
| 35 | + "Resources: Investigation Guide", |
| 36 | +] |
| 37 | +type = "eql" |
| 38 | +query = ''' |
| 39 | +sequence by source.port, source.ip, destination.ip with maxspan=1m |
| 40 | + [network where event.module == "suricata" and source.ip != nulll and destination.ip != null and |
| 41 | + message in ("Command and Control Traffic", "Potentially Bad Traffic", "A Network Trojan was detected", "Detection of a Network Scan", |
| 42 | + "Domain Observed Used for C2 Detected", "Malware Command and Control Activity Detected", "Misc Attack", |
| 43 | + "Device Retrieving External IP Address Detected", "Attempted Information Leak", "Web Application Attack", |
| 44 | + "SQL Injection Attempt", "Attempted User Privilege Gain", "Attempted Administrator Privilege Gain", |
| 45 | + "Executable code was detected", "Webshell Tool Traffic", "Possibly Unwanted Program Detected", "A system call was detected", |
| 46 | + "Unknown Traffic", "Crypto Currency Mining Activity Detected", "Possible Social Engineering Attempted")] |
| 47 | + [network where event.module == "endpoint" and event.action in ("disconnect_received", "connection_attempted")] |
| 48 | +''' |
| 49 | +note = """## Triage and analysis |
| 50 | +
|
| 51 | +### Investigating Suricata and Elastic Defend - Command and Control Correlation |
| 52 | +
|
| 53 | +### Possible investigation steps |
| 54 | +
|
| 55 | +- Investigate in the Timeline feature the two events matching this correlation (Suricata and Elastic Defend). |
| 56 | +- Review the process details like command_line, privileges, global relevance and reputation. |
| 57 | +- Assess the destination.ip reputation and global relevance. |
| 58 | +- Review the parent process execution details like command_line, global relevance and reputation. |
| 59 | +- Examine all network connection details performed by the process during last 48h. |
| 60 | +- Correlate the alert with other security events or logs to identify any patterns or additional indicators of compromise related to the same process or network activity. |
| 61 | +
|
| 62 | +### False positive analysis |
| 63 | +
|
| 64 | +- Trusted system or third party processes performing network activity that looks like beaconing. |
| 65 | +
|
| 66 | +### Response and remediation |
| 67 | +
|
| 68 | +- Immediately isolate the affected system from the network to prevent further unauthorized access or data exfiltration. |
| 69 | +- Terminate the suspicious processes and all associated children and parents. |
| 70 | +- Implement network-level controls to block traffic to the destination.ip. |
| 71 | +- Conduct a thorough review of the system's configuration files to identify unauthorized changes. |
| 72 | +- Reset credentials for any accounts associated with the source machine. |
| 73 | +- Escalate the incident to the security operations center (SOC) or incident response team for further investigation and to determine if additional systems are affected. |
| 74 | +""" |
| 75 | + |
| 76 | +[[rule.threat]] |
| 77 | +framework = "MITRE ATT&CK" |
| 78 | + |
| 79 | +[rule.threat.tactic] |
| 80 | +id = "TA0011" |
| 81 | +name = "Command and Control" |
| 82 | +reference = "https://attack.mitre.org/tactics/TA0011/" |
0 commit comments