AWS security-ir documentation change
Summary
Updated terminology from 'all accounts' to 'covered accounts' regarding monitoring scope
Security assessment
Clarifies monitoring applies only to covered accounts rather than all accounts, improving documentation accuracy but not addressing a specific security vulnerability or introducing new security features.
Diff
diff --git a/security-ir/latest/userguide/setup-monitoring-and-investigation-workflows.md b/security-ir/latest/userguide/setup-monitoring-and-investigation-workflows.md index 53a145784..118d13234 100644 --- a//security-ir/latest/userguide/setup-monitoring-and-investigation-workflows.md +++ b//security-ir/latest/userguide/setup-monitoring-and-investigation-workflows.md @@ -13 +13 @@ If you experience any onboarding issues, then please [ create an AWS Support cas -This feature enables AWS Security Incident Response to monitor and investigate findings across all accounts and active supported AWS Regions in your organization. To facilitate this functionality, AWS Security Incident Response automatically creates a service-linked role in all member accounts within your AWS Organizations. However, for the management account, you must manually create the service-linked role to enable monitoring. +This feature enables AWS Security Incident Response to monitor and investigate findings across all covered accounts and active supported AWS Regions in your organization. To facilitate this functionality, AWS Security Incident Response automatically creates a service-linked role in all covered member accounts within your AWS Organizations. However, for the management account, you must manually create the service-linked role to enable monitoring.