-
Notifications
You must be signed in to change notification settings - Fork 176
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
May Update: S3 Rules #53
Conversation
# IP addresses (in CIDR notation) indicating approved IP ranges for accessing S3 buckets | ||
IP_WHITELIST = { | ||
BUCKET_NAMES = { | ||
# Example bucket names go here |
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.
Should this comment say something like "restricted bucket names go here" or something?
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.
Yep, adding
ip_network('10.0.0.0/8'), | ||
} | ||
|
||
|
||
def rule(event): | ||
# Only evaluate if the remoteIP field is present | ||
if BUCKET_NAMES: |
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.
Is the intent that if BUCKET_NAMES is empty, it applies to all buckets? Perhaps a comment should clarify that under the BUCKET_NAMES declaration at the top.
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.
The intention is that if it's empty, we just apply to all buckets
* adding special handling of SchemaWrongKeyError exceptions * format update; added unit test to check new method * fixing bad merge
sync this fork to panther-labs/panther-analysis v3.16.0
Background
A general audit and refresh of our S3 access log rules
Changes
Testing
Locally: