Controls for Network Access to ML Resources: Study Guide

Securing machine learning (ML) resources requires a robust approach to network isolation and access control. By leveraging Amazon VPC and its associated security features, organizations can ensure that sensitive training data and model endpoints are protected from unauthorized access.

Learning Objectives

After studying this guide, you should be able to:

• Define the Shared Responsibility Model as it applies to networking and ML.
• Distinguish between Security Groups and Network Access Control Lists (NACLs).
• Describe how to implement network isolation for SageMaker notebooks, training jobs, and endpoints.
• Apply the principle of least privilege to network traffic routing.

Key Terms & Glossary

• Virtual Private Cloud (VPC): A logically isolated section of the AWS Cloud where you launch AWS resources in a virtual network.
• Security Group: A stateful virtual firewall for instances that controls inbound and outbound traffic.
• Network ACL (NACL): An optional, stateless layer of security for your VPC that acts as a firewall for controlling traffic in and out of one or more subnets.
• Shared Responsibility Model: A framework that divides security tasks between AWS (security of the cloud) and the customer (security in the cloud).
• Stateful: A security mechanism that automatically allows return traffic for an established connection (e.g., Security Groups).
• Stateless: A security mechanism that requires explicit rules for both inbound and outbound traffic (e.g., NACLs).

The "Big Idea"

[!IMPORTANT] Network security for ML is about Defense in Depth. Even if an IAM credential is compromised, network controls like VPC isolation act as a physical-style barrier that prevents external actors from reaching internal resources unless they are within the authorized network path.

Formula / Concept Box

Hierarchical Outline

• I. Shared Responsibility Model
  • AWS Responsibility (Security OF the Cloud): Physical security, hardware infrastructure, and managed service underlying layers.
  • Customer Responsibility (Security IN the Cloud): Data encryption, IAM configuration, and Network Access Control.
• II. Core Network Security Tools
  • Amazon VPC: Enables logical isolation of ML infrastructure.
  • Security Groups: Acts as a virtual firewall for specific resources (e.g., SageMaker endpoints).
  • Network ACLs: Subnet-level traffic control; used to block specific IPs or ports.
• III. Securing SageMaker Resources
  • Notebook Instances: Deploying within a VPC to restrict access to internal corporate data.
  • Inference Endpoints: Treating endpoints as HTTPS APIs with IP range restrictions.
  • Training Jobs: Ensuring model artifacts ($model.tar.gz$) are stored and accessed via private network paths.

Visual Anchors

Traffic Flow Architecture

Network Isolation Visualization

Definition-Example Pairs

• Least Privilege (Network): Restricting access to the minimum set of IP addresses required for a function.
  • Example: Configuring a Security Group for a SageMaker endpoint to only allow inbound traffic from a specific internal Application Load Balancer IP range.
• Stateless Filtering: Monitoring traffic without regard to previous packets.
  • Example: Using a Network ACL to explicitly deny all traffic from a known malicious IP subnet ($192.168.0.0/24$) regardless of whether they initiated the request.

Worked Examples

Scenario: Restricting Access to a SageMaker Endpoint

Goal: Ensure a production model endpoint only receives traffic from an internal web application.

1. VPC Setup: Deploy the SageMaker endpoint into a private subnet within your VPC.
2. Security Group Configuration:
   • Inbound Rule: Type: HTTPS (443), Source: Custom (Security Group ID of the Web App).
   • Outbound Rule: Limit to only necessary services (e.g., S3 for logging).
3. Endpoint Policy: Attach an IAM policy to the endpoint that requires the request to originate from the specific VPC Endpoint ID.

Checkpoint Questions

1. If a request is allowed by a Security Group but the return traffic is blocked, is the resource likely using a Security Group or a Network ACL? (Answer: Network ACL, as it is stateless and requires a return rule).
2. Which part of the Shared Responsibility Model covers the encryption of data at rest within a VPC? (Answer: Customer responsibility).
3. True or False: A VPC provides logical isolation within the AWS cloud. (Answer: True).

Muddy Points & Cross-Refs

• Stateful vs. Stateless: Students often confuse which is which. Remember: Security Groups are Smart (Stateful) — they remember who you are. Network ACLs are Not (Stateless).
• Public vs. Private Subnets: A subnet is only "public" if its route table has a path to an Internet Gateway (IGW). For ML security, always prefer private subnets with VPC Endpoints for S3 access.

Comparison Tables

Security Groups vs. Network ACLs