Techniques › T1204 › AN1317
AN1317 Analytic 1317
Containers · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Cause→effect chain in CI/dev desktops: (1) user triggers container run/pull after opening a doc/link/script, (2) newly created image/container uses unexpected external registry or entrypoint, (3) container starts and immediately egresses to suspicious destinations.</p>
- Detects
- T1204 User Execution
- Part of
- DET0478 User Execution – multi-surface behavior chain (documents/links → helper/unpacker → LOLBIN/child → egress)
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 |
|---|---|---|
| docker:events | created,started: new container from untrusted registry or unexpected entrypoint | DC0072 Container Creation |
| docker:events | start | DC0077 Container Start |
| NSM:Flow | container egress to unknown IPs/domains | DC0085 Network Traffic Content |
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 |
|---|---|
TrustedRegistries | Approved registries/namespaces. |
AllowedEntrypoints | Expected CMD/ENTRYPOINT for known images. |
TimeWindow | Correlate user action → docker/podman run within 10 minutes. |
KEV CVEs whose mapped technique this analytic detects
| CVE | Vendor / product | State |
|---|---|---|
| CVE-2023-38831 | RARLAB WinRAR | Mapped |
| CVE-2025-24993 | Microsoft Windows | Mapped |