Adversaries may rely on a user running a malicious image to facilitate execution. Amazon Web Services (AWS) Amazon Machine Images (AMIs), Google Cloud Platform (GCP) Images, and Azure Images as well as popular container runtimes such as Docker can be backdoored. Backdoored images may be uploaded to a public repository via Upload Malware, and users may then download and deploy an instance or container from the image without realizing the image is malicious, thus bypassing techniques that specifically achieve Initial Access. This can lead to the execution of malicious code, such as code that executes cryptocurrency mining, in the instance or container.
Adversaries may also name images a certain way to increase the chance of users mistakenly deploying an instance or container from the image (ex: Match Legitimate Name or Location).
TeamTNT has relied on users to download and execute malicious Docker images.
Audit images deployed within the environment to ensure they do not contain any malicious components.
Utilize a trust model such as Docker Content Trust with digital signatures to ensure runtime verification of the integrity and publisher of specific image tags.
|M1031||Network Intrusion Prevention||
Network prevention intrusion systems and systems designed to scan and remove malicious downloads can be used to block activity.
Train users to be aware of the existence of malicious images and how to avoid deploying instances and containers from them.
|ID||Data Source||Data Component||Detects|
|DS0015||Application Log||Application Log Content||
Monitor for third-party application logging, messaging, and/or other artifacts that may rely on a user running a malicious image to facilitate execution.
Monitor executed commands and arguments that may attempt to take advantage of a weakness in an Internet-facing computer or program using software, data, or commands in order to cause unintended or unanticipated behavior.
Track the deployment of new containers, especially from newly built images.
Monitor the behavior of containers within the environment to detect anomalous behavior or malicious activity after users deploy from malicious images.
Monitor the local image registry to make sure malicious images are not added.
Monitor for newly constructed instances that may attempt to take advantage of a weakness in an Internet-facing computer or program using software, data, or commands in order to cause unintended or unanticipated behavior.
Monitor for the activation or invocation of an instance (ex: instance.start within GCP Audit Logs)