Passwordless Sudo Probing
This rule detects passwordless sudo probing activity on Linux systems. Passwordless sudo probing can be an indication of an attacker attempting to enumerate it's allowed commands and potential privilege escalation.
Elastic rule (View on GitHub)
1[metadata]
2creation_date = "2026/05/21"
3integration = ["endpoint", "crowdstrike", "sentinel_one_cloud_funnel", "auditd_manager"]
4maturity = "production"
5updated_date = "2026/05/21"
6
7[rule]
8author = ["Elastic"]
9description = """
10This rule detects passwordless sudo probing activity on Linux systems. Passwordless sudo probing
11can be an indication of an attacker attempting to enumerate it's allowed commands and potential
12privilege escalation.
13"""
14from = "now-9m"
15index = [
16 "auditbeat-*",
17 "endgame-*",
18 "logs-auditd_manager.auditd-*",
19 "logs-crowdstrike.fdr*",
20 "logs-endpoint.events.process*",
21 "logs-sentinel_one_cloud_funnel.*",
22]
23language = "eql"
24license = "Elastic License v2"
25name = "Passwordless Sudo Probing"
26references = [
27 "https://github.com/nrwl/nx-console/issues/3139",
28]
29risk_score = 21
30rule_id = "92b11a06-57ab-4f6d-a18b-fb7fdf3cc63f"
31severity = "low"
32setup = """## Setup
33
34This rule requires data coming in from Elastic Defend.
35
36### Elastic Defend Integration Setup
37Elastic 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.
38
39#### Prerequisite Requirements:
40- Fleet is required for Elastic Defend.
41- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
42
43#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:
44- Go to the Kibana home page and click "Add integrations".
45- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
46- Click "Add Elastic Defend".
47- Configure the integration name and optionally add a description.
48- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
49- 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).
50- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
51- 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.
52For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).
53- Click "Save and Continue".
54- 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.
55For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
56"""
57tags = [
58 "Domain: Endpoint",
59 "OS: Linux",
60 "Use Case: Threat Detection",
61 "Tactic: Discovery",
62 "Data Source: Elastic Endgame",
63 "Data Source: Elastic Defend",
64 "Data Source: Auditd Manager",
65 "Data Source: Crowdstrike",
66 "Data Source: SentinelOne",
67]
68timestamp_override = "event.ingested"
69type = "eql"
70query = '''
71process where host.os.type == "linux" and event.type == "start" and
72event.action in ("exec", "exec_event", "start", "ProcessRollup2", "executed", "process_started") and
73process.name == "sudo" and process.args in ("-n", "--non-interactive") and process.args == "true"
74'''
75
76[[rule.threat]]
77framework = "MITRE ATT&CK"
78
79[[rule.threat.technique]]
80id = "T1033"
81name = "System Owner/User Discovery"
82reference = "https://attack.mitre.org/techniques/T1033/"
83
84[[rule.threat.technique]]
85id = "T1082"
86name = "System Information Discovery"
87reference = "https://attack.mitre.org/techniques/T1082/"
88
89[rule.threat.tactic]
90id = "TA0007"
91name = "Discovery"
92reference = "https://attack.mitre.org/tactics/TA0007/"
References
Related rules
- Kubectl Secrets Enumeration Across All Namespaces
- Docker Socket Enumeration
- ESXI Discovery via Find
- ESXI Discovery via Grep
- Hping Process Activity