AWS securityhub documentation change
Summary
Removed 'AI' from SageMaker control names (SageMaker.4, SageMaker.2, SageMaker.3) to standardize terminology
Security assessment
Changes are purely terminological adjustments to control names without indicating any security vulnerability or new security guidance
Diff
diff --git a/securityhub/latest/userguide/doc-history.md b/securityhub/latest/userguide/doc-history.md index 17917857a..9cdbea2a8 100644 --- a/securityhub/latest/userguide/doc-history.md +++ b/securityhub/latest/userguide/doc-history.md @@ -118 +118 @@ Select controls available in more Regions| The following controls are now availa - * [[SageMaker.4] SageMaker AI endpoint production variants should have an initial instance count greater than 1](./sagemaker-controls.html#sagemaker-4) + * [[SageMaker.4] SageMaker endpoint production variants should have an initial instance count greater than 1](./sagemaker-controls.html#sagemaker-4) @@ -161 +161 @@ Release of CIS AWS Foundations Benchmark v3.0.0| Security Hub released [Center f - * [[SageMaker.4] SageMaker AI endpoint production variants should have an initial instance count greater than 1](./sagemaker-controls.html#sagemaker-4) + * [[SageMaker.4] SageMaker endpoint production variants should have an initial instance count greater than 1](./sagemaker-controls.html#sagemaker-4) @@ -294,2 +294,2 @@ New security controls| The following new Security Hub controls are available: - * [[SageMaker.2] SageMaker AI notebook instances should be launched in a custom VPC](./sagemaker-controls.html#sagemaker-2) - * [[SageMaker.3] Users should not have root access to SageMaker AI notebook instances](./sagemaker-controls.html#sagemaker-3) + * [[SageMaker.2] SageMaker notebook instances should be launched in a custom VPC](./sagemaker-controls.html#sagemaker-2) + * [[SageMaker.3] Users should not have root access to SageMaker notebook instances](./sagemaker-controls.html#sagemaker-3)