AWS whitepapers documentation change
Summary
Updated Security Hub reference to 'Security Hub CSPM' in detective controls section
Security assessment
Specifies CSPM capabilities without evidence of security fixes. Enhances documentation of threat detection features but doesn't mitigate vulnerabilities.
Diff
diff --git a/whitepapers/latest/aws-caf-security-perspective/threat-detection.md b/whitepapers/latest/aws-caf-security-perspective/threat-detection.md index fba997e23..34fd45bc2 100644 --- a//whitepapers/latest/aws-caf-security-perspective/threat-detection.md +++ b//whitepapers/latest/aws-caf-security-perspective/threat-detection.md @@ -48 +48 @@ When creating _directive_ , _preventative_ , _detective_ , and _responsive_ cont -Enabling detective controls on an AWS account or across AWS Organizations should be carefully planned with scaling in mind. Use AWS Organizations functionalities built-in to [AWS Security Services](https://aws.amazon.com/products/security/) such as Amazon GuardDuty, AWS Config, and AWS Security Hub. This will provide the security teams the visibility into the services' functionality into each account, permitting them to audit their detection capabilities. Organizations should plan for how custom controls can be deployed and audited at scale, and provide teams the ability to audit those controls. +Enabling detective controls on an AWS account or across AWS Organizations should be carefully planned with scaling in mind. Use AWS Organizations functionalities built-in to [AWS Security Services](https://aws.amazon.com/products/security/) such as Amazon GuardDuty, AWS Config, and AWS Security Hub CSPM. This will provide the security teams the visibility into the services' functionality into each account, permitting them to audit their detection capabilities. Organizations should plan for how custom controls can be deployed and audited at scale, and provide teams the ability to audit those controls.