-
Notifications
You must be signed in to change notification settings - Fork 180
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
THREAT-422 Stratus AWS S3 Detections #1528
base: develop
Are you sure you want to change the base?
Conversation
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.
This rule likely needs to be split into 3 more specific rules for DeleteObject, DeleteObjects, and CopyObject.
def rule(event): | ||
return ( | ||
aws_cloudtrail_success(event) | ||
and event.get("eventSource") == "s3.amazonaws.com" | ||
and event.get("eventName") in SUSPICIOUS_EVENTS | ||
) |
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.
This seems like it would be overly noisy, especially since the rule has a threshold of 1. For DeleteObject
I would expect a high threshold. For DeleteObjects
a lower threshold. We are not interested in GetObject
as that is a read only event and will be very noisy. For CopyObject
we are only interested when the copied files are encrypted with a client-side key, and again this should have a high threshold.
22bc8b4
to
3e4b9aa
Compare
Changes
AWS.S3.SuspiciousFileActivities
ruleTesting
pat test