Elastic low stable kql
Scheduled Job Creation via At Utility Inside a Container
This rule detects execution of the "at" or "atd" job-scheduling utilities inside a Linux container. Containers are typically immutable, single-purpose, and do not run interactive job schedulers, so the use of "at" to queue a one-time command is anomalous. Adversaries abuse "at" to establish persistence or to execute a payload at a later time after gaining a foothold inside a container.
Detection Logic
from logs-cloud_defend.process* metadata _id, _index, _version
| where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
container.id like "*" and
(
process.name in ("at", "atd") or
kql("""process.args: "at" """)
)
| keep @timestamp, host.id, container.id, process.name, process.args, process.parent.name, process.parent.executable, user.id, _id, _index, _version False Positives
- ⚠ Some container images bundle the "at"/"atd" utilities and a small number of workloads may legitimately schedule one-time jobs. Investigate the queued command and the scheduling principal; baseline and except known automation images where appropriate.
Field Validations
Loading…
Comments (0)
Loading comments...