ato-source-smb

Collects NIST 800-53 evidence from SMB shares into an evidence batch and citations file.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/AI-Strategy-LLC/AgentSkills --skill ato-source-smb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ato-source-smb
Source: https://github.com/AI-Strategy-LLC/AgentSkills/tree/main/skills/repo-scope/ato-source-smb
Command: npx skills add https://github.com/AI-Strategy-LLC/AgentSkills --skill ato-source-smb

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Collects SMB/Windows share evidence for compliance and security investigations without altering the source, enabling auditable evidence gathering.

Core Features & Use Cases

  • OS detection (macOS/Linux) and Windows UNC path support for mounting or accessing shares.
  • Depth-limited traversal, file-type filtering, and per-share configuration to curate relevant evidence.
  • Automatically copy discovered files to the evidence store and emit a structured citation batch with provenance.

Quick Start

Configure the SMB shares you want scanned and run the ato-source-smb workflow to mount, discover, copy, and emit citations.

Frequently Asked Questions about ato-source-smb

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

FAQPage Schema
How do I collect NIST 800-53 audit evidence from SMB file shares?

Collect NIST 800-53 audit evidence from SMB shares by mounting read-only shares across macOS/Linux or accessing UNC paths on Windows. The process applies depth-limited traversal and file-type filtering to map matched files to control families, producing an evidence batch and citations file.

Can I scan Windows UNC paths for compliance evidence without altering the source files?

Yes, you can scan Windows UNC paths for compliance evidence without altering source files. The workflow mounts read-only shares, discovers relevant files based on configured filters, and copies them to an evidence store while emitting a structured citation batch with provenance.

What is the best way to automate forensics evidence gathering across macOS and Linux SMB shares?

Automate forensics evidence gathering across macOS and Linux SMB shares using OS detection to mount read-only shares. The system applies depth-limited traversal and per-share configuration to curate relevant evidence, automatically copying discovered files and emitting structured citations.

Does SMB evidence collection support pre-authenticated mounting for security investigations?

SMB evidence collection enforces ambient-auth by default but supports optional pre-authenticated mounting via an auth-config setup. This allows secure, read-only access to file shares for compliance and security investigations while maintaining provenance.

What happens if partial failures occur during SMB file share evidence collection?

If partial failures occur during SMB file share evidence collection, the system guarantees unmount and captures the errors in the citation batch. This ensures error reporting is maintained alongside the successfully collected evidence batch.

How do I configure depth-limited traversal and file-type filtering for SMB compliance scans?

Configure depth-limited traversal and file-type filtering for SMB compliance scans by setting per-share parameters before running the workflow. This curation process ensures only relevant files are mapped to NIST 800-53 control families and copied to the evidence store.