MITRE ATT&CK T0830: Adversary-in-the-Middle
When to use this skill
Use this skill when the task involves T0830, Adversary-in-the-Middle, ics 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: ics
- ATT&CK ID: T0830
- Technique name: Adversary-in-the-Middle
- Type: technique
- ATT&CK URL: https://attack.mitre.org/techniques/T0830
- Tactics: collection
- Platforms: None
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries with privileged network access may seek to modify network traffic in real time using adversary-in-the-middle (AiTM) attacks. (Citation: Gabriel Sanchez October 2017) This type of attack allows the adversary to intercept traffic to and/or from a particular device on the network. If a AiTM attack is established, then the adversary has the ability to block, log, modify, or inject traffic into the communication stream. There are several ways to accomplish this attack, but some of the most-common are Address Resolution Protocol (ARP) poisoning and the use of a proxy. (Citation: Bonnie Zhu, Anthony Joseph, Shankar Sastry 2011)
An AiTM attack may allow an adversary to perform the following attacks:
Block Reporting Message, Spoof Reporting Message, Modify Parameter, Unauthorized Command Message
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
- Audit
- Communication Authenticity
- Disable or Remove Feature or Program
- Network Intrusion Prevention
- Network Segmentation
- Out-of-Band Communications Channel
- Software Process and Device Authentication
- Static Network Configuration
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- Triton Safety Instrumented System Attack (campaign)
- VPNFilter (malware)
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
- Conrad Layne - GE Digital
1---2name: attack-ics-t0830-adversary-in-the-middle3description: Analyze MITRE ATT&CK T0830 Adversary-in-the-Middle in the ics matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T0830, Adversary-in-the-Middle, or ics ATT&CK. Adversaries with privileged network access may seek to modify network traffic in real time using adversary-in-the-middle (AiTM) attacks.4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See h5---67# MITRE ATT&CK T0830: Adversary-in-the-Middle89## When to use this skill1011Use this skill when the task involves T0830, Adversary-in-the-Middle, ics 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: ics16- ATT&CK ID: T083017- Technique name: Adversary-in-the-Middle18- Type: technique19- ATT&CK URL: https://attack.mitre.org/techniques/T083020- Tactics: collection21- Platforms: None22- Required permissions: Not specified23- Effective permissions: Not specified24- Defenses bypassed: Not specified2526## ATT&CK description2728Adversaries with privileged network access may seek to modify network traffic in real time using adversary-in-the-middle (AiTM) attacks. (Citation: Gabriel Sanchez October 2017) This type of attack allows the adversary to intercept traffic to and/or from a particular device on the network. If a AiTM attack is established, then the adversary has the ability to block, log, modify, or inject traffic into the communication stream. There are several ways to accomplish this attack, but some of the most-common are Address Resolution Protocol (ARP) poisoning and the use of a proxy. (Citation: Bonnie Zhu, Anthony Joseph, Shankar Sastry 2011) 2930An AiTM attack may allow an adversary to perform the following attacks: 31[Block Reporting Message](https://attack.mitre.org/techniques/T0804), [Spoof Reporting Message](https://attack.mitre.org/techniques/T0856), [Modify Parameter](https://attack.mitre.org/techniques/T0836), [Unauthorized Command Message](https://attack.mitre.org/techniques/T0855)3233## Agent workflow34351. 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.362. 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.373. 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.384. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.395. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.406. 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.4142## Bundled resources4344- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.45- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.46- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.47- `templates/detection-brief.md`: detection engineering brief template.48- `templates/hunt-plan.md`: threat hunt plan template.49- `templates/incident-response-note.md`: incident response note template.50- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.51- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.52- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.5354To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.5556## Detection guidance5758No ATT&CK detection guidance was present in the source STIX object.5960## Useful telemetry and data sources6162- Not specified in the STIX object.6364## Mitigations to consider6566- Audit67- Communication Authenticity68- Disable or Remove Feature or Program69- Network Intrusion Prevention70- Network Segmentation71- Out-of-Band Communications Channel72- Software Process and Device Authentication73- Static Network Configuration7475## Known threat context7677Use these examples only as contextual leads, not as proof that an observed event is this technique:7879- Triton Safety Instrumented System Attack (campaign)80- VPNFilter (malware)8182## Recommended output pattern8384When responding with this skill, structure the answer as:8586- Assessment: whether the evidence supports this ATT&CK mapping and why.87- Evidence: specific indicators, logs, behaviors, and assumptions.88- Detection: telemetry sources, analytic logic, and tuning considerations.89- Response: containment, eradication, recovery, and validation actions.90- Coverage gaps: missing logs, sensors, controls, or environmental details.91- References: include the ATT&CK URL and any user-provided evidence references.9293## ATT&CK contributors9495- Conrad Layne - GE Digital
santosomar