LoFP / development teams and data pipelines may legitimately use container overrides to parameterize job executions with dynamic inputs. validate that the submitting identity, job queue, and override content are consistent with expected workload behavior.

Techniques

• T1059

Sample rules

AWS Batch Job Submitted with Container Override by Unusual Identity

• source: elastic
• technicques:
  • T1059

Description

Detects the first time an AWS identity submits an AWS Batch job with a container command override (“containerOverrides.command”), indicating a runtime-modified execution environment. Command overrides allow the submitter to replace the default command of a job definition at submission time. This flexibility is commonly abused by adversaries to inject malicious commands or exfiltration logic into otherwise legitimate Batch compute environments without modifying the underlying job definition — making the malicious activity harder to detect through configuration review alone.

Detection logic

data_stream.dataset: "aws.cloudtrail"
    and event.provider: "batch.amazonaws.com"
    and event.action: "SubmitJob"
    and event.outcome: "success"
    and aws.cloudtrail.request_parameters: (*containerOverrides* and *command*)