Skip to content

Tune and rename AWS attached malicious Lambda layer rule#5236

Merged
nasbench merged 3 commits intoSigmaHQ:masterfrom
nickatrecon:nickatrecon/fix-tune-aws_attached_malicious_lambda_layer
Apr 7, 2025
Merged

Tune and rename AWS attached malicious Lambda layer rule#5236
nasbench merged 3 commits intoSigmaHQ:masterfrom
nickatrecon:nickatrecon/fix-tune-aws_attached_malicious_lambda_layer

Conversation

@nickatrecon
Copy link
Copy Markdown
Contributor

Summary of the Pull Request

Tune and rename rules/cloud/aws/cloudtrail/aws_attached_malicious_lambda_layer.yml.

Name: AWS Attached Malicious Lambda Layer -> AWS New Lambda Layer Attached
Level: medium -> low

Changelog

fix: AWS Attached Malicious Lambda Layer - reduced level and renamed

Example Log Event

Fixed Issues

#5235

SigmaHQ Rule Creation Conventions

  • If your PR adds new rules, please consider following and applying these conventions

@github-actions github-actions Bot added the Rules label Mar 17, 2025
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Welcome @nickatrecon 👋

It looks like this is your first pull request on the Sigma rules repository!

Please make sure to read the SigmaHQ conventions document to make sure your contribution is adhering to best practices and has all the necessary elements in place for a successful approval.

Thanks again, and welcome to the Sigma community! 😃

@nasbench nasbench requested a review from frack113 March 21, 2025 02:11
@nasbench nasbench added this to the Sigma-March-Release milestone Mar 21, 2025
@nasbench
Copy link
Copy Markdown
Member

Since this PR touches the same rules as #5223

I'll close that and moved the changes to this instead

Thanks @imall4n (will credit you in the commit)

@nasbench nasbench merged commit e874eaf into SigmaHQ:master Apr 7, 2025
12 checks passed
@nickatrecon nickatrecon deleted the nickatrecon/fix-tune-aws_attached_malicious_lambda_layer branch April 7, 2025 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Rule tuning: AWS Attached Malicious Lambda Layer should be informational/low and renamed

3 participants