AWS securityagent documentation change
Summary
Updated geographic data processing description from 'within the United States' to 'within the same geographic region' for consistency with other documentation.
Security assessment
This change aligns data processing language with other documentation files. It clarifies geographic data residency but doesn't address a security vulnerability. The change appears to be for consistency and accuracy in security guidance documentation.
Diff
diff --git a/securityagent/latest/userguide/security-guidance.md b/securityagent/latest/userguide/security-guidance.md index 2fab6afa7..a32940fe9 100644 --- a//securityagent/latest/userguide/security-guidance.md +++ b//securityagent/latest/userguide/security-guidance.md @@ -49 +49 @@ AWS Security Agent is instructed to discover security risks, but to do so using -AWS Security Agent allows users to upload artifacts to provide context about their application being tested. For more information on data protection, see [Data protection in AWS Security Agent](./data-protection.html). AWS Security Agent uses Amazon Bedrock’s geographic [cross-region inference](https://docs.aws.amazon.com/securityagent/latest/userguide/security-best-practices.html#_cross_region_inference.html) to increase throughput while keeping data processing within the United States. At launch, AWS Security Agent is deployed in the US East (N. Virginia) region only. +AWS Security Agent allows users to upload artifacts to provide context about their application being tested. For more information on data protection, see [Data protection in AWS Security Agent](./data-protection.html). AWS Security Agent uses Amazon Bedrock’s geographic [cross-region inference](https://docs.aws.amazon.com/securityagent/latest/userguide/security-best-practices.html#_cross_region_inference.html) to increase throughput while keeping data processing within the same geographic region.