|T1021.001||Remote Desktop Protocol|
|T1021.002||SMB/Windows Admin Shares|
|T1021.003||Distributed Component Object Model|
|T1021.006||Windows Remote Management|
Adversaries may use Valid Accounts to log into a computer using the Remote Desktop Protocol (RDP). The adversary may then perform actions as the logged-on user.
Remote desktop is a common feature in operating systems. It allows a user to log into an interactive session with a system desktop graphical user interface on a remote system. Microsoft refers to its implementation of the Remote Desktop Protocol (RDP) as Remote Desktop Services (RDS).
Adversaries may connect to a remote system over RDP/RDS to expand access if the service is enabled and allows access to accounts with known credentials. Adversaries will likely use Credential Access techniques to acquire credentials to use with RDP. Adversaries may also use RDP in conjunction with the Accessibility Features or Terminal Services DLL for Persistence.
The APT1 group is known to have used RDP during operations.
APT3 enables the Remote Desktop Protocol for persistence. APT3 has also interacted with compromised systems to browse and copy files through RDP sessions.
APT39 has been seen using RDP for lateral movement and persistence, in some cases employing the rdpwinst tool for mangement of multiple sessions.
Blue Mockingbird has used Remote Desktop to log on to servers interactively and manually copy files to remote hosts.
During C0015, the threat actors used RDP to access specific network hosts of interest.
During C0018, the threat actors opened a variety of ports to establish RDP connections, including ports 28035, 32467, 41578, and 46892.
Carbanak enables concurrent Remote Desktop Protocol (RDP) sessions.
Cobalt Group has used Remote Desktop Protocol to conduct lateral movement.
Cobalt Strike can start a VNC-based remote desktop server and tunnel the connection through the already established C2 channel.
DarkComet can open an active screen of the victim’s machine and take control of the mouse and keyboard.
FIN10 has used RDP to move laterally to systems in the victim environment.
FIN7 has used RDP to move laterally in victim environments.
Fox Kitten has used RDP to log in and move laterally in the target environment.
HEXANE has used remote desktop sessions for lateral movement.
Imminent Monitor has a module for performing remote desktop access.
Kimsuky has used RDP for direct remote point-and-click access.
Koadic can enable remote desktop on the victim's machine.
Lazarus Group malware SierraCharlie uses RDP for propagation.
Leviathan has targeted RDP credentials and used it to move through the victim environment.
Magic Hound has used Remote Desktop Services to copy tools on targeted systems.
menuPass has used RDP connections to move across the victim network.
njRAT has a module for performing remote desktop access.
OilRig has used Remote Desktop Protocol for lateral movement. The group has also used tunneling tools to tunnel RDP into the environment.
Pupy can enable/disable RDP connection and can start a remote desktop session using a browser web socket client.
QuasarRAT has a module for performing remote desktop access.
Revenge RAT has a plugin to perform RDP access.
SDBbot has the ability to use RDP to connect to victim's machines.
ServHelper has commands for adding a remote desktop user and sending RDP traffic to the attacker through a reverse SSH tunnel.
During the SolarWinds Compromise, APT29 used RDP sessions from public-facing systems to internal servers.
TEMP.Veles utilized RDP throughout an operation.
WarzoneRAT has the ability to control an infected PC using RDP.
Wizard Spider has used RDP for lateral movement.
Audit the Remote Desktop Users group membership regularly. Remove unnecessary accounts and groups from Remote Desktop Users groups.
|M1042||Disable or Remove Feature or Program||
Disable the RDP service if it is unnecessary.
|M1035||Limit Access to Resource Over Network||
Use remote desktop gateways.
Use multi-factor authentication for remote logins.
Do not leave RDP accessible from the internet. Enable firewall rules to block RDP traffic between network security zones within a network.
|M1028||Operating System Configuration||
Change GPOs to define shorter timeouts sessions and maximum amount of time any single session can be active. Change GPOs to specify the maximum amount of time that a disconnected session stays active on the RD session host server.
|M1026||Privileged Account Management||
Consider removing the local Administrators group from the list of groups allowed to log in through RDP.
|M1018||User Account Management||
Limit remote user permissions if remote access is necessary.
|ID||Data Source||Data Component||Detects|
|DS0028||Logon Session||Logon Session Creation||
Monitor for user accounts logged into systems associated with RDP (ex: Windows EID 4624 Logon Type 10). Other factors, such as access patterns (ex: multiple systems over a relatively short period of time) and activity that occurs after a remote login, may indicate suspicious or malicious behavior with RDP.
|DS0029||Network Traffic||Network Connection Creation||
Monitor for newly constructed network connections (typically over port 3389) that may use Valid Accounts to log into a computer using the Remote Desktop Protocol (RDP). The adversary may then perform actions as the logged-on user. Other factors, such as access patterns and activity that occurs after a remote login, may indicate suspicious or malicious behavior with RDP.
|Network Traffic Flow||
Monitor network traffic for uncommon data flows that may use Valid Accounts to log into a computer using the Remote Desktop Protocol (RDP).
Monitor for newly executed processes (such as