Detection rules › Splunk

Detect New Open S3 buckets

Status
production
Severity
medium
Group by
"userIdentity.principalId", bucketName, permission, uri, userAgent, user_arn
Author
Bhavin Patel, Patrick Bareiss, Splunk
Source
github.com/splunk/security_content

The following analytic identifies the creation of open/public S3 buckets in AWS. It detects this activity by analyzing AWS CloudTrail events for PutBucketAcl actions where the access control list (ACL) grants permissions to all users or authenticated users. This activity is significant because open S3 buckets can expose sensitive data to unauthorized access, leading to data breaches. If confirmed malicious, an attacker could read, write, or fully control the contents of the bucket, potentially leading to data exfiltration or tampering.

Known false positives

  • While this search has no known false positives, it is possible that an AWS admin has legitimately created a public bucket for a specific purpose. That said, AWS strongly advises against granting full control to the "All Users" group.

MITRE ATT&CK coverage

TacticTechniques
Collection

Telemetry coverage

Rules detecting the same action

These rules filter on the same operation.

Rule body

name: Detect New Open S3 buckets
id: 2a9b80d3-6340-4345-b5ad-290bf3d0dac4
version: 11
creation_date: '2020-04-29'
modification_date: '2026-05-13'
author: Bhavin Patel, Patrick Bareiss, Splunk
status: production
type: TTP
description: The following analytic identifies the creation of open/public S3 buckets in AWS. It detects this activity by analyzing AWS CloudTrail events for `PutBucketAcl` actions where the access control list (ACL) grants permissions to all users or authenticated users. This activity is significant because open S3 buckets can expose sensitive data to unauthorized access, leading to data breaches. If confirmed malicious, an attacker could read, write, or fully control the contents of the bucket, potentially leading to data exfiltration or tampering.
data_source:
    - AWS CloudTrail
search: |-
    `cloudtrail` eventSource=s3.amazonaws.com eventName=PutBucketAcl
      | rex field=_raw "(?<json_field>{.+})"
      | spath input=json_field output=grantees path=requestParameters.AccessControlPolicy.AccessControlList.Grant{}
      | search grantees=*
      | mvexpand grantees
      | spath input=grantees output=uri path=Grantee.URI
      | spath input=grantees output=permission path=Permission
      | search uri IN ("http://acs.amazonaws.com/groups/global/AllUsers","http://acs.amazonaws.com/groups/global/AuthenticatedUsers")
      | search permission IN ("READ","READ_ACP","WRITE","WRITE_ACP","FULL_CONTROL")
      | rename requestParameters.bucketName AS bucketName
      | stats count min(_time) as firstTime max(_time) as lastTime
        BY user_arn userIdentity.principalId userAgent
           uri permission bucketName
      | `security_content_ctime(firstTime)`
      | `security_content_ctime(lastTime)`
      | `detect_new_open_s3_buckets_filter`
how_to_implement: You must install the AWS App for Splunk.
known_false_positives: While this search has no known false positives, it is possible that an AWS admin has legitimately created a public bucket for a specific purpose. That said, AWS strongly advises against granting full control to the "All Users" group.
references: []
finding:
    title: User $user_arn$ has created an open/public bucket $bucketName$ with the following permissions $permission$
    entity:
        field: user_arn
        type: user
        score: 50
analytic_story:
    - Suspicious AWS S3 Activities
asset_type: S3 Bucket
mitre_attack_id:
    - T1530
product:
    - Splunk Enterprise
    - Splunk Enterprise Security
    - Splunk Cloud
category: cloud
security_domain: threat

Stages and Predicates

Stage 1: search

`cloudtrail` eventSource=s3.amazonaws.com eventName=PutBucketAcl

Stage 2: rex

| rex field=_raw "(?<json_field>{.+})"

Stage 3: spath

| spath input=json_field output=grantees path=requestParameters.AccessControlPolicy.AccessControlList.Grant{}

Stage 4: search

| search grantees=*

Stage 5: mvexpand

| mvexpand grantees

Stage 6: spath

| spath input=grantees output=uri path=Grantee.URI

Stage 7: spath

| spath input=grantees output=permission path=Permission

Stage 8: search

| search uri IN ("http://acs.amazonaws.com/groups/global/AllUsers","http://acs.amazonaws.com/groups/global/AuthenticatedUsers")

Stage 9: search

| search permission IN ("READ","READ_ACP","WRITE","WRITE_ACP","FULL_CONTROL")

Stage 10: rename

| rename requestParameters.bucketName AS bucketName

Stage 11: stats

| stats count min(_time) as firstTime max(_time) as lastTime
    BY user_arn userIdentity.principalId userAgent
       uri permission bucketName

Stage 12: search

| `security_content_ctime(firstTime)`

Stage 13: search

| `security_content_ctime(lastTime)`

Stage 14: search

| `detect_new_open_s3_buckets_filter`

Indicators

These rows show field, operator, and value matches.

FieldKindValuesSearch
eventNameeq
  • PutBucketAcl
field:"aws::eventName" kind:eq value:"PutBucketAcl"
eventSourceeq
  • s3.amazonaws.com
field:"aws::eventSource" kind:eq value:"s3.amazonaws.com"
granteeseq
  • *
field:"grantees" kind:eq value:"*"
permissionin
  • "FULL_CONTROL"
  • "READ"
  • "READ_ACP"
  • "WRITE"
  • "WRITE_ACP"
field:"permission" kind:in
sourcetypeeq
  • aws:cloudtrail
field:"sourcetype" kind:eq value:"aws:cloudtrail"
uriin
  • "http://acs.amazonaws.com/groups/global/AllUsers"
  • "http://acs.amazonaws.com/groups/global/AuthenticatedUsers"
field:"uri" kind:in