Techniques › T1020.001 › AN1131
AN1131 Analytic 1131
IaaS · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Configuration changes to virtual TAP/mirror policies that forward traffic to unapproved destinations. Detection correlates management plane API calls with mirrored traffic observation.</p>
- Detects
- T1020.001 Traffic Duplication
- Part of
- DET0403 Detection Strategy for Traffic Duplication via Mirroring in IaaS and Network Devices
Log sources and channels
Exactly as MITRE states them in x_mitre_log_source_references. Where a channel is vague, it is vague in the source; kevmap does not tidy it.
| Log source | Channel | Data component |
|---|---|---|
| AWS:CloudTrail | CreateTrafficMirrorSession or ModifyTrafficMirrorTarget | DC0078 Network Traffic Flow |
| AWS:VPCFlowLogs | Traffic observed on mirror destination instance | DC0082 Network Connection Creation |
Mutable elements
Parameters MITRE marks as environment-specific. These are the knobs you are expected to tune; they are why an analytic is not a rule.
| Field | Description |
|---|---|
TimeWindow | Detect mirror session creation followed by mirrored traffic within X seconds (e.g., 60s) |
MirrorDestinationCIDR | Define suspicious or external mirror targets (e.g., non-enterprise ranges) |
UserIdentity | Flag traffic mirror activity by non-privileged or unexpected IAM roles |