New AWS Lambda Function URL Configuration Created
Detects when a user creates a Lambda function URL configuration, which could be used to expose the function to the internet and potentially allow unauthorized access to the function's IAM role for AWS API calls. This…
Description
Detects when a user creates a Lambda function URL configuration, which could be used to expose the function to the internet and potentially allow unauthorized access to the function's IAM role for AWS API calls. This could give an adversary access to the privileges associated with the Lambda service role that is attached to that function.
Detection logic
Detection requirements
- Log source product
- aws
- Log source service
- cloudtrail
Known benign triggers
- Creating a Lambda function URL configuration from unfamiliar users should be investigated. If known behavior is causing false positives, it can be exempted from the rule.
- Creating a Lambda function URL configuration may be performed by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment.
MITRE ATT&CK mappings
Not mapped to ATT&CK.
References
| Reference | Cited by |
|---|---|
| cloud.hacktricks.xyz/pentesting-cloud/aws-security/aws-privilege-escalation/aws-lambda-privesc | Only this detection cites it |
| docs.aws.amazon.com/lambda/latest/dg/API_CreateFunctionUrlConfig.html | Only this detection cites it |
| www.wiz.io/blog/how-to-set-secure-defaults-on-aws | Only this detection cites it |
From the source
- At source
- Open at source
- Upstream identifier
- ec541962-c05a-4420-b9ea-84de072d18f4
- Tagged by the source as
- attack.initial-accessattack.privilege-escalation
Licence
- Published under
- Detection Rule License 1.1Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1