T1609 Container Administration Command — Detection Rules

Detection workspace for T1609 Container Administration Command: 3 Sigma sources, 1 Atlas concepts and 1 anomaly models. No live detection validation.

Source-backed rule directory

Potential Remote Command Execution In Pod Container · test · medium · {"category":"application","product":"kubernetes","service":"audit"}
Kubernetes Potential Enumeration Activity · experimental · medium · {"product":"kubernetes","service":"audit"}
Potential Sidecar Injection Into Running Deployment · test · medium · {"category":"application","product":"kubernetes","service":"audit"}

Atlas deterministic concepts

T1609 Container Administration Command

Published pseudocode, not an executable rule

MATCH(orchestrator_request_subresource = exec) AND actor NOT_IN approved_container_admins -> ALERT

Anomaly models

Container administration interface executes command — T1609 Container Administration Command

Comparison 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.

ATT&CK analytic guidance

DET0065 Detection Strategy for Container Administration Command Abuse

AN0177 Analytic 0177

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.

Connected ecosystem references

Linked tags

rule_source_available Edge Anomaly Peer-Group Anomaly Rare-Category Anomaly

Simulation, tools and telemetry

T1609 simulation workspace

Peirates · S0683

Threat actor context

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.

TeamTNT · G0139

Existing anomaly research

Original publication snapshot · Anomaly Detection Atlas

Complete technique engineering workbook

Collection configuration and event examples · Anomaly models and design worksheet · Tools and documented software · Simulation procedures · Offline synthetic collection check

Exact source tags are not semantic relevance verdicts. Review actual rule conditions and observation points; imported rules are not backend-compiled or live-validated.

Connected anomaly research

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.

Sequence

Telemetry contracts · Maintained query examples · Validation and blind spots

Pinned research references. No browser attack runner or production-validated detector is asserted. Imported procedures remain unvalidated; any bounded lab evidence has its own scope. ATT&CK / Atomic provenance · Detection provenance.