You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need a check that looks for public S3 read/write permissions and automatically revokes these when found. This check would look for the following public permissions:
Bucket list objects
Bucket write objects (This is high severity)
Bucket read permissions
Bucket write permissions (This is high severity)
For the high severity permissions we should explicitly detail the customer should manually audit the bucket and it's objects to ensure that is has not been compromised.
This automation workflow can follow a similar pattern to the one for Exposed Access Keys linked below:
If public access is blocked at account then trusted advisor s3 check would never fail, so one wouldn't need to have any reactive approach. To ensure no one changes the public access block setting, we set a policy via SCP.
We need a check that looks for public S3 read/write permissions and automatically revokes these when found. This check would look for the following public permissions:
Bucket list objects
Bucket write objects (This is high severity)
Bucket read permissions
Bucket write permissions (This is high severity)
For the high severity permissions we should explicitly detail the customer should manually audit the bucket and it's objects to ensure that is has not been compromised.
This automation workflow can follow a similar pattern to the one for Exposed Access Keys linked below:
https://github.com/aws/Trusted-Advisor-Tools/tree/master/ExposedAccessKeys
Let me know what you think about this proposed check.
The text was updated successfully, but these errors were encountered: