Potential Successful Linux RDP Brute Force Attack Detected

 1[metadata]
 2creation_date = "2023/07/06"
 3integration = ["auditd_manager"]
 4maturity = "production"
 5updated_date = "2024/05/21"
 6
 7[rule]
 8author = ["Elastic"]
 9description = """
10An RDP (Remote Desktop Protocol) brute force attack involves an attacker repeatedly attempting various username and
11password combinations to gain unauthorized access to a remote computer via RDP, and if successful, the potential impact
12can include unauthorized control over the compromised system, data theft, or the ability to launch further attacks
13within the network, jeopardizing the security and confidentiality of the targeted system and potentially compromising
14the entire network infrastructure. This rule identifies multiple consecutive authentication failures targeting a
15specific user account within a short time interval, followed by a successful authentication.
16"""
17from = "now-9m"
18index = ["auditbeat-*", "logs-auditd_manager.auditd-*"]
19language = "eql"
20license = "Elastic License v2"
21name = "Potential Successful Linux RDP Brute Force Attack Detected"
22risk_score = 47
23rule_id = "521fbe5c-a78d-4b6b-a323-f978b0e4c4c0"
24setup = """## Setup
25
26This rule requires data coming in from one of the following integrations:
27- Auditbeat
28- Auditd Manager
29
30### Auditbeat Setup
31Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
32
33#### The following steps should be executed in order to add the Auditbeat on a Linux System:
34- Elastic provides repositories available for APT and YUM-based distributions. Note that we provide binary packages, but no source packages.
35- To install the APT and YUM repositories follow the setup instructions in this [helper guide](https://www.elastic.co/guide/en/beats/auditbeat/current/setup-repositories.html).
36- To run Auditbeat on Docker follow the setup instructions in the [helper guide](https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-docker.html).
37- To run Auditbeat on Kubernetes follow the setup instructions in the [helper guide](https://www.elastic.co/guide/en/beats/auditbeat/current/running-on-kubernetes.html).
38- For complete “Setup and Run Auditbeat” information refer to the [helper guide](https://www.elastic.co/guide/en/beats/auditbeat/current/setting-up-and-running.html).
39
40### Auditd Manager Integration Setup
41The Auditd Manager Integration receives audit events from the Linux Audit Framework which is a part of the Linux kernel.
42Auditd Manager provides a user-friendly interface and automation capabilities for configuring and monitoring system auditing through the auditd daemon. With `auditd_manager`, administrators can easily define audit rules, track system events, and generate comprehensive audit reports, improving overall security and compliance in the system.
43
44#### The following steps should be executed in order to add the Elastic Agent System integration "auditd_manager" on a Linux System:
45- Go to the Kibana home page and click “Add integrations”.
46- In the query bar, search for “Auditd Manager” and select the integration to see more details about it.
47- Click “Add Auditd Manager”.
48- Configure the integration name and optionally add a description.
49- Review optional and advanced settings accordingly.
50- Add the newly installed “auditd manager” to an existing or a new agent policy, and deploy the agent on a Linux system from which auditd log files are desirable.
51- Click “Save and Continue”.
52- For more details on the integration refer to the [helper guide](https://docs.elastic.co/integrations/auditd_manager).
53
54#### Rule Specific Setup Note
55Auditd Manager subscribes to the kernel and receives events as they occur without any additional configuration.
56However, if more advanced configuration is required to detect specific behavior, audit rules can be added to the integration in either the "audit rules" configuration box or the "auditd rule files" box by specifying a file to read the audit rules from.
57- For this detection rule no additional audit rules are required to be added to the integration.
58"""
59severity = "medium"
60tags = [
61    "Data Source: Auditd Manager",
62    "Domain: Endpoint",
63    "OS: Linux",
64    "Use Case: Threat Detection",
65    "Tactic: Credential Access",
66]
67type = "eql"
68
69query = '''
70sequence by host.id, related.user with maxspan=5s
71  [authentication where host.os.type == "linux" and event.action == "authenticated" and
72   auditd.data.terminal : "*rdp*" and event.outcome == "failure"] with runs=10
73  [authentication where host.os.type == "linux" and event.action  == "authenticated" and
74   auditd.data.terminal : "*rdp*" and event.outcome == "success"] | tail 1
75'''
76
77
78[[rule.threat]]
79framework = "MITRE ATT&CK"
80[[rule.threat.technique]]
81id = "T1110"
82name = "Brute Force"
83reference = "https://attack.mitre.org/techniques/T1110/"
84[[rule.threat.technique.subtechnique]]
85id = "T1110.001"
86name = "Password Guessing"
87reference = "https://attack.mitre.org/techniques/T1110/001/"
88
89[[rule.threat.technique.subtechnique]]
90id = "T1110.003"
91name = "Password Spraying"
92reference = "https://attack.mitre.org/techniques/T1110/003/"
93
94
95
96[rule.threat.tactic]
97id = "TA0006"
98name = "Credential Access"
99reference = "https://attack.mitre.org/tactics/TA0006/"