← ClaudeAtlas

soc2-reportlisted

Use when preparing a SOC 2 report or readiness assessment — mapping controls to the Trust Services Criteria, choosing Type I vs Type II, gathering audit evidence, and tracking exceptions. Triggers on "SOC 2", "Type I", "Type II", "Trust Services Criteria", "TSC", "audit evidence", "AICPA", "control exception".
noctua84/nescio-ai · ★ 0 · Data & Documents · score 73
Install: claude install-skill noctua84/nescio-ai
# SOC 2 Report ## Purpose Create a SOC 2 compliance report that delivers actionable, measurable results. **Category**: Cybersecurity & Information Security ## Inputs ### Required - **Objective**: What you want to achieve with this deliverable - **Context**: Relevant background information (systems, scope, environment) ### Optional - **Constraints**: Any limitations or requirements to consider - **Existing Work**: Previous documents or data to build on ## Context Before starting, read the repo's `CLAUDE.md` and any relevant notes under `memory/` (e.g. `memory/repo/<repo>/`, `memory/feedback/`) for prior decisions and constraints. ## Process ### Step 1: Context & Research - Review any existing soc 2 compliance report documents in the project - Identify key stakeholders and their requirements - Select the most appropriate framework: AICPA Trust Services Criteria, SOC 2 Type I/II, COSO Internal Control Framework ### Step 2: Analysis & Framework Application - Apply the selected framework to structure the soc 2 compliance report - Identify gaps, opportunities, and risks - Define success metrics: Control Count by Trust Category, Exception Rate, Remediation Completion Rate, Evidence Collection Completeness % - Document assumptions and dependencies - Validate approach against industry best practices ### Step 3: Build the Deliverable - Structure the soc 2 compliance report using the output format below - Include specific, actionable recommendations — not generic advice - Ad