MITRE ATT&CK T1102.002: Bidirectional Communication
When to use this skill
Use this skill when the task involves T1102.002, Bidirectional Communication, 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 sub-technique.
Technique context
- ATT&CK domain: enterprise
- ATT&CK ID: T1102.002
- Technique name: Bidirectional Communication
- Type: sub-technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1102/002
- Tactics: command-and-control
- Platforms: ESXi, Linux, macOS, Windows
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may use an existing, legitimate external Web service as a means for sending commands to and receiving output from a compromised system over the Web service channel. Compromised systems may leverage popular websites and social media to host command and control (C2) instructions. Those infected systems can then send the output from those commands back over that Web service channel. The return traffic may occur in a variety of ways, depending on the Web service being utilized. For example, the return traffic may take the form of the compromised system posting a comment on a forum, issuing a pull request to development project, updating a document hosted on a Web service, or by sending a Tweet.
Popular websites and social media acting as a mechanism for C2 may give a significant amount of cover due to the likelihood that hosts within a network are already communicating with them prior to a compromise. Using common services, such as those offered by Google or Twitter, makes it easier for adversaries to hide in expected noise. Web service providers commonly use SSL/TLS encryption, giving adversaries an added level of protection.
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
- Network Intrusion Prevention
- Restrict Web-Based Content
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- 2025 Poland Wiper Attacks (campaign)
- APT12 (intrusion-set)
- APT28 (intrusion-set)
- APT37 (intrusion-set)
- APT39 (intrusion-set)
- BADNEWS (malware)
- BLACKCOFFEE (malware)
- BLUELIGHT (malware)
- BoxCaon (malware)
- CALENDAR (malware)
- Carbanak (intrusion-set)
- Clambling (malware)
- CloudDuke (malware)
- ComRAT (malware)
- Comnie (malware)
- CozyCar (malware)
- CreepyDrive (malware)
- Crutch (malware)
- DOGCALL (malware)
- Empire (tool)
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.
1---2name: attack-ent-t1102-002-bidirectional-communication3description: "Analyze MITRE ATT&CK T1102.002 Bidirectional Communication in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1102.002, Bidirectional Communication, or enterprise ATT&CK. Adversaries may use an existing, legitimate external Web service as a means for sending commands to and receiving output from a compromised system over the Web service channel."4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See https://attack.mitre.org/resources/terms-of-use/5metadata:6 source: https://skillmd.com/skills/santosomar/attack-ent-t1102-002-bidirectional-communication7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T1102.00210 attack_stix_id: attack-pattern--be055942-6e63-49d7-9fa1-9cb7d8a8f3f411 attack_version: "1.1"12 attack_modified: "2025-10-24T17:49:18.602Z"13---1415# MITRE ATT&CK T1102.002: Bidirectional Communication1617## When to use this skill1819Use this skill when the task involves T1102.002, Bidirectional Communication, 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 sub-technique.2021## Technique context2223- ATT&CK domain: enterprise24- ATT&CK ID: T1102.00225- Technique name: Bidirectional Communication26- Type: sub-technique27- ATT&CK URL: https://attack.mitre.org/techniques/T1102/00228- Tactics: command-and-control29- Platforms: ESXi, Linux, macOS, Windows30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may use an existing, legitimate external Web service as a means for sending commands to and receiving output from a compromised system over the Web service channel. Compromised systems may leverage popular websites and social media to host command and control (C2) instructions. Those infected systems can then send the output from those commands back over that Web service channel. The return traffic may occur in a variety of ways, depending on the Web service being utilized. For example, the return traffic may take the form of the compromised system posting a comment on a forum, issuing a pull request to development project, updating a document hosted on a Web service, or by sending a Tweet. 3738Popular websites and social media acting as a mechanism for C2 may give a significant amount of cover due to the likelihood that hosts within a network are already communicating with them prior to a compromise. Using common services, such as those offered by Google or Twitter, makes it easier for adversaries to hide in expected noise. Web service providers commonly use SSL/TLS encryption, giving adversaries an added level of protection.3940## Agent workflow41421. 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.432. 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.443. 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.454. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.465. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.476. 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.4849## Bundled resources5051- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.52- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.53- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.54- `templates/detection-brief.md`: detection engineering brief template.55- `templates/hunt-plan.md`: threat hunt plan template.56- `templates/incident-response-note.md`: incident response note template.57- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.58- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.59- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6061To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6263## Detection guidance6465No ATT&CK detection guidance was present in the source STIX object.6667## Useful telemetry and data sources6869- Not specified in the STIX object.7071## Mitigations to consider7273- Network Intrusion Prevention74- Restrict Web-Based Content7576## Known threat context7778Use these examples only as contextual leads, not as proof that an observed event is this technique:7980- 2025 Poland Wiper Attacks (campaign)81- APT12 (intrusion-set)82- APT28 (intrusion-set)83- APT37 (intrusion-set)84- APT39 (intrusion-set)85- BADNEWS (malware)86- BLACKCOFFEE (malware)87- BLUELIGHT (malware)88- BoxCaon (malware)89- CALENDAR (malware)90- Carbanak (intrusion-set)91- Clambling (malware)92- CloudDuke (malware)93- ComRAT (malware)94- Comnie (malware)95- CozyCar (malware)96- CreepyDrive (malware)97- Crutch (malware)98- DOGCALL (malware)99- Empire (tool)100101## Recommended output pattern102103When responding with this skill, structure the answer as:104105- Assessment: whether the evidence supports this ATT&CK mapping and why.106- Evidence: specific indicators, logs, behaviors, and assumptions.107- Detection: telemetry sources, analytic logic, and tuning considerations.108- Response: containment, eradication, recovery, and validation actions.109- Coverage gaps: missing logs, sensors, controls, or environmental details.110- References: include the ATT&CK URL and any user-provided evidence references.