Attack Ent T1133 External Remote Services

MITRE ATT&CK T1133: External Remote Services

When to use this skill

Use this skill when the task involves T1133, External Remote Services, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.

Technique context

• ATT&CK domain: enterprise
• ATT&CK ID: T1133
• Technique name: External Remote Services
• Type: technique
• ATT&CK URL: https://attack.mitre.org/techniques/T1133
• Tactics: initial-access, persistence
• Platforms: Containers, Linux, macOS, Windows
• Required permissions: Not specified
• Effective permissions: Not specified
• Defenses bypassed: Not specified

ATT&CK description

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 and VNC can also be used externally.(Citation: MacOS VNC software for Remote Desktop)

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.(Citation: Volexity Virtual Private Keylogging) Access to remote services may be used as a redundant or persistent access mechanism during an operation.

Access may also be gained through an exposed service that doesn’t require authentication. In containerized environments, this may include an exposed Docker API, Kubernetes API server, kubelet, or web application such as the Kubernetes dashboard.(Citation: Trend Micro Exposed Docker Server)(Citation: Unit 42 Hildegard Malware)

Adversaries may also establish persistence on network by configuring a Tor hidden service on a compromised system. Adversaries may utilize the tool ShadowLink to facilitate the installation and configuration of the Tor hidden service. Tor hidden service is then accessible via the Tor network because ShadowLink sets up a .onion address on the compromised system. ShadowLink may be used to forward any inbound connections to RDP, allowing the adversaries to have remote access.(Citation: The BadPilot campaign) Adversaries may get ShadowLink to persist on a system by masquerading it as an MS Defender application.(Citation: Russian threat actors dig in, prepare to seize on war fatigue)

Agent workflow

1. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.
2. Load bundled resources as needed: use references/technique-profile.json for structured metadata, references/detection-and-mitigation.md for triage and telemetry guidance, references/known-threat-context.md for ATT&CK relationship context, and templates/ for repeatable outputs.
3. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.
4. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
5. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
6. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.

Bundled resources

• references/technique-profile.json: machine-readable ATT&CK metadata for this technique.
• references/detection-and-mitigation.md: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.
• references/known-threat-context.md: ATT&CK relationship context with attribution cautions.
• templates/detection-brief.md: detection engineering brief template.
• templates/hunt-plan.md: threat hunt plan template.
• templates/incident-response-note.md: incident response note template.
• templates/coverage-assessment.md: ATT&CK coverage assessment template.
• scripts/render_brief.py: local helper that renders a Markdown defensive brief from technique-profile.json.
• assets/output-schema.json: JSON schema for structured technique analysis outputs.

To generate a quick brief, run python scripts/render_brief.py --output brief.md from inside this skill directory, or adapt the templates directly.

Detection guidance

No ATT&CK detection guidance was present in the source STIX object.

Useful telemetry and data sources

• Not specified in the STIX object.

Mitigations to consider

• Disable or Remove Feature or Program
• Limit Access to Resource Over Network
• Multi-factor Authentication
• Network Segmentation
• Restrict Web-Based Content

Known threat context

Use these examples only as contextual leads, not as proof that an observed event is this technique:

• 2015 Ukraine Electric Power Attack (campaign)
• 2025 Poland Wiper Attacks (campaign)
• APT-C-36 (intrusion-set)
• APT18 (intrusion-set)
• APT28 (intrusion-set)
• APT29 (intrusion-set)
• APT41 (intrusion-set)
• Akira (intrusion-set)
• ArcaneDoor (campaign)
• C0027 (campaign)
• C0032 (campaign)
• Chimera (intrusion-set)
• CostaRicto (campaign)
• Doki (malware)
• Dragonfly (intrusion-set)
• Ember Bear (intrusion-set)
• FIN13 (intrusion-set)
• FIN5 (intrusion-set)
• GALLIUM (intrusion-set)
• GOLD SOUTHFIELD (intrusion-set)

Recommended output pattern

When responding with this skill, structure the answer as:

• Assessment: whether the evidence supports this ATT&CK mapping and why.
• Evidence: specific indicators, logs, behaviors, and assumptions.
• Detection: telemetry sources, analytic logic, and tuning considerations.
• Response: containment, eradication, recovery, and validation actions.
• Coverage gaps: missing logs, sensors, controls, or environmental details.
• References: include the ATT&CK URL and any user-provided evidence references.

ATT&CK contributors

• ExtraHop
• David Fiser, @anu4is, Trend Micro
• Alfredo Oliveira, Trend Micro
• Idan Frimark, Cisco
• Rory McCune, Aqua Security
• Yuval Avrahami, Palo Alto Networks
• Jay Chen, Palo Alto Networks
• Brad Geesaman, @bradgeesaman
• Magno Logan, @magnologan, Trend Micro
• Ariel Shuper, Cisco
• Yossi Weizman, Azure Defender Research Team
• Vishwas Manral, McAfee
• Daniel Oakley
• Travis Smith, Tripwire
• David Tayouri
• Liran Ravich, CardinalOps