Currently viewing ATT&CK v7.2 which was live between July 8, 2020 and October 26, 2020. Learn more about the versioning system or see the live site.
Register to stream the next session of ATT&CKcon Power Hour November 12

External Remote Services

Adversaries may leverage external-facing remote services to initially access and/or persist within a network. Remote services such as VPNs, Citrix, and other access mechanisms allow users to connect to internal enterprise network resources from external locations. There are often remote service gateways that manage connections and credential authentication for these services. Services such as Windows Remote Management can also be used externally.

Access to Valid Accounts to use the service is often a requirement, which could be obtained through credential pharming or by obtaining the credentials from users after compromising the enterprise network.[1] Access to remote services may be used as a redundant or persistent access mechanism during an operation.

ID: T1133
Sub-techniques:  No sub-techniques
Tactics: Persistence, Initial Access
Platforms: Linux, Windows
Permissions Required: User
Data Sources: Authentication logs
CAPEC ID: CAPEC-555
Contributors: Daniel Oakley; Travis Smith, Tripwire
Version: 2.1
Created: 31 May 2017
Last Modified: 19 June 2020

Procedure Examples

Name Description
APT18

APT18 actors leverage legitimate credentials to log into external remote services.[3]

APT41

APT41 compromised an online billing/payment service using VPN access between a third-party service provider and the targeted payment service.[16]

Dragonfly 2.0

Dragonfly 2.0 used VPNs and Outlook Web Access (OWA) to maintain access to victim networks.[8][9]

FIN5

FIN5 has used legitimate VPN, Citrix, or VNC credentials to maintain access to a victim environment.[10][11][12]

Ke3chang

Ke3chang regained access after eviction via the corporate VPN solution with a stolen VPN certificate, which they had extracted from a compromised host.[7]

Linux Rabbit

Linux Rabbit attempts to gain access to the server via SSH.[2]

Night Dragon

Night Dragon has used compromised VPN accounts to gain access to victim systems.[13]

OilRig

OilRig uses remote services such as VPN, Citrix, or OWA to persist in an environment.[4]

Sandworm Team

Sandworm Team has used Dropbear SSH with a hardcoded backdoor password to maintain persistence within the target network. Sandworm Team has also used VPN tunnels established in legitimate software company infrastructure to gain access to internal networks of that software company's users.[17][18]

Soft Cell

Soft Cell established VPN access into victim environments.[15]

TEMP.Veles

TEMP.Veles has used a VPN to persist in the victim environment.[14]

Threat Group-3390

Threat Group-3390 actors look for and use VPN profiles during an operation to access the network using external VPN services.[5] Threat Group-3390 has also obtained OWA account credentials during intrusions that it subsequently used to attempt to regain access when evicted from a victim network.[6]

Mitigations

Mitigation Description
Disable or Remove Feature or Program

Disable or block remotely available services that may be unnecessary.

Limit Access to Resource Over Network

Limit access to remote services through centrally managed concentrators such as VPNs and other managed remote access systems.

Multi-factor Authentication

Use strong two-factor or multi-factor authentication for remote service accounts to mitigate an adversary's ability to leverage stolen credentials, but be aware of Two-Factor Authentication Interception techniques for some two-factor authentication implementations.

Network Segmentation

Deny direct remote access to internal systems through the use of network proxies, gateways, and firewalls.

Detection

Follow best practices for detecting adversary use of Valid Accounts for authenticating to remote services. Collect authentication logs and analyze for unusual access patterns, windows of activity, and access outside of normal business hours.

References