Skip to content

borghei/Claude-Skills / ra-qm-team/soc2-compliance-expert

soc2-compliance-expert

Verified

SOC 2 Type I and Type II compliance management against the Trust Services Criteria. Use for SOC 2 readiness assessments, TSC gap analysis, audit evidence collection, infrastructure control validation, and CPA firm audit preparation.

references/audit-preparation-playbook.md

View on GitHub
# SOC 2 Audit Preparation Playbook

End-to-end guide for preparing, executing, and maintaining SOC 2 compliance, from initial scoping through post-audit continuous compliance.

---

## Pre-Audit Checklist

### 90-Day Milestone (T-90 Days)

**Scope and Planning:**
- [ ] Define TSC categories in scope (Security is mandatory; add Availability, Processing Integrity, Confidentiality, Privacy as needed)
- [ ] Define system boundaries (which systems, data stores, networks are in scope)
- [ ] Identify subservice organizations (AWS, GCP, Azure, SaaS vendors)
- [ ] Decide carve-out vs. inclusive method for subservice organizations
- [ ] Document principal service commitments and system requirements
- [ ] Identify complementary user entity controls (CUECs)
- [ ] Determine audit type (Type I first, then Type II, or directly to Type II)
- [ ] Establish SOC 2 project team with executive sponsor

**Gap Analysis:**
- [ ] Inventory all existing policies and procedures
- [ ] Map current controls to TSC requirements (use `soc2_readiness_checker.py`)
- [ ] Interview process owners for each control domain
- [ ] Review existing security assessments, pen tests, and audits
- [ ] Document all gaps with severity and remediation effort estimates
- [ ] Create prioritized remediation roadmap

**Auditor Selection (begin process):**
- [ ] Research CPA firms with SOC 2 experience in your industry
- [ ] Request proposals from 2-3 firms
- [ ] Evaluate based on: experience, methodology, team, timeline, cost
- [ ] Check references from similar-sized companies
- [ ] Negotiate scope, timeline, and fees

### 60-Day Milestone (T-60 Days)

**Policy and Procedure Development:**
- [ ] Information security policy (comprehensive, board-approved)
- [ ] Acceptable use policy
- [ ] Access control policy
- [ ] Data classification and handling policy
- [ ] Change management policy
- [ ] Incident response plan
- [ ] Business continuity / disaster recovery plan
- [ ] Vendor management policy
- [ ] Data retention and disposal policy
- [ ] Password and authentication policy
- [ ] Encryption policy
- [ ] Privacy policy (if Privacy in scope)
- [ ] Employee handbook security section
- [ ] Deploy all policies via centralized policy management system
- [ ] Collect employee acknowledgments for all policies

**Technical Controls Implementation:**
- [ ] Identity provider configured (SSO, MFA enforced for all users)
- [ ] SIEM deployed with log sources from all critical systems
- [ ] Endpoint security deployed (EDR, MDM, disk encryption)
- [ ] Vulnerability scanning configured (internal + external, monthly)
- [ ] Network security configured (firewalls, WAF, segmentation)
- [ ] Encryption at rest enabled for all data stores
- [ ] TLS 1.2+ enforced on all endpoints
- [ ] Backup and recovery configured with encryption
- [ ] CI/CD pipeline security (branch protection, code review, SAST)
- [ ] Secret scanning enabled (pre-commit + CI)
- [ ] DNS security configured (SPF, DKIM, DMARC, DNSSEC, CAA)

**Process Implementation:**
- [ ] Access request and approval workflow operational
- [ ] Access review schedule defined and first review completed
- [ ] Change management workflow operational
- [ ] Incident response team designated and trained
- [ ] Vendor risk assessment program launched
- [ ] Security awareness training deployed
- [ ] Offboarding/deprovisioning process documented and tested

### 30-Day Milestone (T-30 Days)

**Evidence Collection Setup:**
- [ ] Evidence repository structure created (organized by TSC category)
- [ ] Evidence collection calendar established
- [ ] Evidence owners assigned per control domain
- [ ] Automated evidence collection configured (GRC platform or manual process)
- [ ] Initial evidence collection completed for all controls
- [ ] Evidence gaps identified and collection plans in place

