- Home
- Skills
- Finance & Accounting
- soc2 evidence collector
Works with the AI Agents you already use
soc2 evidence collector
Generates audit-ready SOC 2 evidence artifacts for CC6 and CC8 mapped to actual system exports and logs.
$19
soc2 evidence collector
Example session with this skill installed
I need an access-control matrix for a SOC 2 Type II audit covering Jan 1 to June 30. Here is the IAM export from our production AWS account.
- Read your context and instructions
- Compiled the soc2 evidence collector
- Generated the data export
SOC 2 Access Control Matrix (CC6)
Observation Period: 2024-01-01 to 2024-06-30
Source: aws_iam_export_2024_07_01.csv
| Identity | Policy | Access Level | Source Ref |
|---|---|---|---|
| user_admin_01 | AdministratorAccess | Full | Line 12 |
| svc_deploy_bot | CI_CD_Policy | Write | Line 45 |
Findings: 1 orphaned account (user_old_dev) found with active keys (Line 89).
aws_iam_export_2024_07_01.csv
CSV · data export
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
Preparing for a SOC 2 audit often leads to a last-minute scramble to generate evidence that actually maps to specific AICPA criteria. Manually tracing IAM exports or git logs to CC6 and CC8 controls is error-prone and risks providing auditors with gapped or irrelevant data.
What it does
- Generates audit-ready access-control matrices, change-management logs, and encryption inventories.
- Maps every evidence row to specific lines in supplied IAM exports, git histories, or config files.
- Validates Type II evidence against stated observation periods to identify timestamp gaps.
- Flags stale Type I snapshots by comparing export generation dates to the current date.
- Identifies and reports control failures, such as unapproved changes or orphaned accounts, found during processing.
Why this beats prompting it yourself
General-purpose prompts often hallucinate plausible-looking data or fail to maintain the strict traceability required by auditors. This skill enforces a hard requirement for source data, ensuring every artifact is grounded in your actual system configuration rather than a description of it.
Use cases
- Generating a change-management log from git and deployment history for a Type II audit period.
- Creating an access-control matrix mapped to CC6 using raw IAM exports.
- Producing an encryption inventory for data-at-rest and in-transit based on infrastructure-as-code files.
- Identifying gaps in audit evidence before the official auditor review begins.
Known limitations
Does not cover CC7 (System Operations) or CC9 (Risk Mitigation). Requires raw text or file exports of system configs, as it cannot independently query cloud provider APIs.
Does not cover CC7 or CC9 criteria. Requires users to supply raw source data (IAM exports, logs, etc.); cannot pull live data via cloud APIs.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Requires