Process Capability Enumeration

Identifies recursive process capability enumeration of the entire filesystem through the getcap command. Malicious users may manipulate identified capabilities to gain root privileges.

Elastic rule (View on GitHub)

 1[metadata]
 2creation_date = "2024/01/09"
 3integration = ["endpoint"]
 4maturity = "production"
 5min_stack_comments = "Linux effective and permitted process capability data sources were added in version 8.11.0"
 6min_stack_version = "8.11.0"
 7updated_date = "2024/01/09"
 8
 9[rule]
10author = ["Elastic"]
11description = """
12Identifies recursive process capability enumeration of the entire filesystem through the getcap command.
13Malicious users may manipulate identified capabilities to gain root privileges.
14"""
15from = "now-9m"
16index = ["logs-endpoint.events.*"]
17language = "eql"
18license = "Elastic License v2"
19name = "Process Capability Enumeration"
20risk_score = 21
21rule_id = "5c351f54-4187-4ad8-abc8-29b0cfbef8b1"
22setup = """
23
24This rule requires data coming in from Elastic Defend.
25
26### Elastic Defend Integration Setup
27Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
28
29#### Prerequisite Requirements:
30- Fleet is required for Elastic Defend.
31- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
32
33#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:
34- Go to the Kibana home page and click "Add integrations".
35- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
36- Click "Add Elastic Defend".
37- Configure the integration name and optionally add a description.
38- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
39- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. [Helper guide](https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html).
40- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
41- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
42For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).
43- Click "Save and Continue".
44- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
45For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
46
47"""
48severity = "low"
49tags = ["Domain: Endpoint", "OS: Linux", "Use Case: Threat Detection", "Tactic: Discovery", "Data Source: Elastic Defend"]
50timestamp_override = "event.ingested"
51type = "eql"
52query = '''
53process where host.os.type == "linux" and event.action == "exec" and event.type == "start" and
54process.name == "getcap" and process.args == "-r" and process.args == "/" and process.args_count == 3 and
55user.id != "0"
56'''
57
58[[rule.threat]]
59framework = "MITRE ATT&CK"
60
61[[rule.threat.technique]]
62id = "T1057"
63name = "Process Discovery"
64reference = "https://attack.mitre.org/techniques/T1057/"
65
66[rule.threat.tactic]
67id = "TA0007"
68name = "Discovery"
69reference = "https://attack.mitre.org/tactics/TA0007/"

Related rules

to-top