S3 Block Public Access is not enabled for the account

Severity: Low
Service: S3
Check ID: S3_ACCESS_BLOCK_OFF

What this check finds

This control prevents S3 buckets from being made public. If there are no public S3 buckets in the account this should be turned on.

Passing looks like: S3 Block Public Access enabled.

How to fix it

Enable S3 Block Public Access at the account level.

AWS CLI

aws s3control put-public-access-block --account-id ACCOUNT_ID --public-access-block-configuration BlockPublicAcls=true,IgnorePublicAcls=true,BlockPublicPolicy=true,RestrictPublicBuckets=true

Names in capitals are placeholders for your own resource. Review a command before you run it.

AWS console

S3 → Block Public Access settings for this account.

Compliance controls it is evidence for

A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works

Compliance controls mapped to S3 Block Public Access is not enabled for the account
Framework	Controls
CIS AWS Foundations Benchmark v5.0.0	2.1.4 Ensure that S3 is configured with 'Block Public Access' enabled
PCI-DSS v4.0.1	1.4 Network connections between trusted and untrusted networks are controlled
SOC 2 — Trust Services Criteria	C1.2 Access Restrictions and Secure Disposal
NIST SP 800-53 Rev5 (Moderate)	AC-3 Access Enforcement SC-7 Boundary Protection
NIST Cybersecurity Framework 2.0	PR.AA-05 Access permissions and authorizations are enforced with least privilege PR.IR-01 Networks and environments are protected from unauthorized logical access and usage
ISO/IEC 27001:2022 Annex A	A.5.15 Access control A.8.3 Information access restriction A.8.20 Networks security

Checked on every scan

KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs

More S3 checks

All S3 checks