AWS securityhub medium security documentation change
Summary
Removed documentation for SageMaker controls 9-15 related to inter-container encryption and network isolation requirements for various SageMaker job types
Security assessment
The removed controls specifically addressed encryption of data-in-transit (Protect > Data Protection) and secure network configurations - critical security protections for sensitive ML data and processing environments. Deleting these controls removes guidance about preventing data exfiltration, unauthorized access, and encrypting inter-container communications.
Diff
diff --git a/securityhub/latest/userguide/sagemaker-controls.md b/securityhub/latest/userguide/sagemaker-controls.md index 1cef0104d..3e5277bc7 100644 --- a//securityhub/latest/userguide/sagemaker-controls.md +++ b//securityhub/latest/userguide/sagemaker-controls.md @@ -5 +5 @@ -[SageMaker.1] Amazon SageMaker notebook instances should not have direct internet access[SageMaker.2] SageMaker notebook instances should be launched in a custom VPC[SageMaker.3] Users should not have root access to SageMaker notebook instances[SageMaker.4] SageMaker endpoint production variants should have an initial instance count greater than 1[SageMaker.5] SageMaker models should have network isolation enabled[SageMaker.6] SageMaker app image configurations should be tagged[SageMaker.7] SageMaker images should be tagged[SageMaker.8] SageMaker notebook instances should run on supported platforms[SageMaker.9] SageMaker data quality job definitions should have inter-container traffic encryption enabled[SageMaker.10] SageMaker model explainability job definitions should have inter-container traffic encryption enabled[SageMaker.11] SageMaker data quality job definitions should have network isolation enabled[SageMaker.12] SageMaker model bias job definitions should have network isolation enabled[SageMaker.13] SageMaker model quality job definitions should have inter-container traffic encryption enabled[SageMaker.14] SageMaker monitoring schedules should have network isolation enabled[SageMaker.15] SageMaker model bias job definitions should have inter-container traffic encryption enabled +[SageMaker.1] Amazon SageMaker notebook instances should not have direct internet access[SageMaker.2] SageMaker notebook instances should be launched in a custom VPC[SageMaker.3] Users should not have root access to SageMaker notebook instances[SageMaker.4] SageMaker endpoint production variants should have an initial instance count greater than 1[SageMaker.5] SageMaker models should have network isolation enabled[SageMaker.6] SageMaker app image configurations should be tagged[SageMaker.7] SageMaker images should be tagged[SageMaker.8] SageMaker notebook instances should run on supported platforms @@ -224,154 +223,0 @@ For information about the platforms that Amazon SageMaker AI currently supports -## [SageMaker.9] SageMaker data quality job definitions should have inter-container traffic encryption enabled - -**Category:** Protect > Data Protection > Encryption of data-in-transit - -**Severity:** Medium - -**Resource type:** `AWS::SageMaker::DataQualityJobDefinition` - -**AWS Config rule:** [sagemaker-data-quality-job-encrypt-in-transit](https://docs.aws.amazon.com/config/latest/developerguide/sagemaker-data-quality-job-encrypt-in-transit.html) - -**Schedule type:** Change triggered - -**Parameters:** None - -This control checks whether an Amazon SageMaker AI data quality job definition has encryption enabled for inter-container traffic. The control fails if the definition for a job that monitors data quality and drift does not have encryption enabled for inter-container traffic. - -Enabling inter-container traffic encryption protects sensitive ML data during distributed processing for data quality analysis. - -### Remediation - -For more information about inter-container traffic encryption for Amazon SageMaker AI, see [Protect Communications Between ML Compute Instances in a Distributed Training Job](https://docs.aws.amazon.com/sagemaker/latest/dg/train-encrypt.html) in the _Amazon SageMaker AI Developer Guide_. When you create a data quality job definition, you can enable inter-container traffic encryption by setting the value for the `EnableInterContainerTrafficEncryption` parameter to `True`. - -## [SageMaker.10] SageMaker model explainability job definitions should have inter-container traffic encryption enabled - -**Category:** Protect > Data Protection > Encryption of data-in-transit - -**Severity:** Medium - -**Resource type:** `AWS::SageMaker::ModelExplainabilityJobDefinition` - -**AWS Config rule:** [sagemaker-model-explainability-job-encrypt-in-transit](https://docs.aws.amazon.com/config/latest/developerguide/sagemaker-model-explainability-job-encrypt-in-transit.html) - -**Schedule type:** Change triggered - -**Parameters:** None - -This control checks whether an Amazon SageMaker model explainability job definition has inter-container traffic encryption enabled. The control fails if the model explainability job definition does not have inter-container traffic encryption enabled. - -Enabling inter-container traffic encryption protects sensitive ML data such as model data, training datasets, intermediate processing results, parameters and model weights during distributed processing for explainability analysis. - -### Remediation - -For an existing SageMaker model explainability job definition, inter-container traffic encryption cannot be updated in place. To create a new SageMaker model explainability job definition with inter-container traffic encryption enabled, use [API](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_CreateModelExplainabilityJobDefinition.html) or [CLI](https://docs.aws.amazon.com/cli/latest/reference/sagemaker/create-model-explainability-job-definition.html) or [ CloudFormation](https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-resource-sagemaker-modelexplainabilityjobdefinition.html) and set [`EnableInterContainerTrafficEncryption`](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_MonitoringNetworkConfig.html#API_MonitoringNetworkConfig_Contents) to `True`. - -## [SageMaker.11] SageMaker data quality job definitions should have network isolation enabled - -**Category:** Protect > Secure network configuration - -**Severity:** Medium - -**Resource type:** `AWS::SageMaker::DataQualityJobDefinition` - -**AWS Config rule:** [sagemaker-data-quality-job-isolation](https://docs.aws.amazon.com/config/latest/developerguide/sagemaker-data-quality-job-isolation.html) - -**Schedule type:** Change triggered - -**Parameters:** None - -This control checks whether an Amazon SageMaker AI data quality monitoring job definition has network isolation enabled. The control fails if the definition for a job that monitors data quality and drift has network isolation disabled. - -Network isolation reduces the attack. surface and prevents external access thereby protecting against unauthorized external access, accidental data exposure and potential data exfiltration. - -### Remediation - -For more information about network isolation for SageMaker AI, see [Run training and inference containers in internet-free mode](https://docs.aws.amazon.com/sagemaker/latest/dg/mkt-algo-model-internet-free.html) in the _Amazon SageMaker AI Developer Guide_. When you create a data quality job definition, you can enable network isolation by setting the value for the `EnableNetworkIsolation` parameter to `True`. - -## [SageMaker.12] SageMaker model bias job definitions should have network isolation enabled - -**Category:** Protect > Secure network configuration > Resources policy configuration - -**Severity:** Medium - -**Resource type:** `AWS::SageMaker::ModelBiasJobDefinition` - -**AWS Config rule:** [sagemaker-model-bias-job-isolation](https://docs.aws.amazon.com/config/latest/developerguide/sagemaker-model-bias-job-isolation.html) - -**Schedule type:** Change triggered - -**Parameters:** None - -This control checks whether a SageMaker model bias job definition has network isolation enabled. The control fails if model bias job definition does not have network isolation enabled. - -Network isolation prevents SageMaker model bias jobs from communicating with external resources over the internet. By enabling network isolation, you ensure that the job's containers cannot make outbound connections, reducing the attack surface and protecting sensitive data from exfiltration. This is particularly important for jobs processing regulated or sensitive data. - -### Remediation - -To enable network isolation, you must create a new model bias job definition with `EnableNetworkIsolation` parameter set to `True`. Network isolation cannot be modified after job definition creation. To create a new model bias job definition, see [ CreateModelBiasJobDefinition](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_CreateModelBiasJobDefinition.html) in the _Amazon SageMaker AI Developer Guide_. - -## [SageMaker.13] SageMaker model quality job definitions should have inter-container traffic encryption enabled - -**Category:** Protect > Data Protection > Encryption of data-in-transit - -**Severity:** Medium - -**Resource type:** `AWS::SageMaker::ModelQualityJobDefinition` - -**AWS Config rule:** [ssagemaker-model-quality-job-encrypt-in-transit](https://docs.aws.amazon.com/config/latest/developerguide/sagemaker-model-quality-job-encrypt-in-transit.html) - -**Schedule type:** Change triggered - -**Parameters:** None - -This control checks whether Amazon SageMaker model quality job definitions have encryption in transit enabled for inter-container traffic. The control fails if a model quality job definition does not have inter-container traffic encryption enabled. - -Inter-container traffic encryption protects data transmitted between containers during distributed model quality monitoring jobs. By default, inter-container traffic is unencrypted. Enabling encryption helps maintain data confidentiality during processing and supports compliance with regulatory requirements for data in transit protection. - -### Remediation - -To enable inter-container traffic encryption for your Amazon SageMaker model quality job definition, you must re-create the job definition with the appropriate in-transit encryption configuration. To create a model quality job definition, see [ CreateModelQualityJobDefinition](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_CreateModelQualityJobDefinition.html) in the _Amazon SageMaker AI Developer Guide_. - -## [SageMaker.14] SageMaker monitoring schedules should have network isolation enabled - -**Category:** Protect > Secure network configuration - -**Severity:** Medium - -**Resource type:** `AWS::SageMaker::MonitoringSchedule` - -**AWS Config rule:** [sagemaker-monitoring-schedule-isolation](https://docs.aws.amazon.com/config/latest/developerguide/sagemaker-monitoring-schedule-isolation.html) - -**Schedule type:** Change triggered - -**Parameters:** None - -This control checks whether Amazon SageMaker monitoring schedules have network isolation enabled. The control fails if a monitoring schedule has EnableNetworkIsolation set to false or not configured - -Network isolation prevents monitoring jobs from making outbound network calls, reducing the attack surface by eliminating internet access from containers. - -### Remediation - -For information about configuring network isolation in the NetworkConfig parameter when creating or updating a monitoring schedule, see [CreateMonitoringSchedule](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_CreateMonitoringSchedule.html) or [ UpdateMonitoringSchedule](https://docs.aws.amazon.com/sagemaker/latest/APIReference/API_UpdateMonitoringSchedule.html) in the _Amazon SageMaker AI Developer Guide_. - -## [SageMaker.15] SageMaker model bias job definitions should have inter-container traffic encryption enabled - -**Category:** Protect > Data Protection > Encryption of data-in-transit - -**Severity:** Medium - -**Resource type:** `AWS::SageMaker::ModelBiasJobDefinition` - -**AWS Config rule:** [sagemaker-model-bias-job-encrypt-in-transit](https://docs.aws.amazon.com/config/latest/developerguide/sagemaker-model-bias-job-encrypt-in-transit.html) - -**Schedule type:** Change triggered - -**Parameters:** None - -This control checks whether Amazon SageMaker model bias job definitions have inter-container traffic encryption enabled when using multiple compute instances. The control fails if `EnableInterContainerTrafficEncryption` is set to false or is not configured for job definitions with an instance count of 2 or greater. - -EInter-container traffic encryption protects data transmitted between compute instances during distributed model bias monitoring jobs. Encryption prevents unauthorized access to model-related information such as weights that are transmitted between instances. - -### Remediation - -To enable inter-container traffic encryption for SageMaker model bias job definitions, set the `EnableInterContainerTrafficEncryption` parameter to `True` when the job definition uses multiple compute instances. For information about protecting communications between ML compute instances, see [Protect Communications Between ML Compute Instances in a Distributed Training Job](https://docs.aws.amazon.com/sagemaker/latest/dg/train-encrypt.html) in the _Amazon SageMaker AI Developer Guide_. -