RDP Enabled via Registry

  1[metadata]
  2creation_date = "2020/11/25"
  3integration = ["endpoint", "windows"]
  4maturity = "production"
  5min_stack_comments = "New fields added: required_fields, related_integrations, setup"
  6min_stack_version = "8.3.0"
  7updated_date = "2024/03/28"
  8
  9[rule]
 10author = ["Elastic"]
 11description = """
 12Identifies registry write modifications to enable Remote Desktop Protocol (RDP) access. This could be indicative of
 13adversary lateral movement preparation.
 14"""
 15from = "now-9m"
 16index = ["logs-endpoint.events.registry-*", "winlogbeat-*", "logs-windows.sysmon_operational-*", "endgame-*"]
 17language = "eql"
 18license = "Elastic License v2"
 19name = "RDP Enabled via Registry"
 20note = """## Triage and analysis
 21
 22### Investigating RDP Enabled via Registry
 23
 24Microsoft Remote Desktop Protocol (RDP) is a proprietary Microsoft protocol that enables remote connections to other computers, typically over TCP port 3389.
 25
 26Attackers can use RDP to conduct their actions interactively. Ransomware operators frequently use RDP to access victim servers, often using privileged accounts.
 27
 28This rule detects modification of the fDenyTSConnections registry key to the value `0`, which specifies that remote desktop connections are enabled. Attackers can abuse remote registry, use psexec, etc., to enable RDP and move laterally.
 29
 30#### Possible investigation steps
 31
 32- Identify the user account that performed the action and whether it should perform this kind of action.
 33- Contact the user to check if they are aware of the operation.
 34- Investigate the process execution chain (parent process tree) for unknown processes. Examine their executable files for prevalence, whether they are located in expected locations, and if they are signed with valid digital signatures.
 35- Investigate other alerts associated with the user/host during the past 48 hours.
 36- Check whether it makes sense to enable RDP to this host, given its role in the environment.
 37- Check if the host is directly exposed to the internet.
 38- Check whether privileged accounts accessed the host shortly after the modification.
 39- Review network events within a short timespan of this alert for incoming RDP connection attempts.
 40
 41### False positive analysis
 42
 43- This mechanism can be used legitimately. Check whether the user should be performing this kind of activity, whether they are aware of it, whether RDP should be open, and whether the action exposes the environment to unnecessary risks.
 44
 45### Response and remediation
 46
 47- Initiate the incident response process based on the outcome of the triage.
 48- If RDP is needed, make sure to secure it using firewall rules:
 49  - Allowlist RDP traffic to specific trusted hosts.
 50  - Restrict RDP logins to authorized non-administrator accounts, where possible.
 51- Isolate the involved hosts to prevent further post-compromise behavior.
 52- Review the privileges assigned to the involved users to ensure that the least privilege principle is being followed.
 53- Determine the initial vector abused by the attacker and take action to prevent reinfection through the same vector.
 54- Using the incident response data, update logging and audit policies to improve the mean time to detect (MTTD) and the mean time to respond (MTTR).
 55"""
 56risk_score = 47
 57rule_id = "58aa72ca-d968-4f34-b9f7-bea51d75eb50"
 58setup = """## Setup
 59
 60If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
 61events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
 62Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
 63`event.ingested` to @timestamp.
 64For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
 65"""
 66severity = "medium"
 67tags = ["Domain: Endpoint", "OS: Windows", "Use Case: Threat Detection", "Tactic: Lateral Movement", "Tactic: Defense Evasion", "Resources: Investigation Guide", "Data Source: Elastic Endgame", "Data Source: Elastic Defend", "Data Source: Sysmon"]
 68timestamp_override = "event.ingested"
 69type = "eql"
 70
 71query = '''
 72registry where host.os.type == "windows" and 
 73 event.type in ("creation", "change") and
 74  registry.path : "HKLM\\SYSTEM\\*ControlSet*\\Control\\Terminal Server\\fDenyTSConnections" and
 75  registry.data.strings : ("0", "0x00000000") and
 76  not process.executable : ("?:\\Windows\\System32\\SystemPropertiesRemote.exe", 
 77                            "?:\\Windows\\System32\\SystemPropertiesComputerName.exe", 
 78                            "?:\\Windows\\System32\\SystemPropertiesAdvanced.exe", 
 79                            "?:\\Windows\\System32\\SystemSettingsAdminFlows.exe", 
 80                            "?:\\Windows\\WinSxS\\*\\TiWorker.exe", 
 81                            "?:\\Windows\\system32\\svchost.exe")
 82'''
 83
 84
 85[[rule.threat]]
 86framework = "MITRE ATT&CK"
 87[[rule.threat.technique]]
 88id = "T1021"
 89name = "Remote Services"
 90reference = "https://attack.mitre.org/techniques/T1021/"
 91[[rule.threat.technique.subtechnique]]
 92id = "T1021.001"
 93name = "Remote Desktop Protocol"
 94reference = "https://attack.mitre.org/techniques/T1021/001/"
 95
 96
 97
 98[rule.threat.tactic]
 99id = "TA0008"
100name = "Lateral Movement"
101reference = "https://attack.mitre.org/tactics/TA0008/"
102
103
104
105[[rule.threat]]
106framework = "MITRE ATT&CK"
107[[rule.threat.technique]]
108id = "T1112"
109name = "Modify Registry"
110reference = "https://attack.mitre.org/techniques/T1112/"
111
112[rule.threat.tactic]
113id = "TA0005"
114name = "Defense Evasion"
115reference = "https://attack.mitre.org/tactics/TA0005/"