MITRE ATT&CK T1219: Remote Access Tools
When to use this skill
Use this skill when the task involves T1219, Remote Access Tools, 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: T1219
- Technique name: Remote Access Tools
- Type: technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1219
- Tactics: command-and-control
- Platforms: Linux, macOS, Windows
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
An adversary may use legitimate remote access tools to establish an interactive command and control channel within a network. Remote access tools create a session between two trusted hosts through a graphical interface, a command line interaction, a protocol tunnel via development or management software, or hardware-level access such as KVM (Keyboard, Video, Mouse) over IP solutions. Desktop support software (usually graphical interface) and remote management software (typically command line interface) allow a user to control a computer remotely as if they are a local user inheriting the user or software permissions. This software is commonly used for troubleshooting, software installation, and system management.(Citation: Symantec Living off the Land)(Citation: CrowdStrike 2015 Global Threat Report)(Citation: CrySyS Blog TeamSpy) Adversaries may similarly abuse response features included in EDR and other defensive tools that enable remote access.
Remote access tools may be installed and used post-compromise as an alternate communications channel for redundant access or to establish an interactive remote desktop session with the target system. It may also be used as a malware component to establish a reverse connection or back-connect to a service or adversary-controlled system.
Installation of many remote access tools may also include persistence (e.g., the software's installation routine creates a Windows Service). Remote access modules/features may also exist as part of otherwise existing software (e.g., Google Chrome’s Remote Desktop).(Citation: Google Chrome Remote Desktop)(Citation: Chrome Remote Desktop)
Agent workflow
- 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.
- 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.
- 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.
- Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
- Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
- 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
- Execution Prevention
- Filter Network Traffic
- Limit Hardware Installation
- Network Intrusion Prevention
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- Akira (intrusion-set)
- BlackByte (intrusion-set)
- Carbanak (intrusion-set)
- Carbanak (malware)
- Cobalt Group (intrusion-set)
- DarkVishnya (intrusion-set)
- Dridex (malware)
- Egregor (malware)
- FIN7 (intrusion-set)
- GOLD SOUTHFIELD (intrusion-set)
- Hildegard (malware)
- INC Ransom (intrusion-set)
- InvisibleFerret (malware)
- Medusa Group (intrusion-set)
- Night Dragon (campaign)
- OilRig (intrusion-set)
- Operation AkaiRyū (campaign)
- RTM (malware)
- Sandworm Team (intrusion-set)
- TeamTNT (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
- Matt Kelly, @breakersall
- Zachary Stanford, @svch0st
- Dray Agha, @Purp1eW0lf, Huntress Labs
1---2name: attack-ent-t1219-remote-access-tools3description: Analyze MITRE ATT&CK T1219 Remote Access Tools in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1219, Remote Access Tools, or enterprise ATT&CK. An adversary may use legitimate remote access tools to establish an interactive command and control channel within a network.4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See h5---67# MITRE ATT&CK T1219: Remote Access Tools89## When to use this skill1011Use this skill when the task involves T1219, Remote Access Tools, 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.1213## Technique context1415- ATT&CK domain: enterprise16- ATT&CK ID: T121917- Technique name: Remote Access Tools18- Type: technique19- ATT&CK URL: https://attack.mitre.org/techniques/T121920- Tactics: command-and-control21- Platforms: Linux, macOS, Windows22- Required permissions: Not specified23- Effective permissions: Not specified24- Defenses bypassed: Not specified2526## ATT&CK description2728An adversary may use legitimate remote access tools to establish an interactive command and control channel within a network. Remote access tools create a session between two trusted hosts through a graphical interface, a command line interaction, a protocol tunnel via development or management software, or hardware-level access such as KVM (Keyboard, Video, Mouse) over IP solutions. Desktop support software (usually graphical interface) and remote management software (typically command line interface) allow a user to control a computer remotely as if they are a local user inheriting the user or software permissions. This software is commonly used for troubleshooting, software installation, and system management.(Citation: Symantec Living off the Land)(Citation: CrowdStrike 2015 Global Threat Report)(Citation: CrySyS Blog TeamSpy) Adversaries may similarly abuse response features included in EDR and other defensive tools that enable remote access.2930Remote access tools may be installed and used post-compromise as an alternate communications channel for redundant access or to establish an interactive remote desktop session with the target system. It may also be used as a malware component to establish a reverse connection or back-connect to a service or adversary-controlled system.3132Installation of many remote access tools may also include persistence (e.g., the software's installation routine creates a [Windows Service](https://attack.mitre.org/techniques/T1543/003)). Remote access modules/features may also exist as part of otherwise existing software (e.g., Google Chrome’s Remote Desktop).(Citation: Google Chrome Remote Desktop)(Citation: Chrome Remote Desktop)3334## Agent workflow35361. 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.372. 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.383. 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.394. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.405. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.416. 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.4243## Bundled resources4445- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.46- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.47- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.48- `templates/detection-brief.md`: detection engineering brief template.49- `templates/hunt-plan.md`: threat hunt plan template.50- `templates/incident-response-note.md`: incident response note template.51- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.52- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.53- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.5455To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.5657## Detection guidance5859No ATT&CK detection guidance was present in the source STIX object.6061## Useful telemetry and data sources6263- Not specified in the STIX object.6465## Mitigations to consider6667- Disable or Remove Feature or Program68- Execution Prevention69- Filter Network Traffic70- Limit Hardware Installation71- Network Intrusion Prevention7273## Known threat context7475Use these examples only as contextual leads, not as proof that an observed event is this technique:7677- Akira (intrusion-set)78- BlackByte (intrusion-set)79- Carbanak (intrusion-set)80- Carbanak (malware)81- Cobalt Group (intrusion-set)82- DarkVishnya (intrusion-set)83- Dridex (malware)84- Egregor (malware)85- FIN7 (intrusion-set)86- GOLD SOUTHFIELD (intrusion-set)87- Hildegard (malware)88- INC Ransom (intrusion-set)89- InvisibleFerret (malware)90- Medusa Group (intrusion-set)91- Night Dragon (campaign)92- OilRig (intrusion-set)93- Operation AkaiRyū (campaign)94- RTM (malware)95- Sandworm Team (intrusion-set)96- TeamTNT (intrusion-set)9798## Recommended output pattern99100When responding with this skill, structure the answer as:101102- Assessment: whether the evidence supports this ATT&CK mapping and why.103- Evidence: specific indicators, logs, behaviors, and assumptions.104- Detection: telemetry sources, analytic logic, and tuning considerations.105- Response: containment, eradication, recovery, and validation actions.106- Coverage gaps: missing logs, sensors, controls, or environmental details.107- References: include the ATT&CK URL and any user-provided evidence references.108109## ATT&CK contributors110111- Matt Kelly, @breakersall112- Zachary Stanford, @svch0st113- Dray Agha, @Purp1eW0lf, Huntress Labs
santosomar