AWS Security ChangesHomeSearch

AWS security-ir: Rename case data section and update retention periods

Service: security-ir · 2026-10-08 · Documentation low

File: security-ir/latest/userguide/case-data-storage-and-movement.md

Summary

Renames "Case investigation data storage and movement" to "Case data storage and movement" throughout the page and replaces the 90-day retention statement with new retention rules: data kept for the life of the membership, deleted three years after membership cancellation/termination, and deleted one week after AWS account closure.

Security assessment

The change is a terminology rename plus a correction of data retention/residency wording (90-day retention replaced by membership-lifetime retention and deletion timelines). It affects data lifecycle and residency expectations but does not describe or fix any vulnerability, credential handling, or access control.

Evidence

+For standard AWS Regions (Regions available by default), case data stays in the Region where the case was created throughout the investigation lifecycle. Case data is retained for the life of the membership, and then deleted three years after the membership is cancelled or terminated. If the AWS account itself is closed, case data is deleted one week after account closure. 

Diff

diff --git a/security-ir/latest/userguide/case-data-storage-and-movement.md b/security-ir/latest/userguide/case-data-storage-and-movement.md
index b5fbb08..add9387 100644
--- a//security-ir/latest/userguide/case-data-storage-and-movement.md
+++ b//security-ir/latest/userguide/case-data-storage-and-movement.md
@@ -7 +7 @@
-# Case investigation data storage and movement
+# Case data storage and movement
@@ -9 +9 @@
-Case investigation data remains in the AWS Region where you open the security incident case. When you create a case in a specific Region, all logs, metadata, and case information collected for that investigation are stored in that Region. This data doesn't move to other Regions. 
+Case data remains in the AWS Region where you open the security incident case. When you create a case in a specific Region, all logs, metadata, and case information collected for that investigation are stored in that Region. This data doesn't move to other Regions. 
@@ -11 +11 @@ Case investigation data remains in the AWS Region where you open the security in
-For standard AWS Regions (Regions available by default), case investigation data stays in the Region where the case was created throughout the investigation lifecycle and the 90-day retention period. 
+For standard AWS Regions (Regions available by default), case data stays in the Region where the case was created throughout the investigation lifecycle. Case data is retained for the life of the membership, and then deleted three years after the membership is cancelled or terminated. If the AWS account itself is closed, case data is deleted one week after account closure. 
@@ -13 +13 @@ For standard AWS Regions (Regions available by default), case investigation data
-For AWS opt-in Regions (such as Middle East (Bahrain), Africa (Cape Town), or Asia Pacific (Hong Kong)), case investigation data also remains in the Region where the case was created. However, if you enable Security Incident Response in an opt-in Region, all case data from that Region automatically replicates to the US East (N. Virginia) Region (us-east-1) for centralized case management and analysis. 
+For AWS opt-in Regions (such as Middle East (Bahrain), Africa (Cape Town), or Asia Pacific (Hong Kong)), case data also remains in the Region where the case was created. However, if you enable Security Incident Response in an opt-in Region, all case data from that Region automatically replicates to the US East (N. Virginia) Region (us-east-1) for centralized case management and analysis. 
@@ -17 +17 @@ For AWS opt-in Regions (such as Middle East (Bahrain), Africa (Cape Town), or As
-If you operate in opt-in Regions, your case investigation data automatically flows to us-east-1. Organizations with strict data residency requirements must evaluate whether this cross-Region replication is compatible with their compliance obligations. Data never flows between different opt-in Regions, and data from non-opt-in Regions never replicates to opt-in Regions. 
+If you operate in opt-in Regions, your case data automatically flows to us-east-1. Organizations with strict data residency requirements must evaluate whether this cross-Region replication is compatible with their compliance obligations. Data never flows between different opt-in Regions, and data from non-opt-in Regions never replicates to opt-in Regions.