42 of 50 in All Controls
aws

Enable GuardDuty S3 Protection

IDAWS-SEC-003
Severity
high
Automation
Auto
Category
security
Enforcementmandatory
Complexity / Impact
low(none impact)
Risk Profile
medium likelihood(low residual)
Cloud Scopeaws:root
Environments
all
Target Resources
AWS::GuardDuty::DetectorAWS::S3::Bucket
Services
guarddutys3organizations
Tags
threat-detectionguarddutys3data-protectionlanding-zone
Frameworks
NIST 800-53ISO 27001PCI DSSSOC 2AWS FSBP
Depends On
Governance
Cloud Security (quarterly)
Created
2026-05-03
Last Updated
2026-11-20

Specification & Description

Enable Amazon GuardDuty S3 Protection (S3_DATA_EVENTS) across all AWS Organizations member accounts from the Security delegated administrator account to detect suspicious S3 data access and exfiltration activity.

Technical Specifications

GuardDuty S3 Protection inspects CloudTrail S3 data events directly through AWS internal service integration without requiring customer-managed CloudTrail S3 data event selectors on your trails. It detects anomalous object access, bucket policy tampering, Tor or malicious IP access, and discovery activity such as Discovery:S3/BucketEnumeration.Listing.

Enabling the S3_DATA_EVENTS feature with AutoEnable = ALL in the GuardDuty delegated administrator account applies S3 Protection to both existing and future organization member accounts.

Security Rationale

S3 buckets frequently store backups, logs, and sensitive application data. Standard management-event monitoring only captures control-plane API calls like PutBucketPolicy, leaving data-plane operations such as GetObject and ListObjectsV2 invisible unless GuardDuty S3 Protection or targeted data event logging is active.

Business & Security Impact

Without GuardDuty S3 Protection, unauthorized object reads, bulk downloads, or anomalous S3 data-plane activity from compromised credentials can go undetected across workload accounts.

Operational & Implementation Notes

GuardDuty S3 Protection consumes CloudTrail S3 data events directly through AWS internal telemetry and does not depend on enabling CloudTrail data event selectors in member accounts. For S3 access logging cost guardrails, align with AWS-LOG-002.

Compliance Framework Mappings (5)

Regulatory baselines and industry standards mapped to this control specification.

Beta
Framework / StandardMapped Requirements & ControlsControls
NIST 800-53 Rev 5NIST 800-53
SI-4SC-7
2
ISO 27001:2022ISO 27001
A.8.16
1
PCI DSS v4.0PCI DSS
11.5.2
1
SOC 2SOC 2
CC7.2
1
AWS Foundational Security Best PracticesAWS FSBP
GuardDuty.10
1

* Compliance framework mappings are provided for informational architectural reference. Always verify control alignment against your organization's formal audit requirements.

Automated Detection & Rule Logic

Detection Engine: aws-api • Automated: Yes

Query the GuardDuty delegated administrator detector and organization configuration in each operational region to confirm S3_DATA_EVENTS is ENABLED on the administrator detector and AutoEnable is ALL for the organization.

AWS CLI: Verify GuardDuty S3_DATA_EVENTS Status and Org Auto-Enablebash
DETECTOR_ID=$(aws guardduty list-detectors \
  --region "$HOME_REGION" \
  --query "DetectorIds[0]" \
  --output text)

aws guardduty describe-organization-configuration \
  --detector-id "$DETECTOR_ID" \
  --region "$HOME_REGION" \
  --query "Features[?Name=='S3_DATA_EVENTS'].{Name:Name,AutoEnable:AutoEnable}" \
  --output json

aws guardduty get-detector \
  --detector-id "$DETECTOR_ID" \
  --region "$HOME_REGION" \
  --query "Features[?Name=='S3_DATA_EVENTS'].{Name:Name,Status:Status}" \
  --output json

Remediation Guide & Automation

In the GuardDuty delegated administrator (Security) account, enable the `S3_DATA_EVENTS` feature on the administrator detector and set organization auto-enablement to `ALL` so every existing and new member account receives S3 Protection automatically.

Step-by-Step Instructions

  1. In the GuardDuty delegated administrator (Security) account, enable the S3_DATA_EVENTS feature on the administrator detector.
  2. Update the GuardDuty organization configuration with S3_DATA_EVENTS AutoEnable set to ALL to cover both existing and newly joined accounts.
  3. Repeat across all active AWS regions where S3 buckets or member workloads operate.
  4. Route GuardDuty S3 findings to Security Hub and the central SIEM or incident response queue.
AWS CLI: Enable GuardDuty S3 Protection for Organizationbash
# Run in the GuardDuty Delegated Administrator (Security) account
DETECTOR_ID=$(aws guardduty list-detectors \
  --region "$HOME_REGION" \
  --query "DetectorIds[0]" \
  --output text)

aws guardduty update-detector \
  --detector-id "$DETECTOR_ID" \
  --features Name=S3_DATA_EVENTS,Status=ENABLED \
  --region "$HOME_REGION"

aws guardduty update-organization-configuration \
  --detector-id "$DETECTOR_ID" \
  --auto-enable-organization-members ALL \
  --features Name=S3_DATA_EVENTS,AutoEnable=ALL \
  --region "$HOME_REGION"
Terraform: Enable GuardDuty S3 Protection Featurehcl
variable "guardduty_detector_id" {
  type        = string
  description = "GuardDuty detector ID in the Security delegated administrator account."
}

resource "aws_guardduty_detector_feature" "s3_protection" {
  detector_id = var.guardduty_detector_id
  name        = "S3_DATA_EVENTS"
  status      = "ENABLED"
}

resource "aws_guardduty_organization_configuration_feature" "s3_protection" {
  detector_id = var.guardduty_detector_id
  name        = "S3_DATA_EVENTS"
  auto_enable = "ALL"

  depends_on = [aws_guardduty_detector_feature.s3_protection]
}

We value your privacy

We use analytics cookies to understand how visitors interact with our site and to improve the user experience. You can choose to accept or decline these cookies.