**Pre-Audit Readiness:**
- [ ] Internal readiness assessment completed (mock audit)
- [ ] Run `soc2_infrastructure_auditor.py` for technical validation
- [ ] Run `evidence_collector.py` to verify evidence completeness
- [ ] All critical and high gaps remediated
- [ ] System description draft completed
- [ ] Management assertion drafted
- [ ] Auditor engagement letter signed
- [ ] Audit kickoff meeting scheduled
- [ ] Key personnel briefed on auditor interactions

**Training and Preparation:**
- [ ] All employees completed security awareness training
- [ ] Control owners prepared for auditor interviews
- [ ] FAQ document for common auditor questions distributed
- [ ] Interview preparation sessions conducted
- [ ] Evidence request list reviewed and pre-staged

---

## Auditor Selection Criteria

### Evaluation Framework

| Criterion | Weight | Key Questions |
|-----------|--------|---------------|
| **SOC 2 Experience** | 25% | How many SOC 2 audits annually? Industry-specific experience? |
| **Team Quality** | 20% | CPA credentials? CISA certifications? Dedicated engagement team? |
| **Methodology** | 15% | How is evidence collected? What is the testing approach? Technology used? |
| **Timeline** | 15% | Can they meet our target timeline? Flexibility for observation period? |
| **Cost** | 10% | Total engagement cost? Payment structure? Included vs. additional fees? |
| **References** | 10% | References from similar companies? Retention rate? |
| **Communication** | 5% | Responsiveness? Dedicated point of contact? Collaboration tools? |

### Key Questions for Prospective Auditors

1. How many SOC 2 engagements has your firm completed in the past year?
2. Do you have experience in our specific industry/technology stack?
3. What does your evidence collection process look like? Do you use a GRC platform?
4. How do you handle exceptions and qualified findings?
5. What is your typical turnaround time from fieldwork completion to report issuance?
6. Can you provide a sample report (redacted) for reference?
7. What is the engagement team structure (partner, manager, staff)?
8. How do you handle questions or disagreements during fieldwork?
9. What is included in the engagement fee vs. billed separately?
10. Do you offer a readiness assessment as a pre-engagement service?

### Red Flags in Auditor Selection

- Firm has limited SOC 2 experience (fewer than 20 engagements annually)
- Cannot provide references from similar-sized companies
- Unwilling to share methodology or sample report
- Significantly lower price than competitors (may indicate less thorough testing)
- High staff turnover on engagement teams
- No dedicated technology or platform for evidence collection
- Inflexible timeline with no accommodation for observation period

---

## System Description Preparation

### Required Content (Section III)

The system description is the most time-intensive document for first-time SOC 2 reports. It must cover:

#### 1. Services Provided
- Description of the services your organization provides
- Customer types and markets served
- Service delivery model (SaaS, PaaS, managed services)

#### 2. Principal Service Commitments
- Security commitments (data protection, access controls)
- Availability commitments (uptime SLAs, recovery objectives)
- Processing integrity commitments (data accuracy, timeliness)
- Confidentiality commitments (data classification, encryption)
- Privacy commitments (data handling practices)

#### 3. System Components

**Infrastructure:**
- Cloud providers and services used
- Data center locations
- Network architecture (high-level)
- Production environment description

**Software:**
- Core application technology stack
- Third-party software and services
- Monitoring and security tools
- Database technologies

**People:**
- Organizational structure for system operations
- Key roles (CISO, CTO, engineering leads, security team)
- Training requirements
- Background check policies

**Procedures:**
- Access management procedures
- Change management procedures
- Incident response procedures
- Monitoring and alerting procedures
- Backup and recovery procedures

**Data:**
- Types of data processed
- Data classification levels
- Data flow overview (how data enters, moves through, and exits the system)
- Data retention practices

#### 4. System Boundaries
- What is IN scope (systems, data, locations)
- What is OUT of scope (with justification)
- Interconnections with other systems

#### 5. Subservice Organizations
- List of subservice organizations relied upon
- Services provided by each
- Carve-out or inclusive treatment
- Relevant controls (CSOCs)

