AWS securityhub documentation change
Summary
Expanded documentation about cross-standard control disablement scenarios and updated instructional text
Security assessment
Clarifies existing security control management procedures without addressing specific vulnerabilities or introducing new security features. The change from 'specific' to 'only specific' standards emphasizes proper control configuration but doesn't indicate a security flaw.
Diff
diff --git a/securityhub/latest/userguide/disable-controls-across-standards.md b/securityhub/latest/userguide/disable-controls-across-standards.md index 9c0471532..4e6cd0b26 100644 --- a//securityhub/latest/userguide/disable-controls-across-standards.md +++ b//securityhub/latest/userguide/disable-controls-across-standards.md @@ -5 +5 @@ -Cross-standard disablement in multiple accounts and Regions +Cross-standard disablement in multiple accounts and RegionsCross-standard disablement in a single account and Region @@ -9 +9 @@ Cross-standard disablement in multiple accounts and Regions -We recommend disabling an AWS Security Hub Cloud Security Posture Management (CSPM) control across standards to maintain alignment throughout your organization. If you disable a control in specific standards, you continue to receive findings for the control if it is enabled in other standards. +We recommend disabling an AWS Security Hub Cloud Security Posture Management (CSPM) control across standards to maintain alignment throughout your organization. If you disable a control in only specific standards, you continue to receive findings for the control if it is enabled in other standards. @@ -25 +25 @@ If you want some accounts to configure their own controls rather than the delega -### Cross-standard disablement in a single account and Region +## Cross-standard disablement in a single account and Region @@ -27 +27 @@ If you want some accounts to configure their own controls rather than the delega -If you don't use central configuration or are a self-managed account, you can't use configuration policies to centrally disable controls in multiple accounts and Regions. However, you can use the following steps to disable a control in a single account and Region. +If you don't use central configuration or are a self-managed account, you can't use configuration policies to centrally disable controls in multiple accounts and Regions. However, you can disable a control in a single account and Region. @@ -40 +40 @@ Security Hub CSPM console - 4. Choose **Disable Control** (this option doesn't appear for a control that's already disabled). + 4. Choose **Disable Control**. This option doesn't appear for a control that's already disabled.