sample-aiml-security-assessment

AWS AI/ML Security Assessment — Amazon Bedrock, Amazon SageMaker AI & Amazon Bedrock AgentCore

License: MIT-0 Python 3.12+ AWS SAM Serverless

Open-source automated security scanner for Amazon Bedrock, Amazon SageMaker AI, and Amazon Bedrock AgentCore — Built on AWS Well-Architected Framework (Generative AI Lens)

Cloud security automation with 52 security checks for your generative AI and machine learning workloads. Identify IAM misconfigurations, encryption gaps, network isolation issues, and compliance violations with interactive HTML reports and actionable remediation guidance.

See It In Action

The framework generates professional, interactive security assessment reports with filtering, search, and dark mode support.

Download Sample Reports Single Account Multi-Account
AWS AI/ML security assessment dashboard showing Amazon Bedrock, Amazon SageMaker AI, and Amazon Bedrock AgentCore findings by severity

Executive Dashboard (Light Mode)

 AWS AI/ML security assessment dashboard showing Amazon Bedrock, Amazon SageMaker AI, and Amazon Bedrock AgentCore findings by severity

Executive Dashboard (Dark Mode)
Detailed Findings Table

Interactive Findings Table with Filtering

Key Features

Table of Contents

What It Does

This serverless assessment framework automatically evaluates your AI/ML workloads against AWS security best practices. It uses AWS serverless services to gather data from the control plane and generate reports containing the status of various security checks, severity levels, and recommended actions.

Designed for workloads using Amazon Bedrock, Amazon Bedrock AgentCore, or Amazon SageMaker AI.

Why Use This Framework?

Challenge How This Framework Helps
Manual security audits are time-consuming Fully automated scanning with one-click CloudFormation deployment
Inconsistent security checks across teams Standardized 52-check assessment based on AWS Well-Architected best practices
Difficulty tracking AI/ML security posture Interactive HTML dashboards with severity breakdown and per-account visibility
Multi-account complexity Consolidated reporting across AWS Organizations with cross-account role assumption
Compliance and audit support Exportable reports to supplement your compliance program, with remediation guidance linked to AWS documentation
Generative AI security gaps Purpose-built checks for LLM guardrails, model access controls, and prompt injection prevention

Services Covered:

Deployment Options:

How It Works:

  1. Deploy through AWS CloudFormation (one-click deployment)
  2. Framework automatically scans your AI/ML resources
  3. Generates interactive HTML reports stored in your Amazon S3 bucket
  4. All data stays in your AWS account - no external dependencies

Scope and Limitations

This tool operates within the AWS Shared Responsibility Model. It assesses your configuration responsibilities (IAM policies, encryption settings, network isolation, logging) for AI/ML services. It does not assess AWS-managed infrastructure, physical security, or the underlying service platform.

Point-in-time assessment. Each run captures your security posture at the moment of execution. Resource configurations can change immediately after an assessment completes. Run assessments regularly and after significant changes to maintain visibility.

No guarantee of security or compliance. This framework identifies common misconfigurations based on AWS best practices and the AWS Well-Architected Framework. It does not cover all possible security risks, does not replace formal compliance audits (SOC 2, HIPAA, and similar), and does not guarantee that your workloads are secure. Use the results as one input into your broader security program.

52 checks across three services. The assessment covers Amazon Bedrock, Amazon SageMaker AI, and Amazon Bedrock AgentCore. Other AI/ML services (Amazon Comprehend, Amazon Rekognition, Amazon Textract, and others) are not currently assessed.

Quick Start

Architecture

Architecture

Prerequisites

Single-Account Deployment

  1. Download the aiml-security-single-account.yaml AWS CloudFormation template.
  2. Deploy to AWS CloudFormation
  3. Upload the AWS CloudFormation template from step 1.
  4. Provide a stack name and optionally specify your email address to receive notifications.
  5. Leave all other parameters at their default values.
  6. Navigate to the next page, read and acknowledge the notice, and click Next.
  7. Review the information and click Submit.
  8. Wait for the AWS CloudFormation stack to complete.
  9. Once complete, AWS CodeBuild automatically deploys the assessment stack and runs the assessment.
  10. To view results:
    • Navigate to the AWS CloudFormation console
    • Open the stack you deployed (for example, aiml-security-single-account or your custom name)
    • Go to the Outputs tab
    • Copy the AssessmentBucket value
    • Navigate to that Amazon S3 bucket and open the {account_id}/security_assessment_*.html file

Understanding Stack Names

Important: The deployment creates TWO AWS CloudFormation stacks. Only one contains your results!

Stack Type How to Identify What It Contains What to Do
Infrastructure Stack
(This is the one you need)		 The name you chose
Examples:
- my-aiml-assessment
- aiml-security-prod
- aiml-security-single-account 		AWS CodeBuild project
Amazon S3 bucket for results
AWS IAM roles
The "AssessmentBucket" output 		Use this stack to view results!

1. Open this stack in console
2. Go to Outputs tab
3. Copy AssessmentBucket value
Assessment Stack
(Auto-generated - ignore this)		 Auto-generated name:
Single-account: aiml-sec-{account_id}
Multi-account: aiml-security-{account_id} per member account, plus aiml-security-mgmt for the management account
Examples:
aiml-sec-123456789012 (single)
aiml-security-123456789012 (multi) 		AWS Lambda functions
AWS Step Functions
Internal resources
No outputs you need 		Don't use this stack!

It's for internal operations only.
Created automatically by AWS CodeBuild.

Quick Check: If you see a stack name starting with aiml-sec- or aiml-security- followed by numbers (or aiml-security-mgmt), that’s an auto-generated assessment stack. Look for the stack name you originally chose during deployment.

Multi-Account Deployment

Prerequisites

The deployment follows a two-step approach:

Step 1: Deploy Member Roles (AWS CloudFormation StackSets)

Deploy 1-aiml-security-member-roles.yaml to all target accounts using AWS CloudFormation StackSets with service-managed permissions.

AWS Console Deployment

  1. Navigate to AWS CloudFormation > StackSets in the management account
  2. Click Create StackSet
  3. Select Upload a template file and upload 1-aiml-security-member-roles.yaml
  4. Enter a StackSet name (for example, aiml-security-member-roles)
  5. Set the ManagementAccountID parameter to your management account ID
  6. Under Permissions, select Service-managed permissions
  7. Under Deployment targets, select the Organizational Units (OUs) containing your target accounts
  8. Select us-east-1 (or your target region) under Specify regions
  9. Review and click Submit

This uses AWS Organizations to deploy the member role to all accounts in the selected OUs. New accounts added to those OUs will automatically receive the role.

Step 2: Deploy Central Infrastructure

Deploy 2-aiml-security-codebuild.yaml in your central management account or delegated administrator member account.

AWS Console Deployment

  1. Navigate to AWS CloudFormation
  2. Select Upload a template file and upload the 2-aiml-security-codebuild.yaml file.
  3. Set the MultiAccountScan parameter to true.
  4. Optionally, provide your email address in the EmailAddress parameter for completion notifications.
  5. Leave the remaining parameters at their default values.
  6. Navigate to the next page, read and acknowledge the notice, and click Next.
  7. Review the information and click Submit.
  8. Stack creation automatically triggers AWS CodeBuild, which deploys the assessment to each account and runs it.

How It Works

Single-Account Mode (MultiAccountScan=false)

Multi-Account Mode (MultiAccountScan=true)

Assessment Execution Process

Automatic Trigger

Multi-Account Orchestration

  1. Account Discovery: AWS CodeBuild queries AWS Organizations for active accounts
  2. Role Assumption: Assumes AIMLSecurityMemberRole in each target account
  3. Module Deployment: Deploys the AI/ML assessment module:
    • Amazon Bedrock Assessment AWS Lambda
    • Amazon SageMaker AI Assessment AWS Lambda
    • Amazon Bedrock AgentCore Assessment AWS Lambda
    • AWS IAM Permission Caching AWS Lambda
    • Consolidated Report Generation AWS Lambda
  4. Assessment Execution: AWS Step Functions orchestrate parallel AWS Lambda execution
  5. Results Collection: Individual AWS Lambda functions store results in local Amazon S3 buckets
  6. Consolidation: AWS CodeBuild collects and consolidates results from all accounts
  7. Reporting: Generates multi-account HTML and CSV reports
  8. Notification: Sends completion notification through Amazon SNS (if configured)

Permissions Required

Central Account Role (MultiAccountCodeBuildRole)

Member Account Role (AIMLSecurityMemberRole)

Monitoring and Results

Viewing Assessment Results

You can check the AWS CodeBuild console to confirm the assessment completed successfully before accessing the results.

Accessing Results

  1. Find the Amazon S3 Bucket Name:
    • Navigate to AWS CloudFormation > Stacks in the AWS Console
    • For single-account deployments using the standalone template (aiml-security-single-account.yaml), select the stack you deployed (for example, aiml-security-single-account) and find the AssessmentBucket output. Results are synced to this bucket under the {account_id}/ prefix.
    • For multi-account deployments, select the aiml-security-multi-account stack created in Step 2: Deploy Central Infrastructure and find the AssessmentBucket output
    • Go to the Outputs tab
    • Copy the Amazon S3 bucket name

    Note: The deployment creates multiple Amazon S3 buckets. Only use the bucket from the AssessmentBucket output above. Other buckets (such as aiml-sec-*-aimlassessmentbucket-* from nested stacks or aws-sam-cli-managed-* for deployment artifacts) are for internal use and can be ignored.

  2. Navigate to the Amazon S3 Bucket:
    • Go to Amazon S3 in the AWS Console
    • Search for and open your assessment bucket
    • For single-account deployments, open the security_assessment_XXXXX.html report
    • For multi-account deployments, follow the Report Structure guidance below

Report Structure

Consolidated Reports

Individual Account Reports

Understanding Results

Severity Description
High Critical security issues requiring immediate attention
Medium Important security improvements recommended
Low Minor optimizations suggested
Informational Advisory information, no action required
N/A Check not applicable (no resources to assess)
Status Description
Failed Security issue identified that requires remediation
Passed Checked resources met the assessed best practice at time of scan
N/A No resources exist to check (for example, no notebooks, no guardrails configured)

Customization

Adding New Accounts

Option A: AWS Console

  1. Navigate to AWS CloudFormation > StackSets
  2. Select aiml-security-member-roles AWS CloudFormation StackSet
  3. Click Add stacks to StackSet
  4. Choose deployment targets:
    • Deploy to accounts: Enter specific account IDs
    • Regions: Select target regions
  5. Review and click Submit

Modifying Assessment Scope

To add or remove service permissions, edit the member role permissions in 1-aiml-security-member-roles.yaml.

Concurrent Scanning

Adjust the ConcurrentAccountScans parameter based on your organization size and cost considerations.

Cleanup

Single-Account Cleanup

To remove all resources deployed for single-account assessment:

  1. Delete the AWS SAM-deployed assessment stack:
    • Navigate to AWS CloudFormation > Stacks
    • Select the aiml-sec-{account_id} stack (for example, aiml-sec-123456789012)
    • Click Delete
    • Wait for stack deletion to complete
  2. Delete the AWS CodeBuild infrastructure stack:
    • Select the aiml-security-single-account stack (or your custom stack name)
    • Click Delete
    • Wait for stack deletion to complete
  3. Clean up Amazon S3 buckets (if stack deletion fails due to non-empty buckets): 
    # Empty the assessment bucket
