AWS securityhub documentation change
Summary
Updated documentation to reflect rebranding from 'Security Hub' to 'Security Hub CSPM' (Cloud Security Posture Management) throughout the document, including console/API references and conceptual explanations
Security assessment
The changes primarily update branding/naming conventions to emphasize CSPM (Cloud Security Posture Management) capabilities. While CSPM is a security-related feature, there's no evidence this change addresses a specific security vulnerability. The updates enhance documentation clarity about existing security posture management features but don't introduce new security content or fix vulnerabilities.
Diff
diff --git a/securityhub/latest/userguide/securityhub-standards-enable-disable-controls.md b/securityhub/latest/userguide/securityhub-standards-enable-disable-controls.md index 07bab1183..37696b6d3 100644 --- a//securityhub/latest/userguide/securityhub-standards-enable-disable-controls.md +++ b//securityhub/latest/userguide/securityhub-standards-enable-disable-controls.md @@ -3 +3 @@ -[Documentation](/index.html)[AWS Security Hub](/securityhub/index.html)[User Guide](what-is-securityhub.html) +[Documentation](/index.html)[AWS Security Hub](/securityhub/index.html)[ User Guide ](what-is-security-hub-adv.html) @@ -5 +5 @@ -# Enabling controls in Security Hub +# Enabling controls in Security Hub CSPM @@ -7 +7 @@ -In AWS Security Hub, a control is a safeguard within a security standard that helps an organization protect the confidentiality, integrity, and availability of its information. Each Security Hub control is related to a specific AWS resource. When you enable a control, Security Hub begins to run security checks for the control and generates findings for it. Security Hub also considers all enabled controls when calculating security scores. +In AWS Security Hub Cloud Security Posture Management (CSPM), a control is a safeguard within a security standard that helps an organization protect the confidentiality, integrity, and availability of its information. Each Security Hub CSPM control is related to a specific AWS resource. When you enable a control, Security Hub CSPM begins to run security checks for the control and generates findings for it. Security Hub CSPM also considers all enabled controls when calculating security scores. @@ -11 +11 @@ You can choose to enable a control across all of the security standards that it -If you enable cross-Region aggregation and sign in to an aggregation Region, the Security Hub console shows controls that are available in at least one linked Region. If a control is available in a linked Region but not in the aggregation Region, you can't enable or disable that control from the aggregation Region. +If you enable cross-Region aggregation and sign in to an aggregation Region, the Security Hub CSPM console shows controls that are available in at least one linked Region. If a control is available in a linked Region but not in the aggregation Region, you can't enable or disable that control from the aggregation Region. @@ -13 +13 @@ If you enable cross-Region aggregation and sign in to an aggregation Region, the -You can enable and disable controls in each Region by using the Security Hub console, Security Hub API, or AWS CLI. +You can enable and disable controls in each Region by using the Security Hub CSPM console, Security Hub CSPM API, or AWS CLI. @@ -15 +15 @@ You can enable and disable controls in each Region by using the Security Hub con -The instructions for enabling and disabling controls vary based on whether or not you use [central configuration](./central-configuration-intro.html). This topic describes the differences. Central configuration is available to users who integrate Security Hub and AWS Organizations. We recommend using central configuration to simplify the process of enabling and disabling controls in multi-account, multi-Region environments. If you use central configuration, you can enable a control across multiple accounts and Regions through the use of configuration policies. If you don't use central configuration, you must enable a control separately in each Region and account. +The instructions for enabling and disabling controls vary based on whether or not you use [central configuration](./central-configuration-intro.html). This topic describes the differences. Central configuration is available to users who integrate Security Hub CSPM and AWS Organizations. We recommend using central configuration to simplify the process of enabling and disabling controls in multi-account, multi-Region environments. If you use central configuration, you can enable a control across multiple accounts and Regions through the use of configuration policies. If you don't use central configuration, you must enable a control separately in each Region and account.