#### 6. Complementary User Entity Controls (CUECs)
- Controls customers are expected to implement
- Examples: securing their own credentials, configuring their own access controls, managing their own backup of exported data

### System Description Best Practices

- Engage the auditor to review the draft system description before fieldwork
- Use diagrams (data flow, network architecture) to supplement text
- Be specific about technologies and configurations
- Update the system description for any significant changes during the observation period
- Have the system description reviewed by engineering, security, and legal teams
- Version control the system description with change tracking

---

## Management Assertion Writing

### Structure

The management assertion is a formal statement from the organization's management that accompanies the SOC 2 report.

**Required Elements:**
1. Statement that the system description is fairly presented
2. Statement that controls are suitably designed (Type I) / designed and operating effectively (Type II)
3. Statement regarding the criteria used (Trust Services Criteria)
4. Description of the period covered

### Template

> **Management's Assertion**
>
> We have prepared the accompanying description of [Company Name]'s [System Name] system (the "System Description") throughout the period [Start Date] to [End Date] (the "Period"), based on the criteria for a description of a service organization's system in DC Section 200, 2018 Description Criteria for a Description of a Service Organization's System in a SOC 2 Report.
>
> We confirm, to the best of our knowledge and belief, that:
>
> a. The description fairly presents the [System Name] system that was designed and implemented throughout the Period.
>
> b. The controls stated in the description were suitably designed and operating effectively to provide reasonable assurance that the service commitments and system requirements were achieved based on the applicable trust services criteria throughout the Period.
>
> c. The criteria we used in making this assertion were the Trust Services Criteria established by the AICPA (TSP Section 100, 2017 Trust Services Criteria for Security, Availability, Processing Integrity, Confidentiality, and Privacy).

---

## Evidence Organization Strategies

### Folder Structure

```
soc2-evidence/
├── 01-control-environment/
│   ├── CC1.1-code-of-conduct/
│   │   ├── code-of-conduct-policy-v2.1.pdf
│   │   └── employee-acknowledgments-2026.csv
│   ├── CC1.2-board-oversight/
│   │   ├── board-meeting-minutes-Q1-2026.pdf
│   │   └── security-committee-charter.pdf
│   └── ...
├── 02-communication/
├── 03-risk-assessment/
├── 04-monitoring/
├── 05-control-activities/
├── 06-access-controls/
├── 07-system-operations/
├── 08-change-management/
├── 09-risk-mitigation/
├── 10-availability/
├── 11-processing-integrity/
├── 12-confidentiality/
├── 13-privacy/
├── system-description/
│   ├── system-description-v1.0.docx
│   ├── data-flow-diagram.png
│   └── network-architecture.png
└── management-assertion/
    └── management-assertion-signed.pdf
```

### Naming Conventions

Format: `[TSC-ID]_[Description]_[Date].[ext]`

Examples:
- `CC6.1_MFA-enrollment-report_2026-03.pdf`
- `CC7.1_vuln-scan-external_2026-02.pdf`
- `CC8.1_change-tickets-sample_2026-Q1.xlsx`
- `A1.2_DR-test-results_2026-01.pdf`

### Evidence Quality Checklist

For each evidence artifact, verify:
- [ ] Dated within the observation period
- [ ] Shows the complete control (not partial)
- [ ] Clearly readable (not blurry screenshots)
- [ ] Sensitive data redacted (PII, passwords, keys)
- [ ] Consistent with system description
- [ ] Attribution clear (who performed the control)
- [ ] Standalone comprehensible (auditor can understand without explanation)

---

## Common Deficiency Types and Responses

### Deficiency Classification

| Type | Definition | Report Impact |
|------|-----------|--------------|
| **Exception** | Control operated but a specific instance failed | Noted in report but may not affect opinion |
| **Deficiency** | Control design gap or consistent operating failure | Noted in report, may affect opinion |
| **Significant Deficiency** | Deficiency severe enough to warrant attention | Prominently noted, likely affects opinion |
| **Material Weakness** | Reasonable possibility of material misstatement | Qualified or adverse opinion |

### Top Deficiency Categories and Mitigation

**1. Access Control Deficiencies (Most Common)**

*Examples:*
- Terminated user access not removed within 24 hours
- MFA not enforced for all users
- Access reviews not completed on schedule

*Mitigation:*
- Automate deprovisioning via HRIS-IdP integration (SCIM)
- Enforce MFA at IdP level with no exceptions
- Automate access review scheduling with escalation

**2. Change Management Deficiencies**

*Examples:*
- Changes deployed without documented approval
- Code reviews bypassed
- Emergency changes without post-hoc review

*Mitigation:*
- Enforce branch protection (approvals required, no bypass)
- Implement CI/CD gates that block without approval
- Create emergency change tracking with 48-hour review requirement

**3. Monitoring Deficiencies**

*Examples:*
- Insufficient log coverage
- Alerts not responded to within SLA
- Vulnerability scan gaps

*Mitigation:*
- Audit log sources against system inventory monthly
- Implement alert response SLAs with tracking
- Automate vulnerability scanning schedule

**4. Vendor Management Deficiencies**

*Examples:*
- Critical vendor SOC 2 reports not collected
- Vendor risk assessments not performed annually
- Missing DPAs

*Mitigation:*
- Create vendor review calendar with automated reminders
- Template vendor security questionnaire for efficiency
- Centralize vendor management in GRC platform

**5. Documentation Deficiencies**

*Examples:*
- Policies not reviewed within 12 months
- System description inaccurate
- Missing evidence for controls

*Mitigation:*
- Implement policy management system with review reminders
- Update system description with every significant change
- Establish evidence collection calendar and ownership

### Responding to Auditor Findings

1. **Do not argue the finding.** Understand what the auditor observed.
2. **Provide context.** Explain any compensating controls or mitigating circumstances.
3. **Accept the finding** and commit to a remediation timeline.
4. **Document the root cause** (process gap, tool limitation, human error).
5. **Implement the fix** and document evidence of remediation.
6. **Verify** the fix addresses the root cause, not just the symptom.

### Management Response Template

> **Finding:** [Auditor's description of the deficiency]
>
> **Management Response:** Management acknowledges this finding. The root cause was [explanation]. We have implemented [remediation actions] effective [date]. Specifically:
> - [Action 1 with owner and completion date]
> - [Action 2 with owner and completion date]
>
> We believe these actions adequately address the identified deficiency and will prevent recurrence. We will verify effectiveness through [monitoring approach].

---

## Post-Audit Remediation Tracking

### Remediation Register

| Finding ID | Category | Severity | Description | Root Cause | Remediation Action | Owner | Target Date | Status | Evidence |
|-----------|----------|----------|-------------|-----------|-------------------|-------|-------------|--------|----------|
| F-001 | CC6.3 | High | Access review not completed in Q2 | Manual process, no calendar | Automate review scheduling | IAM Lead | 2026-04-15 | Complete | Screenshot |
| F-002 | CC8.1 | Medium | 2 changes without approval | Emergency process unclear | Define emergency change criteria | Eng Manager | 2026-04-30 | In Progress | Policy draft |

### Remediation SLAs

| Severity | SLA | Escalation |
|----------|-----|-----------|
| Critical | 30 days | CISO + Executive sponsor |
| High | 60 days | CISO |
| Medium | 90 days | Security Manager |
| Low | Next audit cycle | Security Analyst |

---

## Continuous Compliance Maintenance

### Monthly Activities

- [ ] Review security monitoring alerts and response metrics
- [ ] Verify vulnerability scanning completed (internal + external)
- [ ] Check MFA enrollment report (100% compliance)
- [ ] Review access provisioning/deprovisioning tickets
- [ ] Verify backup success and test restoration
- [ ] Review change management tickets for compliance
- [ ] Update evidence repository with monthly artifacts
- [ ] Check phishing simulation results
- [ ] Review endpoint compliance (EDR, encryption, patches)
- [ ] Verify log ingestion and SIEM health

### Quarterly Activities

- [ ] Complete privileged access review
- [ ] Service account access review
- [ ] Conduct incident response tabletop exercise
- [ ] Review vendor security (critical vendors)
- [ ] Update risk register
- [ ] Security metrics report to management
- [ ] Review and update system description (if changes occurred)
- [ ] Third-party access review
- [ ] Review and test DR/backup procedures

### Semi-Annual Activities

- [ ] Complete standard user access review
- [ ] DR failover test
- [ ] Communication tree test
- [ ] Review and update BIA
- [ ] Security program effectiveness assessment
- [ ] Review insurance coverage adequacy

### Annual Activities

- [ ] Comprehensive risk assessment
- [ ] Policy review and update cycle (all policies)
- [ ] Penetration testing (external, may be quarterly)
- [ ] Security awareness training (refresh for all employees)
- [ ] Board/committee annual security briefing
- [ ] Code of conduct acknowledgment renewal
- [ ] Background check compliance review
- [ ] Vendor reassessment (all critical and high vendors)
- [ ] SOC 2 report renewal planning (begin 3 months before observation period ends)
- [ ] Privacy impact assessment review
- [ ] Data retention schedule review
- [ ] Encryption key rotation verification
- [ ] Incident response plan update
- [ ] DR plan update

### Compliance Calendar Template

| Month | Week 1 | Week 2 | Week 3 | Week 4 |
|-------|--------|--------|--------|--------|
| **Jan** | Vuln scan, MFA check | Access review (Q4 priv) | Risk register update | Security metrics report |
| **Feb** | Vuln scan, MFA check | Backup test | Vendor review (critical) | IR tabletop |
| **Mar** | Vuln scan, MFA check | Standard access review | Policy review cycle starts | DR failover test |
| **Apr** | Vuln scan, MFA check | Access review (Q1 priv) | Risk register update | Security metrics report |
| **May** | Vuln scan, MFA check | Backup test | Vendor review | IR tabletop |
| **Jun** | Vuln scan, MFA check | Pen test planning | Annual risk assessment | Communication tree test |
| **Jul** | Vuln scan, MFA check | Access review (Q2 priv) | Pen test execution | Security metrics report |
| **Aug** | Vuln scan, MFA check | Backup test | Vendor review (critical) | IR tabletop |
| **Sep** | Vuln scan, MFA check | Standard access review | Policy update completion | DR failover test |
| **Oct** | Vuln scan, MFA check | Access review (Q3 priv) | Risk register update | Security metrics report |
| **Nov** | Vuln scan, MFA check | Backup test | Vendor review | IR tabletop |
| **Dec** | Vuln scan, MFA check | Annual security training | Board security briefing | Year-end compliance review |

---

## Cost Estimation Framework

### First-Year SOC 2 Costs

| Cost Category | Type I | Type II | Notes |
|--------------|--------|---------|-------|
| **Audit fees** | $20K-$60K | $40K-$100K | Varies by firm, scope, and company size |
| **GRC platform** | $10K-$30K/yr | $10K-$30K/yr | Vanta, Drata, Secureframe, Laika |
| **Security tooling** | $5K-$50K/yr | $5K-$50K/yr | SIEM, EDR, vulnerability scanner (may already exist) |
| **Penetration test** | $10K-$30K | $10K-$30K | Annual, scope-dependent |
| **Internal labor** | 200-500 hours | 400-1000 hours | Policy writing, evidence collection, remediation |
| **Consulting** (optional) | $10K-$40K | $15K-$50K | Readiness assessment, gap remediation support |
| **Training** | $2K-$5K | $2K-$5K | Security awareness platform |
| **Total (estimated)** | **$40K-$120K** | **$80K-$250K** | First year including setup costs |

### Annual Renewal Costs

| Cost Category | Annual Cost | Notes |
|--------------|------------|-------|
| **Audit fees** | $30K-$80K | Typically lower than first year |
| **GRC platform** | $10K-$30K/yr | Ongoing subscription |
| **Security tooling** | $5K-$50K/yr | Ongoing licensing |
| **Penetration test** | $10K-$30K | Annual requirement |
| **Internal labor** | 200-400 hours | Evidence maintenance, remediation |
| **Total (estimated)** | **$55K-$150K** | Annual ongoing cost |

### Cost Optimization Strategies

1. **Use a GRC platform** to automate evidence collection (saves 200+ hours annually)
2. **Start with Type I** to validate control design before committing to Type II observation period
3. **Scope carefully** -- only include TSC categories required by customers
4. **Use cloud-native security tools** (many are included in cloud provider pricing)
5. **Combine audits** if pursuing multiple certifications (ISO 27001 + SOC 2 unified audit)
6. **Negotiate multi-year audit contracts** for reduced annual fees
7. **Invest in automation** (automated access reviews, SCIM provisioning, CI/CD security gates)

### ROI Justification

| Benefit | Impact |
|---------|--------|
| **Shorter sales cycles** | Enterprise deals close 2-4 weeks faster with SOC 2 |
| **Reduced security questionnaires** | SOC 2 report answers 80%+ of customer security questions |
| **Competitive advantage** | Required by most enterprise buyers (eliminates deals lost to competitors with SOC 2) |
| **Insurance premiums** | Cyber insurance premiums may decrease 5-15% |
| **Incident prevention** | Controls reduce likelihood and impact of security incidents |
| **Regulatory readiness** | SOC 2 controls align with GDPR, HIPAA, PCI-DSS requirements |

### Timeline to Revenue Impact

| Milestone | Timeline | Revenue Impact |
|-----------|----------|---------------|
| SOC 2 Type I report | 3-6 months | Unlocks mid-market deals |
| SOC 2 Type II report | 9-18 months | Unlocks enterprise deals |
| Continuous compliance | Ongoing | Faster renewals, reduced churn |

---

## GRC Platform Comparison

| Platform | Pricing (approx.) | Strengths | Best For |
|----------|-------------------|----------|----------|
| **Vanta** | $10K-$30K/yr | Most integrations, easy setup | Startups, SMBs |
| **Drata** | $10K-$25K/yr | Good UX, automated evidence | Growth-stage companies |
| **Secureframe** | $10K-$25K/yr | Multi-framework support | Companies needing SOC 2 + ISO |
| **Laika** | $15K-$30K/yr | Compliance-as-a-service | Companies wanting managed compliance |
| **Tugboat Logic** (OneTrust) | $15K-$35K/yr | Policy templates, risk management | Mid-market companies |
| **AuditBoard** | $25K-$75K/yr | Enterprise GRC, internal audit | Large enterprises |
| **Sprinto** | $8K-$20K/yr | Automated testing, good value | Cost-conscious startups |

**Selection Criteria:**
- Number of native integrations with your technology stack
- Automated evidence collection coverage
- Auditor collaboration portal
- Multi-framework support (if pursuing SOC 2 + ISO 27001)
- Policy management and employee acknowledgment tracking
- Pricing model (per-user, flat-rate, or scope-based)

---

## Common Mistakes to Avoid

1. **Starting the observation period before controls are ready.** Every control must be operational before the clock starts. Gaps during observation become findings.

2. **Treating SOC 2 as a one-time project.** SOC 2 requires continuous compliance. Build sustainable processes, not one-time fixes.

3. **Over-scoping.** Include only the TSC categories your customers require. Each additional category adds cost and complexity.

4. **Under-investing in evidence collection.** Auditors need evidence. If you cannot prove a control exists and operates, it effectively does not exist.

5. **Waiting until fieldwork to prepare evidence.** Start collecting evidence from day one of the observation period. Do not scramble during fieldwork.

6. **Ignoring complementary user entity controls (CUECs).** If your service requires customers to implement certain controls (e.g., securing their credentials), document these in the system description.

7. **Not preparing employees for auditor interviews.** Auditors will interview control owners. Prepare employees with common questions and ensure they know what controls they operate.

8. **Choosing the cheapest auditor.** A poor audit experience wastes time and may require rework. Choose auditors with relevant experience and good communication.

9. **Not addressing prior-year findings.** If you had findings in a previous audit, address them before the next observation period. Repeat findings raise auditor concerns.

10. **Manual processes that cannot scale.** Automate where possible (access reviews, evidence collection, vulnerability scanning). Manual processes break under growth.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall