Amazon S3 Protection in Amazon GuardDuty
S3 protection enables Amazon GuardDuty to monitor object-level API operations to identify potential security risks for data within your S3 buckets.
GuardDuty monitors threats against your Amazon S3 resources by analyzing Amazon CloudTrail management
events and CloudTrail S3 data events. These data sources monitor different kinds of activity, for
example, CloudTrail management events for S3 include operations that list or configure S3
buckets, such as ListBuckets
, DeleteBuckets
, and
PutBucketReplication
. Examples of data events for S3 include object-level
API operations, such as GetObject
, ListObjects
,
DeleteObject
, and PutObject
.
GuardDuty monitoring of CloudTrail management events is on by default for all accounts that have enabled GuardDuty and is not configurable. CloudTrail S3 data event logs are a configurable data source in GuardDuty. By default, S3 protection is enabled for new detectors, for accounts created before the addition of S3 protection this data source must be enabled manually. The processes for enabling or disabling S3 data event monitoring is covered in this topic.
We strongly recommend that you enable S3 protection in GuardDuty. If the feature is disabled, GuardDuty is unable to fully monitor or generate findings for suspicious access to data stored in your S3 buckets.
How GuardDuty uses S3 data events
The S3 protection feature in GuardDuty refers to whether S3 data events are enabled as a data source for GuardDuty. When S3 data event monitoring is enabled GuardDuty immediately begins to analyze S3 data events from all of your S3 buckets and monitor them for malicious and suspicious activity. For more information, see How Amazon GuardDuty uses its data sources.
GuardDuty does not process requests to objects that you have made publicly accessible, but it does alert you when a bucket is made publicly accessible. When GuardDuty detects a threat based on S3 data event monitoring, it generates a security finding. For information about the types of findings GuardDuty can generate for Amazon S3 see GuardDuty S3 finding types.
If you disable S3 protection, GuardDuty immediately stops consuming this data source and stops monitoring access to data stored in your S3 buckets.
Configuring S3 protection for a standalone account
For accounts associated by Amazon Organizations, this process can be automated through console settings as described in the next section.
Accounts that were using GuardDuty before the addition of S3 protection can enable the new
data source by configuring GuardDuty through the console or the UpdateDetector
API operation.
To configure Amazon S3 data events as a data source for your account, see the following configuration options.
To enable or disable S3 protection
Choose your access method below for instructions on enabling or disabling S3 protection for a standalone account.
Configuring S3 protection in multiple-account environments
In a multi-account environment, only GuardDuty administrator accounts can configure S3 protection. GuardDuty administrator accounts can enable or disable S3 protection for their member accounts. GuardDuty member accounts cannot enable or disable this data source.
GuardDuty administrator accounts that manage their member accounts with Amazon Organizations support can choose to have S3 protection automatically enabled on all new accounts in the organization. For more information, see Managing GuardDuty accounts with Amazon Organizations.
Automatically enabling S3 protection for Organization member accounts
This functionality is only available to administrators of GuardDuty members incorporated through Amazon Organizations.
-
Use your administrator account to perform this step.
Open the GuardDuty console at https://console.amazonaws.cn/guardduty/
. -
In the navigation pane, under Settings, choose Accounts.
-
Ensure Auto-enable for GuardDuty is turned on. If it is off, you can enable by selecting Enable from the banner or by selecting Auto-enable is OFF. This feature will automatically enable GuardDuty for new member accounts within your organization and must be enabled in order to auto-enable S3 protection.
-
Once Auto-enable for GuardDuty is on, you can enable S3 protection for your new members in addition to enabling GuardDuty by selecting the S3 Protection toggle icon. Choose Update Settings to confirm.
To selectively enable or disable S3 protection in member accounts
Choose your access method below for instructions on enabling or disabling S3 protection for member accounts.
Automatically disabling S3 protection for new GuardDuty accounts
By default, S3 protection is enabled automatically for new detectors.
If you are a GuardDuty administrator enabling GuardDuty for the first time on a new account, and you
do not want S3 protection enabled by default, you can disable it by modifying the createDetector API operation with the optional
dataSources
object. The following example uses the Amazon CLI to enable a
new GuardDuty detector with the S3 protection disabled.
aws guardduty create-detector --enable --data-sources '{"S3Logs":{"Enable":false}}'