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.(Citation: Kubernetes Jobs)(Citation: Kubernetes CronJob) An adversary therefore may utilize a CronJob to schedule deployment of a Job that executes malicious code in various nodes within a cluster.(Citation: Threat Matrix for Kubernetes)
Container Orchestration Job
source_name: mitre-attack  url: https://attack.mitre.org/techniques/T1053/007  external_id: T1053.007     source_name: Kubernetes CronJob  description: The Kubernetes Authors. (n.d.). Kubernetes CronJob. Retrieved March 29, 2021.  url: https://kubernetes.io/docs/concepts/workloads/controllers/cron-jobs/     source_name: Kubernetes Jobs  description: The Kubernetes Authors. (n.d.). Kubernetes Jobs. Retrieved March 30, 2021.  url: https://kubernetes.io/docs/concepts/workloads/controllers/job/     source_name: Threat Matrix for Kubernetes  description: Weizman, Y. (2020, April 2). Threat Matrix for Kubernetes. Retrieved March 30, 2021.  url: https://www.microsoft.com/security/blog/2020/04/02/attack-matrix-kubernetes/     