Techniques › T1543.005 › AN1304
AN1304 Analytic 1304
Containers · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Correlate the creation or modification of containers using restart policies (e.g., 'always') or DaemonSets with elevated host access, service account misuse, or privileged container contexts. Watch for manipulation of systemd units involving containers or pod scheduling targeting specific nodes or namespaces.</p>
- Detects
- T1543.005 Container Service
- Part of
- DET0473 Detect persistent or elevated container services via container runtime or cluster manipulation
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 |
|---|---|---|
| auditd:SYSCALL | execve | DC0032 Process Creation |
| systemd:unit | container run with restart policy set to 'always' or 'unless-stopped' | DC0072 Container Creation |
| kubernetes:audit | create | DC0019 Pod Creation |
| kubernetes:audit | create | DC0060 Service 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 |
|---|---|
restartPolicy | Tune for environments that legitimately use 'always' or 'unless-stopped' in trusted containers |
targetNamespace | Scope detection to high-risk namespaces (e.g., kube-system) |
nodeSelector|nodeName | Adjust if targeting known cluster configurations or test environments |
unitFilePath | Adapt to your OS/systemd hierarchy and container binary references |
TimeWindow | Adjust temporal correlation (e.g., container launch → privilege escalation) |