Adversaries may implant cloud or container images with malicious code to establish persistence after gaining access to an environment. 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 implanted or backdoored. Unlike Upload Malware, this technique focuses on adversaries implanting an image in a registry within a victim’s environment. Depending on how the infrastructure is provisioned, this could provide persistent access if the infrastructure provisioning tool is instructed to always use the latest image.[1]
A tool has been developed to facilitate planting backdoors in cloud container images.[2] If an attacker has access to a compromised AWS instance, and permissions to list the available container images, they may implant a backdoor such as a Web Shell.[1]
| ID | Mitigation | Description |
|---|---|---|
| M1047 | Audit |
Periodically check the integrity of images and containers used in cloud deployments to ensure they have not been modified to include malicious software. |
| M1045 | Code Signing |
Several cloud service providers support content trust models that require container images be signed by trusted sources.[3][4] |
| M1026 | Privileged Account Management |
Limit permissions associated with creating and modifying platform images or containers based on the principle of least privilege. |
| ID | Data Source | Data Component |
|---|---|---|
| DS0007 | Image | Image Creation |
| Image Modification |
Monitor interactions with images and containers by users to identify ones that are added or modified anomalously.
In containerized environments, changes may be detectable by monitoring the Docker daemon logs or setting up and monitoring Kubernetes audit logs depending on registry configuration.