AWS config documentation change
Summary
Replaced 'AWS Security Hub' with 'AWS Security Hub CSPM' in the context of services creating Config rules
Security assessment
This is a branding/nomenclature update (Security Hub to Security Hub CSPM) without substantive security implications. No security vulnerabilities are mentioned, and the operational guidance remains unchanged.
Diff
diff --git a/config/latest/developerguide/select-resources.md b/config/latest/developerguide/select-resources.md index 35ca69af4..f16ae9660 100644 --- a//config/latest/developerguide/select-resources.md +++ b//config/latest/developerguide/select-resources.md @@ -142 +142 @@ If you record a global IAM resource type in at least one Region, periodic rules -To avoid unnecessary evaluations, you should only deploy AWS Config rules and conformance packs that have these global resources in scope to one of the supported Regions. For a list of which managed rules are supported in which Regions, see [List of AWS Config Managed Rules by Region Availability](https://docs.aws.amazon.com/config/latest/developerguide/managing-rules-by-region-availability.html). This applies to AWS Config rules, organizational AWS Config rules, and also rules created by other AWS services, such as AWS Security Hub and AWS Control Tower. +To avoid unnecessary evaluations, you should only deploy AWS Config rules and conformance packs that have these global resources in scope to one of the supported Regions. For a list of which managed rules are supported in which Regions, see [List of AWS Config Managed Rules by Region Availability](https://docs.aws.amazon.com/config/latest/developerguide/managing-rules-by-region-availability.html). This applies to AWS Config rules, organizational AWS Config rules, and also rules created by other AWS services, such as AWS Security Hub CSPM and AWS Control Tower.