Back to Skills

assisting-with-soc2-audit-preparation

jeremylongshore
Updated Today
15 views
712
74
712
View on GitHub
Metawordautomation

About

This Claude Skill automates SOC 2 audit preparation by gathering evidence, assessing controls, and identifying compliance gaps. Developers should use it when preparing for audits, checking Trust Service Criteria, or generating readiness reports. It triggers on phrases like "SOC 2 audit preparation" and utilizes tools like Bash for audit collection and compliance checks.

Quick Install

Claude Code

Recommended
Plugin CommandRecommended
/plugin add https://github.com/jeremylongshore/claude-code-plugins-plus
Git CloneAlternative
git clone https://github.com/jeremylongshore/claude-code-plugins-plus.git ~/.claude/skills/assisting-with-soc2-audit-preparation

Copy and paste this command in Claude Code to install this skill

Documentation

Prerequisites

Before using this skill, ensure:

  • Documentation directory accessible in {baseDir}/docs/
  • Infrastructure-as-code and configuration files available
  • Access to cloud provider logs (AWS CloudTrail, Azure Activity Log, GCP Audit Logs)
  • Security policies and procedures documented
  • Employee training records available
  • Incident response documentation accessible
  • Write permissions for audit reports in {baseDir}/soc2-audit/

Instructions

1. Trust Service Criteria Assessment

Evaluate controls across five categories:

Security (Common Criteria) - Required for all SOC 2 audits:

  • CC1: Control Environment
  • CC2: Communication and Information
  • CC3: Risk Assessment
  • CC4: Monitoring Activities
  • CC5: Control Activities
  • CC6: Logical and Physical Access Controls
  • CC7: System Operations
  • CC8: Change Management
  • CC9: Risk Mitigation

Additional Criteria (Optional):

  • Availability
  • Processing Integrity
  • Confidentiality
  • Privacy

2. Evidence Collection Phase

Security Controls Evidence:

  • Access control policies and configurations
  • Multi-factor authentication implementation
  • Password policy documentation
  • Firewall rules and network segmentation
  • Encryption at rest and in transit
  • Security monitoring and alerting configs

Operational Evidence:

  • Change management logs
  • Backup and recovery procedures
  • Disaster recovery testing results
  • System monitoring dashboards
  • Capacity planning documentation
  • Performance metrics

Policy and Procedure Evidence:

  • Information security policy
  • Incident response plan
  • Business continuity plan
  • Vendor management procedures
  • Employee onboarding/offboarding
  • Security awareness training records

System Evidence:

  • System architecture diagrams
  • Data flow diagrams
  • Asset inventory
  • Software bill of materials (SBOM)
  • Configuration management database

3. Control Effectiveness Testing

For each control point:

  • Verify control design (is it properly designed?)
  • Test operating effectiveness (is it working as intended?)
  • Document test results with screenshots/logs
  • Identify gaps or weaknesses
  • Recommend remediation actions

4. Compliance Gap Analysis

Compare current state against SOC 2 requirements:

  • Missing controls (critical gaps)
  • Partially implemented controls (needs improvement)
  • Improperly documented controls (evidence gaps)
  • Ineffective controls (design or operating failures)

5. Evidence Documentation

Organize evidence by Trust Service Criteria:

{baseDir}/soc2-audit/
├── CC1-control-environment/
│   ├── org-chart.pdf
│   ├── security-policy.md
│   └── training-records.xlsx
├── CC6-access-controls/
│   ├── iam-policies.json
│   ├── mfa-config.yaml
│   └── access-review-logs.csv
├── CC7-system-operations/
│   ├── monitoring-configs/
│   ├── backup-procedures.md
│   └── incident-logs/
└── readiness-report.md

6. Generate Readiness Report

Create comprehensive SOC 2 readiness assessment with:

  • Executive summary with readiness score
  • Control-by-control assessment
  • Gap analysis with severity ratings
  • Remediation roadmap with timelines
  • Evidence collection checklist
  • Auditor interview preparation guide

