Cloud environments
In cloud, "execution" frequently means calling management APIs, running commands through administration services, deploying functions or containers, rather than running malware on a laptop.
TA0002Tactic 4 of 15
How do attackers run code in AWS once they have access?
Execution covers techniques that result in adversary-controlled code or commands running on a local or remote system. It is usually paired with other tactics — running a tool to discover the environment, or running code that steals credentials — and is the point where intent turns into action.
The adversary is trying to run malicious code or instructions on a system.
Execution consists of techniques that result in adversary-controlled code running on a local or remote system. Techniques that run malicious code are often paired with techniques from all other tactics to achieve broader goals, like exploring a network or stealing data. For example, an adversary might use a remote access tool to run a PowerShell script that does Remote System Discovery.
In cloud, "execution" frequently means calling management APIs, running commands through administration services, deploying functions or containers, rather than running malware on a laptop.
Examples: issuing AWS CLI / SDK calls (Cloud API), ssm:SendCommand against instances, creating Lambda functions, running ECS tasks or EKS pods, or modifying EC2 user data.
ATT&CK now includes Direct (T1699) and Indirect (T1698) Prompt Injection under Execution: adversary instructions executed by an AI system. For agents with tools, that execution can translate into real API calls.
ssm:SendCommand / ssm:StartSessionRun commands on managed instances.lambda:CreateFunction / UpdateFunctionCodeRun code with the function’s execution role.ecs:RunTaskLaunch containers with a chosen task role.Most cloud attacker activity is API calls with stolen credentials.
View on MITRE ATT&CKSSM and similar services run commands on fleets.
Serverless functions execute with their own (sometimes privileged) roles.
Containers deployed into clusters run attacker code next to legitimate workloads.
Instructions hidden in content ingested by AI systems.
Instructions supplied directly to an AI system.
SendCommand / StartSession by unexpected principals
Function creation or code changes outside pipelines
Agent tool calls with parameters from untrusted content
For leadership
In cloud, the ability to execute is granted by permissions. Every identity able to run commands on production systems or deploy code is part of the production attack surface.
Myth
“Without malware there is no execution.”
Reality
Cloud attacks often execute entirely through legitimate APIs and administrative services.
0 of 3 done
Saved only in this browser. Nothing is sent to Securitain.
MITRE ATT&CK® and ATT&CK® are registered trademarks of The MITRE Corporation. ATT&CK data © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation (ATT&CK v20.1). Securitain is not affiliated with or endorsed by MITRE. Explanations, scenarios and control mappings on this page are Securitain’s own analysis. Sources and licensing
Stay in the loop