Amazon Web Services (AWS) S3

The Amazon Web Services (AWS) S3 integration detects a variety of data loss prevention, account misconfiguration, and user security risks in an integrated AWS account that could leave you and your organization vulnerable.

• An AWS account using AWS S3 (Simple Storage Service)
• For initial setup, access to the AWS account with permission to create a new IAM Role with the scopes listed below.

For the AWS S3 integration to function, Cloudflare CASB requires the following access scopes via an IAM Role with cross-account access:

• s3:PutBucketNotification
• s3:GetObject
• s3:ListBucket

These permissions follow the principle of least privilege to ensure that only the minimum required access is granted. To learn more about each permission scope, refer to the AWS S3 Permissions documentation ↗︎.

You can connect an AWS compute account to your CASB integration to perform Data Loss Prevention scans within your S3 bucket and avoid data egress. CASB will scan any objects that exist in the bucket at the time of configuration.

To connect a compute account to your AWS integration:

1. In Cloudflare One ↗︎, go to Cloud & SaaS findings > Integrations.
2. Find and select your AWS integration.
3. Select Open connection instructions.
4. Follow the instructions provided to connect a new compute account.
5. Select Refresh.

You can only connect one computer account to an integration. To remove a compute account, select Manage compute accounts.

Once your AWS compute account has successfully connected to your CASB integration, you can configure where and how to scan for sensitive data:

1. In Cloudflare One ↗︎, go to Integrations > Cloud & SaaS integrations.
2. Find and select your AWS integration.
3. Select Create new configuration.
4. In Resources, choose the buckets you want to scan. Select Continue.
5. Choose the file types, sampling percentage, and DLP profiles to scan for.
6. (Optional) Configure additional settings, such as the limit of API calls over time for CASB to adhere to.
7. Select Continue.
8. Review the details of the scan, then select Start scan.

CASB will take up to an hour to begin scanning. To view the scan results, go to Cloud & SaaS findings > Content Findings.

To manage your resources, go to Integrations > Cloud & SaaS integrations, then find and select your AWS integration. From here, you can pause all or individual scans, add or remove resources, and change scan settings.

For more information, refer to Content findings.

The AWS S3 integration currently scans for the following findings, or security risks. Findings are grouped by category and then ordered by severity level.

To stay up-to-date with new CASB findings as they are added, bookmark this page or subscribe to its RSS feed.

Flag security issues in S3 Buckets, including overpermissioning, access policies, and user security best practices.