RDP Enabled via Registryedit

Identifies registry write modifications to enable Remote Desktop Protocol (RDP) access. This could be indicative of adversary lateral movement preparation.

Rule type: eql

Rule indices:

  • logs-endpoint.events.*
  • winlogbeat-*
  • logs-windows.*

Severity: medium

Risk score: 47

Runs every: 5 minutes

Searches indices from: now-9m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100

Tags:

  • Elastic
  • Host
  • Windows
  • Threat Detection
  • Lateral Movement

Version: 5 (version history)

Added (Elastic Stack release): 7.11.0

Last modified (Elastic Stack release): 8.1.0

Rule authors: Elastic

Rule license: Elastic License v2

Rule queryedit

registry where event.type in ("creation", "change") and
registry.path : "HKLM\\SYSTEM\\*ControlSet*\\Control\\Terminal
Server\\fDenyTSConnections" and registry.data.strings : ("0",
"0x00000000") and not (process.name : "svchost.exe" and user.domain ==
"NT AUTHORITY") and not process.executable :
"C:\\Windows\\System32\\SystemPropertiesRemote.exe"

Threat mappingedit

Framework: MITRE ATT&CKTM

Rule version historyedit

Version 5 (8.1.0 release)
  • Updated query, changed from:

    registry where registry.path :
    "HKLM\\SYSTEM\\ControlSet*\\Control\\Terminal
    Server\\fDenyTSConnections" and registry.data.strings == "0" and not
    (process.name : "svchost.exe" and user.domain == "NT AUTHORITY") and
    not process.executable :
    "C:\\Windows\\System32\\SystemPropertiesRemote.exe"
Version 4 (7.16.0 release)
  • Formatting only
Version 3 (7.12.0 release)
  • Formatting only
Version 2 (7.11.2 release)
  • Formatting only