AWS securityhub documentation change
Summary
Added entry about removing RDS.18 control from standards due to EC2-Classic retirement
Security assessment
Documents removal of obsolete security control but does not address an active security vulnerability
Diff
diff --git a/securityhub/latest/userguide/doc-history.md index 3e41af89e..be53e0a4d 100644 --- a/securityhub/latest/userguide/doc-history.md +++ b/securityhub/latest/userguide/doc-history.md @@ -7 +7 @@ -The following table describes the important changes to the documentation since the last release of AWS Security Hub. For security control releases, the date specifies when the controls begin to be available in supported AWS Regions. It can take 1–2 weeks for controls to be available in all supported Regions. +The following table describes the important changes to the documentation since the last release of AWS Security Hub. For releases of new security controls, the date specifies when the controls begin to be available in supported AWS Regions. It can take 1‐2 weeks for controls to be available in all supported Regions. @@ -12,0 +13 @@ Change| Description| Date +Updates to security standards and controls| We removed the [RDS.18 security control](https://docs.aws.amazon.com/securityhub/latest/userguide/rds-controls.html#rds-18) from the AWS Foundational Security Best Practices v1.0.0 standard and automated checks for NIST SP 800-53 Rev. 5 requirements. Since Amazon EC2-Classic networking was retired, Amazon Relational Database Service (Amazon RDS) instances can no longer be deployed outside a VPC. The control continues to be part of the [AWS Control Tower service-managed standard](https://docs.aws.amazon.com/securityhub/latest/userguide/service-managed-standard-aws-control-tower.html).| March 7, 2025