Files
sigma-rules/rules/ml/ml_linux_anomalous_network_activity.toml
T
Ross Wolf 5fcece8416 Populate rules/ directory.
Co-Authored-By: Brent Murphy <56412096+bm11100@users.noreply.github.com>
Co-Authored-By: Craig Chamberlain <randomuserid@users.noreply.github.com>
Co-Authored-By: David French <56409778+threat-punter@users.noreply.github.com>
Co-Authored-By: Derek Ditch <dcode@users.noreply.github.com>
Co-Authored-By: Justin Ibarra <brokensound77@users.noreply.github.com>
2020-06-29 22:57:03 -06:00

37 lines
2.3 KiB
TOML

[metadata]
creation_date = "2020/03/25"
ecs_version = ["1.5.0"]
maturity = "production"
updated_date = "2020/03/25"
[rule]
anomaly_threshold = 50
author = ["Elastic"]
description = """
Identifies Linux processes that do not usually use the network but have unexpected network activity, which can indicate
command-and-control, lateral movement, persistence, or data exfiltration activity. A process with unusual network
activity can denote process exploitation or injection, where the process is used to run persistence mechanisms that
allow a malicious actor remote access or control of the host, data exfiltration, and execution of unauthorized network
applications.
"""
false_positives = ["A newly installed program or one that rarely uses the network could trigger this signal."]
from = "now-45m"
interval = "15m"
license = "Elastic License"
machine_learning_job_id = "linux_anomalous_network_activity_ecs"
name = "Unusual Linux Network Activity"
note = """### Investigating Unusual Network Activity ###
Signals from this rule indicate the presence of network activity from a Linux process for which network activity is rare and unusual. Here are some possible avenues of investigation:
- Consider the IP addresses and ports. Are these used by normal but infrequent network workflows? Are they expected or unexpected?
- If the destination IP address is remote or external, does it associate with an expected domain, organization or geography? Note: avoid interacting directly with suspected malicious IP addresses.
- Consider the user as identified by the username field. Is this network activity part of an expected workflow for the user who ran the program?
- Examine the history of execution. If this process manifested only very recently, it might be part of a new software package. If it has a consistent cadence - for example if it runs monthly or quarterly - it might be part of a monthly or quarterly business or maintenance process.
- Examine the process arguments, title and working directory. These may provide indications as to the source of the program or the nature of the tasks it is performing."""
references = ["https://www.elastic.co/guide/en/siem/guide/current/prebuilt-ml-jobs.html"]
risk_score = 21
rule_id = "52afbdc5-db15-485e-bc24-f5707f820c4b"
severity = "low"
tags = ["Elastic", "Linux", "ML"]
type = "machine_learning"