Container Orchestration Job

T1053.007

Sub-technique of T1053 Scheduled Task/Job.View on attack.mitre.org

About this technique

Adversaries may abuse task scheduling functionality provided by container orchestration tools such as Kubernetes to schedule deployment of containers configured to execute malicious code. Container orchestration jobs run these automated tasks at a specific date and time, similar to cron jobs on a Linux system. Deployments of this type can also be configured to maintain a quantity of containers over time, automating the process of maintaining persistence within a cluster.

In Kubernetes, a CronJob may be used to schedule a Job that runs one or more containers to perform specific tasks. An adversary therefore may utilize a CronJob to schedule deployment of a Job that executes malicious code in various nodes within a cluster.

Detection rules2

Rules on DetectionCode tagged with T1053.007.

Sigma0

No Sigma rules are mapped to this technique yet.

Splunk2

RuleTypeRiskData source
Cisco Isovalent - Cron Job CreationAnomalyNULLCisco Isovalent Process Exec
Kubernetes Cron Job CreationAnomalyNULLKubernetes Audit

Groups0

None recorded.

Software0

None recorded.

Campaigns0

None recorded.

Procedure examples0

No procedure examples are recorded for this technique.

References3

  1. Kubernetes CronJob Open source
    The Kubernetes Authors. (n.d.). Kubernetes CronJob. Retrieved March 29, 2021.
  2. Kubernetes Jobs Open source
    The Kubernetes Authors. (n.d.). Kubernetes Jobs. Retrieved March 30, 2021.
  3. Threat Matrix for Kubernetes Open source
    Weizman, Y. (2020, April 2). Threat Matrix for Kubernetes. Retrieved March 30, 2021.

Data from MITRE ATT&CK® (Enterprise). ATT&CK® is a registered trademark of The MITRE Corporation.