AWS awscloudtrail: Rename S3 data events to CloudTrail S3 data events; add ExpireRestore event
Summary
Editorial rewrite of the CloudTrail S3 data events governance page: renames "Amazon S3 data events" to "CloudTrail S3 data events" throughout, collapses the long table of contents into a short bullet list, restructures the governance/security/compliance bullets, renames two governance questions ("Who read or searched this data?" → "Who accessed this data?", "Where did this data come from?" → "Who updated or created this data?"), and adds the `ExpireRestore` lifecycle event to the service-initiated events table.
Security assessment
The change is primarily terminology and structure, but it retains and re-emphasizes security guidance that CloudTrail S3 data events (GetObject, PutObject, lifecycle events, authentication failure events) are used to detect data exfiltration, destructive activity, and credential misuse, and it adds the `ExpireRestore` lifecycle event so that lifecycle-driven deletion/expiry of restored objects is auditable. No specific vulnerability, CVE, or misconfiguration fix is referenced, so it is documentation-level hardening guidance rather than a security fix.
Evidence
+ * **Secure your data** – Detect and investigate data exfiltration, destructive activity, and credential misuse.
Diff
diff --git a/awscloudtrail/latest/userguide/logging-s3-data-events-governance.md b/awscloudtrail/latest/userguide/logging-s3-data-events-governance.md index 2d176d3..0c32786 100644 --- a//awscloudtrail/latest/userguide/logging-s3-data-events-governance.md +++ b//awscloudtrail/latest/userguide/logging-s3-data-events-governance.md @@ -9 +9 @@ Amazon S3 resource types for data eventsData governance: know who uses your data -# Logging Amazon S3 data events for data governance, security, and compliance +# Logging CloudTrail S3 data events for data governance, security, and compliance @@ -13 +13 @@ Amazon S3 often stores an organization's most sensitive data, such as customer r -This section describes how you can use Amazon S3 data events to: +This section describes how you can use CloudTrail S3 data events to: @@ -15 +15 @@ This section describes how you can use Amazon S3 data events to: -Govern your data + * **Govern your data** – Know who uses your data and how it changes over its lifecycle. @@ -16,0 +17 @@ Govern your data + * **Secure your data** – Detect and investigate data exfiltration, destructive activity, and credential misuse. @@ -18 +19 @@ Govern your data -Know who uses your data and how it changes over its lifecycle. + * **Prove compliance** – Show auditors evidence of access, retention, and deletion. @@ -20 +20,0 @@ Know who uses your data and how it changes over its lifecycle. -Secure your data @@ -23,6 +22,0 @@ Secure your data -Detect and investigate data exfiltration, destructive activity, and credential misuse. - -Prove compliance - - -Show auditors evidence of access, retention, and deletion. @@ -34,35 +28 @@ By default, trails don't log data events. Additional charges apply for data even - * [Amazon S3 resource types for data events](./logging-s3-data-events-governance.html#logging-s3-data-events-resource-types) - - * [Identify who performed an action](./logging-s3-data-events-governance.html#logging-s3-data-events-identify-actor) - - * [Data governance: know who uses your data and how it changes](./logging-s3-data-events-governance.html#logging-s3-data-events-data-governance) - - * [Security: detect and investigate threats](./logging-s3-data-events-governance.html#logging-s3-data-events-security) - - * [Investigate authentication failures](./logging-s3-data-events-governance.html#logging-s3-data-events-investigate-authn-failures) - - * [Determine whether a person or a lifecycle rule deleted an object](./logging-s3-data-events-governance.html#logging-s3-data-events-who-deleted-object) - - * [Compliance: prove your controls work](./logging-s3-data-events-governance.html#logging-s3-data-events-compliance) - - * [Verify that Amazon S3 data event logging is turned on](./logging-s3-data-events-governance.html#logging-s3-data-events-verify-logging) - - * [Logging and excluding Amazon S3 lifecycle and authentication failure events](./logging-s3-data-events-governance.html#logging-s3-lifecycle-authn-events) - - * [Amazon S3 lifecycle events](./logging-s3-data-events-governance.html#logging-s3-lifecycle-events) - - * [Considerations](./logging-s3-data-events-governance.html#logging-s3-lifecycle-authn-considerations) - - * [Examples: Log Amazon S3 lifecycle and authentication failure events](./logging-s3-data-events-governance.html#logging-s3-lifecycle-authn-examples-log) - - * [Example 1: Log all Amazon S3 data events, including lifecycle and authentication failure events](./logging-s3-data-events-governance.html#logging-s3-example-log-all) - - * [Example 2: Log only lifecycle events](./logging-s3-data-events-governance.html#logging-s3-example-log-lifecycle-only) - - * [Example 3: Log only authentication failure events](./logging-s3-data-events-governance.html#logging-s3-example-log-authn-only) - - * [Example 4: Log lifecycle events for a specific bucket](./logging-s3-data-events-governance.html#logging-s3-example-log-lifecycle-one-bucket) - - * [Examples: Exclude Amazon S3 lifecycle and authentication failure events](./logging-s3-data-events-governance.html#logging-s3-lifecycle-authn-examples-exclude) - - * [Example 5: Exclude lifecycle events](./logging-s3-data-events-governance.html#logging-s3-example-exclude-lifecycle) + * Amazon S3 resource types for data events @@ -70 +30 @@ By default, trails don't log data events. Additional charges apply for data even - * [Example 6: Exclude authentication failure events](./logging-s3-data-events-governance.html#logging-s3-example-exclude-authn) + * Data governance: know who uses your data and how it changes @@ -72 +32 @@ By default, trails don't log data events. Additional charges apply for data even - * [Example 7: Exclude both lifecycle and authentication failure events](./logging-s3-data-events-governance.html#logging-s3-example-exclude-both) + * Security: detect and investigate threats @@ -74 +34 @@ By default, trails don't log data events. Additional charges apply for data even - * [Example 8: Exclude lifecycle storage class transitions only](./logging-s3-data-events-governance.html#logging-s3-example-exclude-transitions) + * Compliance: prove your controls work @@ -76 +36 @@ By default, trails don't log data events. Additional charges apply for data even - * [Exclude lifecycle events by using the console](./logging-s3-data-events-governance.html#logging-s3-example-exclude-lifecycle-console) + * Logging and excluding Amazon S3 lifecycle and authentication failure events @@ -83 +43 @@ By default, trails don't log data events. Additional charges apply for data even -To log Amazon S3 data events, specify one or more of the following values for the `resources.type` field in your trail's advanced event selectors. For the full list of resource types, see [Data events](./logging-data-events-with-cloudtrail.html#logging-data-events). +To log CloudTrail S3 data events, specify one or more of the following values for the `resources.type` field in your trail's advanced event selectors. For the full list of resource types, see [Data events](./logging-data-events-with-cloudtrail.html#logging-data-events). @@ -100 +60 @@ S3 vector bucket | `AWS::S3Vectors::VectorBucket` | Activity on vector buckets i -Each Amazon S3 data event has an `eventType` value that tells you whether a person or application performed the action, or whether Amazon S3 performed it. +Each CloudTrail S3 data event has an `eventType` value that tells you whether a person or application performed the action, or whether Amazon S3 performed it. @@ -109 +69 @@ Each Amazon S3 data event has an `eventType` value that tells you whether a pers -The following Amazon S3 data events are service-initiated (`AwsServiceEvent`) events. +The following CloudTrail S3 data events are service-initiated (`AwsServiceEvent`) events. @@ -113 +73 @@ Event source | Event names | What triggers the event -`s3lifecycle.amazonaws.com` | `ExpireObject`, `CreateDeleteMarker`, `DeleteUpload`, `TransitionObject`, `TransitionSIAObject`, `TransitionZIAObject`, `TransitionINTObject`, `TransitionGIRObject`, `TransitionGDAObject` | An Amazon S3 Lifecycle rule. For more information about Amazon S3 Lifecycle events, see Amazon S3 lifecycle events. +`s3lifecycle.amazonaws.com` | `ExpireObject`, `ExpireRestore`, `CreateDeleteMarker`, `DeleteUpload`, `TransitionObject`, `TransitionSIAObject`, `TransitionZIAObject`, `TransitionINTObject`, `TransitionGIRObject`, `TransitionGDAObject` | An Amazon S3 Lifecycle rule. For more information about Amazon S3 Lifecycle events, see Amazon S3 lifecycle events. @@ -120 +80 @@ Event source | Event names | What triggers the event -Data governance requires visibility into which principals access your critical data stores, where your data comes from, and what happens to it over time. Amazon S3 data events help you answer the following questions. +Data governance requires visibility into which principals access your critical data stores, where your data comes from, and what happens to it over time. CloudTrail S3 data events help you answer the following questions. @@ -124,2 +84,2 @@ Question | Data events that answer it -Who read or searched this data? | `GetObject`, `HeadObject`, `GetObjectAttributes`, `SelectObjectContent`, `GetObjectTorrent`, `ListObjects`, `ListObjectVersions`, `GetVectors`, `QueryVectors`, `ListVectors`, `WriteGetObjectResponse` -Where did this data come from? | `PutObject`, `CopyObject`, `CreateMultipartUpload`, `UploadPart`, `UploadPartCopy`, `CompleteMultipartUpload`, `RestoreObject`, `RenameObject`, `PutVectors` +Who accessed this data? | `GetObject`, `HeadObject`, `GetObjectAttributes`, `SelectObjectContent`, `GetObjectTorrent`, `ListObjects`, `ListObjectVersions`, `GetVectors`, `QueryVectors`, `ListVectors`, `WriteGetObjectResponse` +Who updated or created this data? | `PutObject`, `CopyObject`, `CreateMultipartUpload`, `UploadPart`, `UploadPartCopy`, `CompleteMultipartUpload`, `RestoreObject`, `RenameObject`, `PutVectors` @@ -131 +91 @@ What happened to this data over its lifecycle? | All events with the `s3lifecycl -When a security incident occurs, Amazon S3 data events show which objects were accessed, which principal accessed them, from which IP address or VPC endpoint, and at what time. Use the following events to detect and investigate common threats. +When a security incident occurs, CloudTrail S3 data events show which objects were accessed, which principal accessed them, from which IP address or VPC endpoint, and at what time. Use the following events to detect and investigate common threats. @@ -153 +113 @@ Check the `eventType` and `eventSource` fields of the event. If `eventType` is ` -Regulated industries must continuously prove who accessed what data, when, and whether that access was authorized. Amazon S3 data events provide this evidence at the API-call level, recorded by AWS rather than reported by your application. +Regulated industries must continuously prove who accessed what data, when, and whether that access was authorized. CloudTrail S3 data events provide this evidence at the API-call level, recorded by AWS rather than reported by your application. @@ -160 +120 @@ Access reviews | Read events, such as `GetObject` and `HeadObject`, on in-scope -Continuous monitoring of logging | Use AWS Config and AWS Security Hub CSPM to verify that Amazon S3 data event logging stays turned on. See the following section. +Continuous monitoring of logging | Use AWS Config and AWS Security Hub CSPM to verify that CloudTrail S3 data event logging stays turned on. See the following section. @@ -162 +122 @@ Continuous monitoring of logging | Use AWS Config and AWS Security Hub CSPM to v -### Verify that Amazon S3 data event logging is turned on +### Verify that CloudTrail S3 data event logging is turned on @@ -164 +124 @@ Continuous monitoring of logging | Use AWS Config and AWS Security Hub CSPM to v -Use the following controls to check continuously that your accounts log Amazon S3 data events: +Use the following controls to check continuously that your accounts log CloudTrail S3 data events: @@ -166 +126 @@ Use the following controls to check continuously that your accounts log Amazon S - * **AWS Config** : The [cloudtrail-s3-dataevents-enabled](https://docs.aws.amazon.com/config/latest/developerguide/cloudtrail-s3-dataevents-enabled.html) managed rule checks whether at least one trail logs Amazon S3 data events for all buckets, or for the buckets that you specify. + * **AWS Config** : The [cloudtrail-s3-dataevents-enabled](https://docs.aws.amazon.com/config/latest/developerguide/cloudtrail-s3-dataevents-enabled.html) managed rule checks whether at least one trail logs CloudTrail S3 data events for all buckets, or for the buckets that you specify. @@ -177 +137 @@ To protect the integrity of your logs, turn on log file integrity validation for -CloudTrail logs two categories of Amazon S3 data events that aren't direct requests from your principals: +CloudTrail logs two categories of CloudTrail S3 data events that aren't direct requests from your principals: @@ -192,0 +153 @@ Event name | Description | S3 server access logs operation +`ExpireRestore` | A lifecycle rule expired the temporary copy of an object that was restored from an archive storage class. | `S3.EXPIRE.RESTORE` @@ -221 +182 @@ Each lifecycle event includes the bucket name, object key, version ID, object si - * Example 1: Log all Amazon S3 data events, including lifecycle and authentication failure events + * Example 1: Log all CloudTrail S3 data events, including lifecycle and authentication failure events @@ -232 +193 @@ Each lifecycle event includes the bucket name, object key, version ID, object si -#### Example 1: Log all Amazon S3 data events, including lifecycle and authentication failure events +#### Example 1: Log all CloudTrail S3 data events, including lifecycle and authentication failure events @@ -314 +275 @@ The following AWS CLI command configures a trail to log lifecycle events for obj -If you don't need these events, you can exclude them to reduce costs while you continue to log all other Amazon S3 data events. +If you don't need these events, you can exclude them to reduce costs while you continue to log all other CloudTrail S3 data events. @@ -333 +294 @@ If you don't need these events, you can exclude them to reduce costs while you c -The following AWS CLI command configures a trail to log all Amazon S3 data events except lifecycle events. The trail continues to log all requests made by your principals. +The following AWS CLI command configures a trail to log all CloudTrail S3 data events except lifecycle events. The trail continues to log all requests made by your principals. @@ -353 +314 @@ The following AWS CLI command configures a trail to log all Amazon S3 data event -The following AWS CLI command configures a trail to log all Amazon S3 data events except authentication failure events. The trail continues to log all other Amazon S3 data events, including other failed requests such as `AccessDenied` errors. +The following AWS CLI command configures a trail to log all CloudTrail S3 data events except authentication failure events. The trail continues to log all other CloudTrail S3 data events, including other failed requests such as `AccessDenied` errors. @@ -373 +334 @@ The following AWS CLI command configures a trail to log all Amazon S3 data event -The following AWS CLI command configures a trail to log all Amazon S3 data events except lifecycle and authentication failure events. +The following AWS CLI command configures a trail to log all CloudTrail S3 data events except lifecycle and authentication failure events. @@ -393 +354 @@ The following AWS CLI command configures a trail to log all Amazon S3 data event -Storage class transitions are often the highest-volume lifecycle events. The following AWS CLI command logs all Amazon S3 data events, including lifecycle expirations, delete markers, and incomplete multipart upload cleanups, but excludes storage class transitions. The example uses two selectors: the first logs all non-lifecycle events, and the second logs lifecycle events whose names don't start with `Transition`. +Storage class transitions are often the highest-volume lifecycle events. The following AWS CLI command logs all CloudTrail S3 data events, including lifecycle expirations, delete markers, and incomplete multipart upload cleanups, but excludes storage class transitions. The example uses two selectors: the first logs all non-lifecycle events, and the second logs lifecycle events whose names don't start with `Transition`.