- Notifications
You must be signed in to change notification settings - Fork 603
[New Rule] Adding Coverage for Unusual AWS S3 Object Encryption with SSE-C
#4377
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.
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
Merged
terrancedejesus merged 12 commits into main from new-rule-aws-s3-sse-c-encrypted-objects Jan 15, 2025
Merged
[New Rule] Adding Coverage for Unusual AWS S3 Object Encryption with SSE-C
#4377
terrancedejesus merged 12 commits into main from new-rule-aws-s3-sse-c-encrypted-objects Jan 15, 2025
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Enhancement - GuidelinesThese guidelines serve as a reminder set of considerations when addressing adding a new schema feature to the code. Documentation and Context
Code Standards and Practices
Testing
Additional Schema Related Checks
|
terrancedejesus commented Jan 15, 2025
rules/integrations/aws/impact_s3_unusual_object_encryption_with_sse_c.toml Show resolved Hide resolved
Samirbous approved these changes Jan 15, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice one! maybe add an additional one with threshold rule type (multi encryptions by same aws.cloudtrail.user_identity.arn)
Mikaayenson approved these changes Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport: auto Domain: Cloud Workloads Integration: AWS AWS related rules meta:rapid-merge patch Rule: New Proposal for new rule schema
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Pull Request
Issue link(s):
Summary - What I changed
Adds detection coverage for ransom attempts by encrypting S3 objects with SSE-C via compromised AWS creds.
Identifies when AWS S3 objects stored in a bucket are encrypted using Server-Side Encryption with Customer-Provided Keys (SSE-C). Adversaries with compromised AWS credentials can encrypt objects in an S3 bucket using their own encryption keys, rendering the objects unreadable or recoverable without the key. This can be used as a form of ransomware to extort the bucket owner for the decryption key.
How To Test
Visit shared stack with the following query within the last 2 days.
Checklist
bug
,enhancement
,schema
,maintenance
,Rule: New
,Rule: Deprecation
,Rule: Tuning
,Hunt: New
, orHunt: Tuning
so guidelines can be generatedmeta:rapid-merge
label if planning to merge within 24 hoursContributor checklist