Skip to main content

🛡️ AWS SageMaker Notebook Instance is not in a VPC🟢

Logic​

Similar Policies​

Description​

Open File

Description​

This policy identifies AWS SageMaker Notebook Instances that are not deployed within a Virtual Private Cloud (VPC).

Rationale​

By default, SageMaker notebook instances run in an AWS-managed network environment with direct access to the public internet. Deploying notebook instances within a customer-managed VPC provides enhanced security, control, and visibility over network traffic.

Key benefits include:

  1. Network Isolation: The notebook instance can communicate with other AWS resources (such as Amazon RDS or EMR) using private IP addresses.
  2. Access Control: Inbound and outbound traffic can be tightly controlled using Security Groups and Network ACLs.
  3. Private Connectivity: AWS services (for example, Amazon S3) can be accessed through VPC Endpoints, ensuring traffic remains within the AWS global network.
  4. Monitoring and Auditing: Network activity can be monitored and analyzed using VPC Flow Logs.

Impact​

Remediation requires provisioning a new SageMaker notebook instance within the desired VPC and subnet, as the VPC configuration cannot be modified after the notebook instance is created. This process may involve migrating data, notebooks, and configurations from the existing instance to the newly created one.

... see more

Remediation​

Open File

Remediation​

Deploy SageMaker Notebook Instances Within a VPC​

To remediate this finding, provision a new AWS SageMaker Notebook Instance within the appropriate VPC and subnet, and migrate all required data and configurations from the existing incompliant instance. AWS does not allow the VPC configuration of a notebook instance to be modified after creation.

From Command Line​
1. Create a New Notebook Instance in the Desired VPC​

Before proceeding, ensure that the target VPC, subnet, and security groups are properly configured.

aws sagemaker create-notebook-instance \
    --notebook-instance-name {{new-instance-name}} \
    --instance-type {{instance-type}} \
    --role-arn {{iam-role-arn}} \
    --subnet-id {{subnet-id}} \
    --security-group-ids {{security-group-ids}} \
    --direct-internet-access Disabled
2. Migrate Data and Decommission the Incompliant Instance​
  • Wait until the new notebook instance reaches the InService state.
  • Migrate notebooks, datasets, and any required configurations from the existing instance to the newly created instance.

... see more

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlagsCompliance
💼 AWS Foundational Security Best Practices v1.0.0 → 💼 [SageMaker.2] SageMaker AI notebook instances should be launched in a custom VPC1no data
💼 Cloudaware Framework → 💼 Secure Access70no data
💼 FedRAMP High Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)3782no data
💼 FedRAMP High Security Controls → 💼 AC-4 Information Flow Enforcement (M)(H)237101no data
💼 FedRAMP High Security Controls → 💼 AC-4(21) Physical or Logical Separation of Information Flows (M)(H)1160no data
💼 FedRAMP High Security Controls → 💼 AC-6 Least Privilege (M)(H)81174no data
💼 FedRAMP High Security Controls → 💼 AC-21 Information Sharing (M)(H)18no data
💼 FedRAMP High Security Controls → 💼 SC-7 Boundary Protection (L)(M)(H)10879no data
💼 FedRAMP High Security Controls → 💼 SC-7(3) Access Points (M)(H)18no data
💼 FedRAMP High Security Controls → 💼 SC-7(4) External Telecommunications Services (M)(H)46no data
💼 FedRAMP High Security Controls → 💼 SC-7(20) Dynamic Isolation and Segregation (H)18no data
💼 FedRAMP High Security Controls → 💼 SC-7(21) Isolation of System Components (H)35no data
💼 FedRAMP Low Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)82no data
💼 FedRAMP Low Security Controls → 💼 SC-7 Boundary Protection (L)(M)(H)47no data
💼 FedRAMP Moderate Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)82no data
💼 FedRAMP Moderate Security Controls → 💼 AC-4 Information Flow Enforcement (M)(H)185no data
💼 FedRAMP Moderate Security Controls → 💼 AC-4(21) Physical or Logical Separation of Information Flows (M)(H)60no data
💼 FedRAMP Moderate Security Controls → 💼 AC-6 Least Privilege (M)(H)674no data
💼 FedRAMP Moderate Security Controls → 💼 AC-21 Information Sharing (M)(H)18no data
💼 FedRAMP Moderate Security Controls → 💼 SC-7 Boundary Protection (L)(M)(H)765no data
💼 FedRAMP Moderate Security Controls → 💼 SC-7(3) Access Points (M)(H)18no data
💼 FedRAMP Moderate Security Controls → 💼 SC-7(4) External Telecommunications Services (M)(H)46no data
💼 NIST CSF v2.0 → 💼 DE.CM-01: Networks and network services are monitored to find potentially adverse events170no data
💼 NIST CSF v2.0 → 💼 DE.CM-09: Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events170no data
💼 NIST CSF v2.0 → 💼 ID.AM-03: Representations of the organization's authorized network communication and internal and external network data flows are maintained86no data
💼 NIST CSF v2.0 → 💼 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties131no data
💼 NIST CSF v2.0 → 💼 PR.DS-01: The confidentiality, integrity, and availability of data-at-rest are protected180no data
💼 NIST CSF v2.0 → 💼 PR.DS-02: The confidentiality, integrity, and availability of data-in-transit are protected156no data
💼 NIST CSF v2.0 → 💼 PR.DS-10: The confidentiality, integrity, and availability of data-in-use are protected176no data
💼 NIST CSF v2.0 → 💼 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage119no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-3 Access Enforcement15557no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-3(7) Access Enforcement _ Role-based Access Control29no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-4 Information Flow Enforcement3269116no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-4(21) Information Flow Enforcement _ Physical or Logical Separation of Information Flows3760no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-6 Least Privilege102367no data
💼 NIST SP 800-53 Revision 5 → 💼 AC-21 Information Sharing218no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-7 Boundary Protection29486no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(3) Boundary Protection _ Access Points18no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(4) Boundary Protection _ External Telecommunications Services46no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(9) Boundary Protection _ Restrict Threatening Outgoing Communications Traffic29no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(11) Boundary Protection _ Restrict Incoming Communications Traffic35no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(16) Boundary Protection _ Prevent Discovery of System Components36no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(20) Boundary Protection _ Dynamic Isolation and Segregation18no data
💼 NIST SP 800-53 Revision 5 → 💼 SC-7(21) Boundary Protection _ Isolation of System Components35no data