User Execution: Вредоносный образ
Other sub-techniques of User Execution (3)
| ID | Название |
|---|---|
| .001 | Вредоносная ссылка |
| .002 | Вредоносный файл |
| .003 | Вредоносный образ |
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.(Citation: Summit Route Malicious AMIs) 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).(Citation: Aqua Security Cloud Native Threat Report June 2021)
Примеры процедур |
|
| Название | Описание |
|---|---|
| TeamTNT |
TeamTNT has relied on users to download and execute malicious Docker images.(Citation: Lacework TeamTNT May 2021) |
Контрмеры |
|
| Контрмера | Описание |
|---|---|
| Code Signing |
Enforce binary and application integrity with digital signature verification to prevent untrusted code from executing. |
| Network Intrusion Prevention |
Use intrusion detection signatures to block traffic at network boundaries. |
| User Training |
Train users to be aware of access or manipulation attempts by an adversary to reduce the risk of successful spearphishing, social engineering, and other techniques that involve user interaction. |
| Audit |
Perform audits or scans of systems, permissions, insecure software, insecure configurations, etc. to identify potential weaknesses. |
Обнаружение
Monitor the local image registry to make sure malicious images are not added. 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.
Ссылки
- Team Nautilus. (2021, June). Attacks in the Wild on the Container Supply Chain and Infrastructure. Retrieved August 26, 2021.
- Piper, S.. (2018, September 24). Investigating Malicious AMIs. Retrieved March 30, 2021.
- Stroud, J. (2021, May 25). Taking TeamTNT's Docker Images Offline. Retrieved September 22, 2021.
- Microsoft. (2019, September 5). Content trust in Azure Container Registry. Retrieved October 16, 2019.
- Docker. (2019, October 10). Content trust in Docker. Retrieved October 16, 2019.
Связанные риски
Каталоги
Мы используем cookie-файлы, чтобы получить статистику, которая помогает нам улучшить сервис для вас с целью персонализации сервисов и предложений. Вы может прочитать подробнее о cookie-файлах или изменить настройки браузера. Продолжая пользоваться сайтом, вы даёте согласие на использование ваших cookie-файлов и соглашаетесь с Политикой обработки персональных данных.