Techniques › T1496.002 › AN0084
AN0084 Analytic 0084
IaaS · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Virtual instances or workloads generating sustained outbound data rates, often to TOR, VPN, or proxy endpoints. Often coincides with unusual IAM usage or deployed scripts (e.g., cron jobs using proxy clients).</p>
- Detects
- T1496.002 Bandwidth Hijacking
- Part of
- DET0028 Detect Excessive or Unauthorized Bandwidth Usage for Botnet, Proxyjacking, or Scanning Purposes
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 | StartInstances | DC0080 Instance Start |
| AWS:VPCFlowLogs | egress > 90th percentile or frequent connection reuse | DC0078 Network Traffic Flow |
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 |
|---|---|
InstanceType | High-throughput instance types are more likely to be targeted for hijacking. |
TrafficEgressThreshold | Customize detection thresholds based on cloud provider quotas or billing alerts. |