More Info:

S3 buckets should not allow READ access to AWS authenticated users through ACLs n order to protect your S3 data against unauthorized access.

Risk Level

Medium

Address

Security

Compliance Standards

CBP, AWSWAF, PCIDSS, NIST

Triage and Remediation

Remediation

Sure, here are the step-by-step instructions to remediate the issue in AWS:

  1. Log in to the AWS Management Console and navigate to the S3 service.

  2. Select the S3 bucket that is allowing READ access to authenticated users.

  3. Click on the “Permissions” tab and then click on “Bucket Policy”.

  4. In the Bucket Policy Editor, remove any statements that allow authenticated users to read from the bucket.

  5. You can use the following policy to deny read access to authenticated users:

{
    "Version": "2012-10-17",
    "Id": "DenyReadAccessToAuthenticatedUsers",
    "Statement": [
        {
            "Sid": "DenyReadAccess",
            "Effect": "Deny",
            "Principal": {
                "AWS": [
                    "*"
                ]
            },
            "Action": [
                "s3:GetObject",
                "s3:GetObjectVersion"
            ],
            "Resource": [
                "arn:aws:s3:::bucket-name/*"
            ],
            "Condition": {
                "StringEquals": {
                    "aws:PrincipalType": "AuthenticatedUser"
                }
            }
        }
    ]
}
  1. Replace “bucket-name” with the name of your S3 bucket.

  2. Click on the “Save” button to apply the new policy.

  3. Verify that the policy has been applied correctly by attempting to access the S3 bucket as an authenticated user. You should receive an error message indicating that you do not have permission to access the bucket.

That’s it! You have successfully remediated the misconfiguration in AWS S3 bucket.

Additional Reading: