AWS systems-manager documentation change
Summary
Replaced references to 'AWS Security Hub' with 'AWS Security Hub CSPM' in patch compliance monitoring context.
Security assessment
Consistency update for service naming. The security functionality (monitoring patch compliance) remains unchanged with no vulnerability fixes mentioned.
Diff
diff --git a/systems-manager/latest/userguide/patch-manager-find-noncompliant-nodes.md b/systems-manager/latest/userguide/patch-manager-find-noncompliant-nodes.md index f83a1f19c..c7a2f259f 100644 --- a//systems-manager/latest/userguide/patch-manager-find-noncompliant-nodes.md +++ b//systems-manager/latest/userguide/patch-manager-find-noncompliant-nodes.md @@ -15 +15 @@ There are two SSM documents that are used to identify or update noncompliant man -Patch compliance data from Patch Manager can be sent to AWS Security Hub. Security Hub gives you a comprehensive view of your high-priority security alerts and compliance status. It also monitors the patching status of your fleet. For more information, see [Integrating Patch Manager with AWS Security Hub](./patch-manager-security-hub-integration.html). +Patch compliance data from Patch Manager can be sent to AWS Security Hub CSPM. Security Hub CSPM gives you a comprehensive view of your high-priority security alerts and compliance status. It also monitors the patching status of your fleet. For more information, see [Integrating Patch Manager with AWS Security Hub CSPM](./patch-manager-security-hub-integration.html).