Can create malicious Lambda functions.1
Serverless Execution T1648
- Tactic
- Execution
- Platforms
- SaaS, IaaS, Office Suite
- Version
- 1.2
- Created
- 27 May 2022
- Last modified
- 15 April 2025
- Contributors
- Shailesh Tiwary (Indian Army); Praetorian; Oleg Kolesnikov, Securonix; Cisco; Varonis Threat Labs; Alex Soler, AttackIQ; Vectra AI; OWN
Adversaries may abuse serverless computing, integration, and automation services to execute arbitrary code in cloud environments. Many cloud providers offer a variety of serverless resources, including compute engines, application integration services, and web servers.
Serverless Execution MITRE reference T1648
1 software entry is documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
All 1 software entries for this technique
Offense vs defense T1648
Is defensive coverage keeping up with adversary use? Eight counts, each ranked against all 697 ATT&CK techniques. Attack sits left, defense right, so a shape leaning left means adversaries are better documented here than defenders are equipped. Hover any spoke for its percentile and the share of techniques that have more. The timeline below shows when each side arrived.
Serverless Execution detection strategy DET0374
MITRE names one behaviour worth catching for this technique and breaks it into 3 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Detection Strategy for Serverless Execution (T1648)
AN1053 · IaaS
Correlate creation or modification of serverless functions (e.g., AWS Lambda, GCP Cloud Functions, Azure Functions) with anomalous IAM role assignments or permissions escalation events. Detect subsequent executions of newly created functions that perform unexpected actions such as spawning outbound network connections, accessing sensitive resources, or creating additional credentials.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Application Log ContentDC0038 | AWS:CloudTrail | InvokeFunction: Unexpected or repeated invocation of functions not tied to known workflows |
| Cloud Service ModificationDC0069 | AWS:CloudTrail | CreateFunction / UpdateFunctionConfiguration: Function creation, role assignment, or configuration change events |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| RoleScope | Which IAM roles or privileges are considered sensitive when applied to functions |
| AllowedFunctions | Known baseline list of approved serverless functions to reduce false positives |
| TimeWindow | Temporal threshold for correlating function creation with anomalous execution |
AN1054 · Office Suite
Monitor for creation of new Power Automate flows or equivalent automation scripts that trigger on user or file events. Detect anomalous actions performed by these automations, such as email forwarding, anonymous link creation, or unexpected API calls to external endpoints.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Application Log ContentDC0038 | m365:exchange | New-InboxRule: Automation that triggers abnormal forwarding or external link generation |
| Cloud Service ModificationDC0069 | m365:unified | AddFlow / UpdateFlow: New automation or workflow creation events |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| UserContext | Business units or users where automation creation is expected (developers, admins) |
| FlowActions | Specific automation actions (email forwarding, file sharing) that should be considered suspicious |
AN1055 · SaaS
Track creation or update of SaaS automation scripts (e.g., Google Workspace Apps Script). Detect when these scripts are bound to user events such as file opens or account modifications, and correlate with subsequent abnormal API calls that exfiltrate or modify user data.
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
| Data component | Name | Channel |
|---|---|---|
| Application Log ContentDC0038 | saas:googledrive | FileOpen / FileAccess: Event-driven script triggering on user file actions |
| Cloud Service ModificationDC0069 | saas:appsscript | Create / Update: Deployment of scripts with event-driven triggers |
Tunable fields
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
| Field | What you tune |
|---|---|
| ScriptScope | Which SaaS apps or APIs can be legitimately automated in the environment |
| TriggerTypes | Event-driven triggers (e.g., on file open, on user creation) considered suspicious |
Where possible, consider restricting access to and use of serverless functions. For examples, conditional access policies can be applied to users attempting to create workflows in Microsoft Power Automate. Google Apps Scripts that use OAuth can be limited by restricting access to high-risk OAuth scopes.
Remove permissions to create, modify, or run serverless resources from users that do not explicitly require them.
Tests from Atomic Red Team (MIT licence) · technique definition