AWS Security ChangesHomeSearch

AWS whitepapers documentation change

Service: whitepapers · 2025-12-10 · Documentation low

File: whitepapers/latest/aws-security-incident-response-guide/use-logs-for-alerting.md

Summary

Changed 'AWS Security Hub' to 'AWS Security Hub CSPM' in native alerting services section

Security assessment

Simple service name update without security impact. No vulnerability fixes or new security guidance introduced.

Diff

diff --git a/whitepapers/latest/aws-security-incident-response-guide/use-logs-for-alerting.md b/whitepapers/latest/aws-security-incident-response-guide/use-logs-for-alerting.md
index 3f25d8c78..85374415f 100644
--- a//whitepapers/latest/aws-security-incident-response-guide/use-logs-for-alerting.md
+++ b//whitepapers/latest/aws-security-incident-response-guide/use-logs-for-alerting.md
@@ -7 +7 @@
-AWS natively provides alerting through security services, such as Amazon GuardDuty, [AWS Security Hub](https://aws.amazon.com/security-hub/), and AWS Config. You can also use custom alert generation engines for security alerts not covered by these services or for specific alerts relevant to your environment. Building these alerts and detections is covered in the section called [Detection](./detection.html) in this document. 
+AWS natively provides alerting through security services, such as Amazon GuardDuty, [AWS Security Hub CSPM](https://aws.amazon.com/security-hub/), and AWS Config. You can also use custom alert generation engines for security alerts not covered by these services or for specific alerts relevant to your environment. Building these alerts and detections is covered in the section called [Detection](./detection.html) in this document.