1200KM / detection
Detection workspace for T1609 Container Administration Command: 3 Sigma sources, 1 Atlas concepts and 1 anomaly models. No live detection validation.
MATCH(orchestrator_request_subresource = exec) AND actor NOT_IN approved_container_admins -> ALERTComparison unit: identity-namespace-workload relationship.
Expected behavior: a small approved set of identities performs interactive execution in specific namespaces.
Deviation: new identity-to-namespace edge or rare service-account action.
Defenders may detect abuse of container administration commands by observing anomalous use of management utilities (`docker exec`, `kubectl exec`, or API calls to kubelet) correlated with unexpected process creation inside containers. Behavioral chains include unauthorized API requests followed by command execution within running pods or containers, often originating from unusual user accounts, automation scripts, or IP addresses outside the expected cluster management plane.
These are explicit actor-to-technique associations in the existing Threat Matrix snapshot, not attribution of an event or proof that a detector identifies the actor. No tool-to-actor relationship is inferred.
Curated research views reached through an exact source technique, a catalog model, or a reviewed collection reference. These are navigation associations, not claims of detector effectiveness or sensor equivalence.
Telemetry contracts · Maintained query examples · Validation and blind spots
Pinned research references. No browser attack runner, live simulation result or validated detector is asserted. Source mappings and validation limits are preserved. ATT&CK / Atomic provenance · Detection provenance.