AWS solutions documentation change
Summary
Updated deployment instructions for security automation stacks when using consolidated control findings
Security assessment
Clarifies security control implementation requirements but does not address specific vulnerabilities. Focuses on proper security automation setup.
Diff
diff --git a/solutions/latest/automated-security-response-on-aws/deciding-where-to-deploy-each-stack.md b/solutions/latest/automated-security-response-on-aws/deciding-where-to-deploy-each-stack.md index 582c15f3e..66abbaecb 100644 --- a//solutions/latest/automated-security-response-on-aws/deciding-where-to-deploy-each-stack.md +++ b//solutions/latest/automated-security-response-on-aws/deciding-where-to-deploy-each-stack.md @@ -69 +69 @@ The accounts in your organization can be configured with the consolidated contro -If enabled, you must use v2.0.0 of the solution or later. In addition, you must deploy both the Admin and Member nested stacks for the "SC" or "security control" standards. This deploys the automation documents and EventBridge rules for use with the consolidated control IDs generated when this feature is turned on. There is no need to deploy the Admin or Member nested stacks for specific standards (e.g. AWS FSBP) when using this feature. +When this feature is enabled, you must use solution version 2.0.0 or later and enable the "SC" (Security Control) playbook in both the Admin and Member stacks. These stacks deploy the automation documents needed to work with consolidated control IDs. You do not need to deploy stacks for individual standards (such as AWS FSBP) when using consolidated control findings.