Output

The skill produces:

Primary Output: SOC 2 readiness report saved to {baseDir}/soc2-audit/readiness-report-YYYYMMDD.md

Report Structure:

# SOC 2 Readiness Assessment
Assessment Date: 2024-01-15
Organization: TechCorp Inc.
Audit Type: SOC 2 Type II (Security + Availability)

## Executive Summary
- Overall Readiness: 75% (Needs Improvement)
- Controls Implemented: 28/40 (70%)
- Critical Gaps: 3
- High Priority Items: 8
- Estimated Remediation Time: 8-12 weeks

## Readiness by Trust Service Category

### CC1: Control Environment (80%)
✅ Implemented (4):
- Organizational structure documented
- Security policy established
- Risk assessment framework in place
- Board oversight of security

⚠️ Gaps (1):
- Security role and responsibility matrix incomplete

### CC6: Logical and Physical Access Controls (60%)
✅ Implemented (5):
- Multi-factor authentication enabled
- Role-based access control (RBAC) implemented
- Password policy enforced
- Access review process established
- Visitor access controls in place

❌ Critical Gaps (2):
- No automated user deprovisioning
- Privileged access not logged/monitored

⚠️ High Priority (3):
- Access logs retention < 1 year
- No formal access request workflow
- Physical security cameras not monitored 24/7

### CC7: System Operations (70%)
[Similar breakdown...]

## Critical Gaps Requiring Immediate Action

### 1. Automated User Deprovisioning (CC6.2)
**Current State**: Manual offboarding process
**Risk**: Terminated employees retain system access
**Evidence**: {baseDir}/hr/offboarding-checklist.pdf
**Remediation**:
- Implement automated deprovisioning tied to HR system
- Set up alerts for access not removed within 24 hours
- Estimated effort: 2-3 weeks
**Priority**: CRITICAL

### 2. Privileged Access Monitoring (CC6.7)
**Current State**: No logging of admin actions
**Risk**: Insider threats undetected
**Remediation**:
- Enable audit logging for all admin accounts
- Set up SIEM alerts for privileged actions
- Implement session recording for production access
**Priority**: CRITICAL

### 3. Disaster Recovery Testing (CC7.4)
**Current State**: DR plan exists but never tested
**Risk**: Recovery time objectives may not be achievable
**Remediation**:
- Schedule quarterly DR tests
- Document test results
- Update plan based on test findings
**Priority**: CRITICAL

## Evidence Collection Status

| Control | Evidence Type | Status | Location |
|---------|--------------|--------|----------|
| CC1.1 | Org Chart | ✅ Complete | {baseDir}/soc2-audit/CC1/ |
| CC6.1 | MFA Config | ✅ Complete | {baseDir}/soc2-audit/CC6/ |
| CC6.2 | Offboarding Logs | ❌ Missing | N/A |
| CC7.1 | Monitoring Dashboards | ⚠️ Partial | Need 90-day history |

## Remediation Roadmap

**Weeks 1-2 (Critical Fixes)**:
- Implement automated deprovisioning
- Enable privileged access monitoring
- Begin DR test planning

**Weeks 3-6 (High Priority)**:
- Extend log retention to 1 year
- Implement access request workflow
- Complete initial DR test

**Weeks 7-12 (Medium Priority)**:
- Enhance physical security monitoring
- Improve change management documentation
- Complete second DR test cycle

## Auditor Preparation

**Key Interview Topics**:
- Control environment and tone from the top
- Incident response capabilities
- Change management process
- Access control procedures
- Monitoring and alerting effectiveness

**Suggested Interviewees**:
- CTO/CISO (control environment)
- Security Engineer (technical controls)
- HR Manager (employee lifecycle)
- Operations Lead (monitoring, DR)

## Next Steps

1. Review and approve remediation roadmap
2. Assign owners to each gap remediation
3. Begin evidence collection for completed controls
4. Schedule monthly progress reviews
5. Engage SOC 2 auditor for scoping discussion

Secondary Outputs:

  • Evidence collection checklist (Excel/CSV)
  • Control testing templates
  • Auditor questionnaire responses
  • Gap tracking dashboard (JSON for dashboarding tools)

Error Handling

Common Issues and Resolutions:

  1. Missing Evidence Files

    • Error: "Cannot locate security policy in {baseDir}/docs/"
    • Resolution: Request document locations from user
    • Fallback: Mark as evidence gap in report
  2. Incomplete Access Logs

    • Error: "Log retention < SOC 2 requirement (1 year)"
    • Resolution: Note current retention period, flag as gap
    • Remediation: Extend retention, backfill if possible
  3. Undocumented Procedures

    • Error: "No incident response playbook found"
    • Resolution: Flag as critical gap requiring documentation
    • Assistance: Provide template for creating procedure
  4. Cloud Provider Access Required

    • Error: "Cannot assess AWS controls without API access"
    • Resolution: Request CloudTrail exports or console screenshots
    • Alternative: Provide manual checklist for cloud controls
  5. Multiple Environments Not Distinguished

    • Error: "Production and dev configs mixed in {baseDir}/"
    • Resolution: Request environment separation or clear labeling
    • Risk: May audit wrong environment

Resources

SOC 2 Framework References:

Control Implementation Guides:

Compliance Automation Tools:

  • Drata: SOC 2 compliance automation
  • Vanta: Continuous compliance monitoring
  • Secureframe: Evidence collection platform

Template Documents:

  • Information Security Policy: {baseDir}/templates/security-policy-template.md
  • Incident Response Plan: {baseDir}/templates/incident-response-template.md
  • Risk Assessment Template: {baseDir}/templates/risk-assessment-template.xlsx

Auditor Resources:

  • Find SOC 2 auditors: https://www.aicpa.org/
  • SOC 2 vs ISO 27001 comparison
  • Type I vs Type II audit differences

Evidence Examples:

  • Sample SOC 2 control matrix
  • Evidence collection best practices
  • Auditor interview preparation guide

GitHub Repository

jeremylongshore/claude-code-plugins-plus
Path: plugins/security/soc2-audit-helper/skills/soc2-audit-helper
aiautomationclaude-codedevopsmarketplacemcp

Related Skills

sglang

Meta

SGLang is a high-performance LLM serving framework that specializes in fast, structured generation for JSON, regex, and agentic workflows using its RadixAttention prefix caching. It delivers significantly faster inference, especially for tasks with repeated prefixes, making it ideal for complex, structured outputs and multi-turn conversations. Choose SGLang over alternatives like vLLM when you need constrained decoding or are building applications with extensive prefix sharing.

View skill

Algorithmic Art Generation

Meta

This skill helps developers create algorithmic art using p5.js, focusing on generative art, computational aesthetics, and interactive visualizations. It automatically activates for topics like "generative art" or "p5.js visualization" and guides you through creating unique algorithms with features like seeded randomness, flow fields, and particle systems. Use it when you need to build reproducible, code-driven artistic patterns.

View skill

llamaindex

Meta

LlamaIndex is a data framework for building RAG-powered LLM applications, specializing in document ingestion, indexing, and querying. It provides key features like vector indices, query engines, and agents, and supports over 300 data connectors. Use it for document Q&A, chatbots, and knowledge retrieval when building data-centric applications.

View skill

canvas-design

Meta

The canvas-design skill generates original visual art in PNG and PDF formats for creating posters, designs, and other static artwork. It operates through a two-step process: first creating a design philosophy document, then visually expressing it on a canvas. The skill focuses on original compositions using form, color, and space while avoiding copyright infringement by never copying existing artists' work.

View skill