ato-source-aws

Collect NIST 800-53 evidence from AWS via read-only MCP API calls.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/AlastairThomson/AgentSkills --skill ato-source-aws-alastairthomson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ato-source-aws
Source: https://github.com/AlastairThomson/AgentSkills/tree/main/skills/global-scope/ato-source-aws
Command: npx skills add https://github.com/AlastairThomson/AgentSkills --skill ato-source-aws-alastairthomson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Collects NIST 800-53 evidence from AWS via the MCP AWS API server calls in read-only mode. This enables compliant, non-destructive assessments without modifying or exposing credentials.

Core Features & Use Cases

  • Read-only evidence collection for ATO readiness across AWS services.
  • Transparent, governance-friendly workflow with ambient authentication and region controls.
  • Real-world use case: feed AWS evidence into the ATO package to substantiate control compliance.

Quick Start

Run the AWS ATO collection through the MCP server with ambient authentication and US-region scope.

Frequently Asked Questions about ato-source-aws

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I collect NIST 800-53 evidence from AWS for ATO readiness?

Collect NIST 800-53 evidence from AWS by running read-only MCP API server calls that discover and export compliance artifacts without modifying resources or exposing credentials.

Can I gather AWS compliance evidence without risking accidental writes to my environment?

Yes, AWS compliance evidence is gathered using read-only API calls that enforce non-write actions, ensuring your environment remains non-destructive and fully compliant during assessments.

What is the best way to perform a non-destructive AWS ATO assessment using ambient authentication?

Perform a non-destructive AWS ATO assessment by configuring an AWS scope, restricting to US regions, and using ambient authentication to validate scope, discover evidence, and export results.

Does AWS ATO evidence collection require explicit credential configuration?

AWS ATO evidence collection uses ambient authentication and optional preauth via auth-config, avoiding explicit credential exposure while maintaining a governance-friendly workflow.

What limitations apply when collecting NIST 800-53 evidence from AWS?

Evidence collection is limited to read-only actions and restricted to US regions, ensuring no write operations occur and all API calls remain within the configured AWS scope.

How does the AWS ATO evidence collector workflow generate compliance citations?

The workflow validates the configured AWS scope, discovers evidence via read-only API calls, exports results, and emits citations to substantiate NIST 800-53 control compliance.