AWS solutions documentation change
Summary
Updated instructions for enabling playbooks based on Security Hub's consolidated control findings feature, including clarification about default behavior for new deployments after February 23, 2023.
Security assessment
The change provides updated operational guidance about Security Hub configuration but doesn't address any specific vulnerability or weakness. It clarifies deployment instructions without security implications.
Diff
diff --git a/solutions/latest/automated-security-response-on-aws/deploy-the-solution.md b/solutions/latest/automated-security-response-on-aws/deploy-the-solution.md index fe67e2be2..b690faa73 100644 --- a//solutions/latest/automated-security-response-on-aws/deploy-the-solution.md +++ b//solutions/latest/automated-security-response-on-aws/deploy-the-solution.md @@ -9 +9 @@ -If the [consolidated control findings](./deciding-where-to-deploy-each-stack.html#consolidated-controls-findings) feature is turned on in Security Hub (**this is default in new deployments**), only enable the Security Control (CS) playbook **when deploying this solution**. If the feature is not turned on, **only** enable the playbooks for the security standards that are enabled in Security Hub. Enabling additional playbooks can result in reaching the [quota for EventBridge Rules](./.html#amazon-eventbridge-rules-quotas). +If the [consolidated control findings](./deciding-where-to-deploy-each-stack.html#consolidated-controls-findings) feature is turned on in Security Hub, only enable the Security Control (SC) playbook when deploying this solution. If the feature is not turned on, **only** enable the playbooks for the security standards that are enabled in Security Hub. Consolidated control findings is enabled by default if you enable Security Hub CSPM on or after February 23, 2023.