Rule: S3 Buckets should Prohibit Public Read Access
This rule ensures that S3 buckets restrict public read access for improved security.
| Rule | S3 buckets should prohibit public read access |
| Framework | NIST 800-171 Revision 2 |
| Severity | ✔ Medium |
Rule Description
The rule requires that all S3 buckets should prohibit public read access in accordance with the guidelines outlined in NIST 800-171 Revision 2. This is to ensure the security and integrity of sensitive data stored in S3 buckets.
Troubleshooting Steps
If the S3 bucket allows public read access, unauthorized users may be able to access and retrieve sensitive data, which can lead to data breaches and privacy violations. It is important to verify that the S3 bucket configuration prohibits public access to prevent such issues.
Necessary Codes
There are no specific codes required to implement this rule, as it involves configuring the S3 bucket settings.
Step-by-Step Guide for Remediation
Step 1: Access AWS Management Console
- Go to the AWS Management Console and sign in using appropriate credentials.
Step 2: Navigate to S3 Buckets
- Select the S3 service from the list of available services.
Step 3: Select the targeted Bucket
- Locate and select the specific S3 bucket you want to configure.
Step 4: Access Permissions Configuration
- Click on the "Permissions" tab to access the bucket's permissions configuration.
Step 5: Edit Public Access Settings
- In the "Public access settings" section, click on "Edit."
Step 6: Disable Public Access
- Review the listed configurations to ensure the bucket prohibits public access.
- Disable any public access settings that allow public read access.
Step 7: Save Changes
- After making the necessary changes, click on "Save changes" to apply the new bucket configuration.
Conclusion
By following the step-by-step guide, you can ensure that S3 buckets comply with the policy of prohibiting public read access as mandated by NIST 800-171 Revision 2. This will help safeguard sensitive data and prevent unauthorized access.