Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix false positives in "AWS Attached Malicious Lambda Layer" rule #5223

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Fix false positives in "AWS Attached Malicious Lambda Layer" rule #5223

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
92b52f9
Update aws_attached_malicious_lambda_layer.yml
imall4n Mar 5, 2025
4040299
Update aws_attached_malicious_lambda_layer.yml
nasbench Mar 5, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion rules/cloud/aws/cloudtrail/aws_attached_malicious_lambda_layer.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ references:
- https://docs.aws.amazon.com/lambda/latest/dg/API_UpdateFunctionConfiguration.html
author: Austin Songer
date: 2021-09-23
modified: 2022-10-09
modified: 2025-03-05
tags:
- attack.privilege-escalation
logsource:
Expand All @@ -18,6 +18,7 @@ detection:
selection:
eventSource: lambda.amazonaws.com
eventName|startswith: 'UpdateFunctionConfiguration'
requestParameters.layers|contains: '*'
condition: selection
falsepositives:
- Lambda Layer being attached may be performed by a system administrator. Verify whether the user identity, user agent, and/or hostname should be making changes in your environment.
Expand Down