aws s3 rm s3://<assessment-bucket-name> --recursive

# If versioning is enabled, delete version markers
aws s3api delete-objects --bucket <bucket-name> --delete \
  "$(aws s3api list-object-versions --bucket <bucket-name> \
  --query '{Objects: Versions[].{Key:Key,VersionId:VersionId}}')"

# Delete the bucket
aws s3 rb s3://<bucket-name>

Multi-Account Cleanup

To remove all resources deployed for multi-account assessment:

  1. Delete AWS SAM-deployed stacks in each member account:
    • For each account that was scanned, navigate to AWS CloudFormation > Stacks
    • Select the aiml-security-{account_id} stack (for example, aiml-security-123456789012)
    • For the management account, select aiml-security-mgmt
    • Click Delete
    • Alternatively, use the AWS CLI to delete across accounts: 
      # Assume role in member account and delete stack
aws cloudformation delete-stack --stack-name aiml-security-<account_id> \
  --region <region>
  2. Delete the central AWS CodeBuild infrastructure stack:
    • In the management account, navigate to AWS CloudFormation > Stacks
    • Select the aiml-security-multi-account stack
    • Click Delete
    • Wait for stack deletion to complete
  3. Delete the AWS CloudFormation StackSet member roles:
    • Navigate to AWS CloudFormation > StackSets
    • Select the aiml-security-member-roles AWS CloudFormation StackSet
    • Click Actions > Delete stacks from StackSet
    • Select all deployment targets (OUs or accounts)
    • Wait for stack instances to be deleted
    • Once all stack instances are removed, delete the AWS CloudFormation StackSet itself
  4. Clean up Amazon S3 buckets (if stack deletion fails due to non-empty buckets): 
    # List and identify assessment buckets
aws s3 ls | grep aiml-security

# Empty each bucket
aws s3 rm s3://<bucket-name> --recursive

# Delete version markers if versioning was enabled
aws s3api delete-objects --bucket <bucket-name> --delete \
  "$(aws s3api list-object-versions --bucket <bucket-name> \
  --query '{Objects: Versions[].{Key:Key,VersionId:VersionId}}')"

# Delete the bucket
aws s3 rb s3://<bucket-name>

Cleanup Order

For a clean removal, delete resources in this order:

  1. Assessment stacks (auto-created by SAM):
    • Single-account: aiml-sec-{account_id} (for example, aiml-sec-123456789012)
    • Multi-account: aiml-security-{account_id} per member account, plus aiml-security-mgmt for management account
  2. Infrastructure stack (the stack you deployed manually):
    • Single-account: Your chosen stack name (for example, my-aiml-assessment)
    • Multi-account: aiml-security-multi-account or your chosen name

  3. AWS CloudFormation StackSet member roles (multi-account only)

  4. Any remaining Amazon S3 buckets manually

Documentation

Document Description
Security Checks Reference Complete reference for all 52 security checks with severity levels
Troubleshooting Guide Common issues, debugging tips, and FAQ
Developer Guide Architecture details, adding custom checks, and contributing

CI/CD

GitHub Actions workflows run automatically on pull requests and pushes to main:

Workflow Trigger What It Checks
Python Code Quality PR Runs ruff check and ruff format --check on changed Python files
CloudFormation Lint PR Validates deployment and SAM templates with cfn-lint
SAM Validate & Build PR Runs sam validate --lint and sam build on SAM templates
ASH Security Scan PR Scans changed files for secrets, dependency vulnerabilities, and IaC misconfigurations
ASH Full Repository Scan Push to main, monthly Full repository security scan with results uploaded as artifacts

Contributing

We welcome community contributions! Please see Developer Guide for guidelines.

Security

See CONTRIBUTING for reporting security issues.

License

This library is licensed under the MIT-0 License. See the LICENSE file.

This site is open source. Improve this page.