Skip to content

Commit

Permalink
Patch 460 (#482)
Browse files Browse the repository at this point in the history
* Update s3-bucket-all-users-acl.md

* Updated images for all steps

* Update s3-bucket-all-users-acl.md

* Update s3-bucket-all-users-acl.md

* Apply suggestions from code review

Co-authored-by: alphadev4 <[email protected]>
  • Loading branch information
shuklaalok87 and alphadev4 authored Nov 2, 2022
1 parent 4957af5 commit 5e80278
Show file tree
Hide file tree
Showing 10 changed files with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions en/aws/s3/s3-bucket-all-users-acl.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,14 +15,14 @@
| **Recommended Action** | Disable global all users policies on all S3 buckets and ensure both the bucket ACL is configured with least privileges. |

## Detailed Remediation Steps
1. Log into the AWS Management Console.
1. Log in to the AWS Management Console.
2. Select the "Services" option and search for S3. </br> <img src="/resources/aws/s3/s3-bucket-all-users-acl/step2.png"/>
3. Scroll down the left navigation panel and choose "Buckets".</br> <img src="/resources/aws/s3/s3-bucket-logging/step3.png"/>
3. Scroll down the left navigation panel and choose "Buckets".</br> <img src="/resources/aws/s3/s3-bucket-all-users-acl/step3.png"/>
4. Select the "Bucket" that needs to be verified and click on its identifier(name) from the "Bucket name" column.</br><img src="/resources/aws/s3/s3-bucket-all-users-acl/step4.png"/>
5. Click on the "Permissions" tab on the top menu. </br><img src="/resources/aws/s3/s3-bucket-all-users-acl/step5.png"/>
6. Check the "Acess Control List" option under "Permissions" and scroll down the configuration page and check the "Public access". If "Read bucket permissions" , "Write objects" , "List objects" and "Write bucket permissions" are set to "Yes" then the selected S3 bucket allows global write, delete, or read ACL permissions. </br><img src="/resources/aws/s3/s3-bucket-all-users-acl/step6.png"/>
7. Repeat steps number 2 - 6 to verify other S3 buckets in the region. </br>
8. Select the "S3 bucket" on which global access needs to be disabled and click on the "Permissions" tab. </br><img src="/resources/aws/s3/s3-bucket-all-users-acl/step8.png"/>
9. Scroll down the "Acess Control List" configuration page and under "Public access" click on the "Everyone" and uncheck the checkboxes against "Read bucket permissions" , "Write objects" , "List objects" and "Write bucket permissions". </br><img src="/resources/aws/s3/s3-bucket-all-users-acl/step10.png"/>
10. Click on the "Save" button to make the necessary changes. </br><img src="/resources/aws/s3/s3-bucket-all-users-acl/step10.png"/>
11. Repeat steps number 8 - 10 to diable global write, delete, or read ACL permissions in other S3 buckets.</br>
6. Check the "Access Control List" option under "Permissions" and scroll down the configuration page and check the "Block public access (bucket settings)". If its status is "Off" then public access to your S3 bucket and objects is open. </br><img src="/resources/aws/s3/s3-bucket-all-users-acl/step6.png"/>
7. Scroll down to "Access control list (ACL)" and verify if the bucket allows "Everyone (public access)".</br><img src="/resources/aws/s3/s3-bucket-all-users-acl/step7.png"/>
8. If public List, Read or Write is Enabled in step 6 or 7 then disable by clicking "Edit" in "Block public access (bucket settings)" and select "Block all public access" and click "Save changes" button. </br><img src="/resources/aws/s3/s3-bucket-all-users-acl/step8.png"/>
9. In the "Edit Block public access (bucket settings)" confirmation box type "confirm" in the text box and click "Confirm" button.</br><img src="/resources/aws/s3/s3-bucket-all-users-acl/step9.png"/>
10. Scroll down to "Access control list (ACL)" and click "Edit". On the "Edit access control list (ACL)" page uncheck all checkboxes other than "Bucket owner (your AWS account)" and click on "Save changes" button.</br><img src="/resources/aws/s3/s3-bucket-all-users-acl/step10.png"/>
11. Repeat steps number 4 - 10 to disable global write, delete, or read ACL permissions in other S3 buckets.</br>
Binary file modified resources/aws/s3/s3-bucket-all-users-acl/step10.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/aws/s3/s3-bucket-all-users-acl/step2.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/aws/s3/s3-bucket-all-users-acl/step3.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/aws/s3/s3-bucket-all-users-acl/step4.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/aws/s3/s3-bucket-all-users-acl/step5.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/aws/s3/s3-bucket-all-users-acl/step6.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/aws/s3/s3-bucket-all-users-acl/step8.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified resources/aws/s3/s3-bucket-all-users-acl/step9.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 5e80278

Please sign in to comment.