Performing SOC 2 Type II Audit Preparation

Overview

SOC 2 Type II audit preparation involves designing, implementing, and demonstrating the operational effectiveness of controls aligned to the AICPA Trust Services Criteria (TSC) over a defined audit period (typically 6-12 months). Unlike Type I which assesses control design at a point in time, Type II evaluates whether controls operated effectively throughout the entire examination period.

Prerequisites

• Understanding of AICPA Trust Services Criteria (2017, updated 2022)
• Knowledge of internal control frameworks (COSO 2013)
• Familiarity with organizational IT infrastructure and data flows
• Access to GRC (Governance, Risk, Compliance) tooling

Core Concepts

Trust Services Criteria (TSC)

Five categories, with Security (Common Criteria) being mandatory:

Criteria	Description	Required
Security (CC)	Protection against unauthorized access	Mandatory
Availability (A)	System availability for operation and use	Optional
Processing Integrity (PI)	System processing is complete, valid, accurate, timely, authorized	Optional
Confidentiality (C)	Information designated as confidential is protected	Optional
Privacy (P)	Personal information collected, used, retained, disclosed per notice	Optional

Common Criteria (CC Series)

Security is organized into 9 series based on COSO principles:

Series	Focus Area	COSO Principle
CC1	Control Environment	Integrity and ethical values
CC2	Communication and Information	Quality information for controls
CC3	Risk Assessment	Identify and assess risks
CC4	Monitoring Activities	Monitor and evaluate controls
CC5	Control Activities	Select and develop controls
CC6	Logical and Physical Access	Restrict access to authorized users
CC7	System Operations	Detect and respond to system anomalies
CC8	Change Management	Authorized, tested, approved changes
CC9	Risk Mitigation	Risk mitigation through business processes

Type I vs Type II

Aspect	Type I	Type II
Scope	Control design at a point in time	Control effectiveness over a period
Audit Period	Single date	6-12 months (typically 12)
Evidence	Design documentation	Operating evidence throughout period
Assurance	Lower	Higher
Market Value	Initial baseline	Industry standard expectation

Implementation Steps

Phase 1: Scoping and Readiness (Weeks 1-4)

1. Determine which TSC categories to include (Security mandatory, others based on customer needs)
2. Define system boundaries and description components:

• Infrastructure (servers, networks, cloud services)
• Software (applications, operating systems)
• People (roles, responsibilities)
• Procedures (automated and manual)
• Data (data flows, classification)

1. Select audit firm (CPA firm with SOC experience)
2. Define audit window (start and end dates)
3. Conduct readiness assessment against selected criteria

Phase 2: Control Design and Implementation (Weeks 5-16)

1. Map organizational controls to TSC criteria
2. Design controls for each applicable criterion:

• CC6.1: Logical access security (SSO, MFA, RBAC)
• CC6.2: System credential management
• CC6.3: Access removal upon termination
• CC7.1: Intrusion detection and monitoring
• CC7.2: Security incident response
• CC8.1: Change management process

1. Implement technical controls:

• Identity provider (Okta, Azure AD)
• Endpoint detection and response
• SIEM for log aggregation
• Vulnerability scanning
• Encryption at rest and in transit

1. Implement administrative controls:

• Security policies and procedures
• Background check process
• Security awareness training
• Vendor management programme

1. Document all controls with:

• Control objective
• Control activity description
• Frequency (continuous, daily, weekly, quarterly, annual)
• Control owner
• Evidence type (screenshot, report, ticket, log)

Phase 3: Evidence Collection Period (Audit Window)

1. Operate controls consistently throughout the audit period
2. Collect and organize evidence:

• Access review completion records (quarterly)
• Change management tickets and approvals
• Incident response logs
• Vulnerability scan reports
• Penetration test results
• Training completion records
• Backup verification logs
• System availability reports

1. Maintain evidence repository with clear naming conventions
2. Track control failures and exceptions
3. Implement remediation for any control gaps identified during the period

Phase 4: Pre-Audit Preparation (Weeks before audit)

1. Perform internal control testing (walkthroughs)
2. Prepare system description document
3. Organize evidence by TSC criterion
4. Brief control owners on audit process
5. Prepare management assertion letter
6. Identify and remediate any last-minute gaps

Phase 5: Audit Execution

1. Auditor performs inquiry, observation, inspection, and reperformance
2. Provide requested evidence and access
3. Respond to auditor questions and information requests
4. Address any exceptions identified during testing
5. Review draft report for factual accuracy

Phase 6: Report and Remediation

1. Receive SOC 2 Type II report
2. Address any qualified opinions or control exceptions
3. Distribute report to customers (typically under NDA)
4. Plan remediation for identified exceptions
5. Begin preparing for next audit cycle

Key Artifacts

• System Description Document
• Control Matrix (TSC mapping)
• Risk Assessment Documentation
• Evidence Repository
• Management Assertion Letter
• SOC 2 Type II Report (Sections I-V)
• Remediation Plan for Exceptions

Common Pitfalls

• Starting evidence collection too late - need full audit period coverage
• Inconsistent control operation (e.g., missing quarterly access reviews)
• Insufficient system description detail
• Not including subservice organizations (IaaS providers)
• Failing to document complementary user entity controls (CUECs)
• Manual controls without documented evidence of execution

Verification Criteria

Confirm successful execution by validating:

• [ ] All prerequisite tools and access requirements are satisfied
• [ ] Each workflow step completed without errors
• [ ] Output matches expected format and contains expected data
• [ ] No security warnings or misconfigurations detected
• [ ] Results are documented and evidence is preserved for audit

Compliance Framework Mapping

This skill supports compliance evidence collection across multiple frameworks:

• SOC 2: CC1.1 (Control Environment), CC2.1 (Information & Communication)
• ISO 27001: Clause 4-10 (ISMS Requirements)
• NIST 800-53: PM-1 (Security Program Plan), PL-2 (System Security Plan)
• NIST CSF: ID.GV (Governance), ID.RM (Risk Management Strategy)

Claw GRC Tip: When this skill is executed by a registered agent, compliance evidence is automatically captured and mapped to the relevant controls in your active frameworks.

Deploying This Skill with Claw GRC

Agent Execution

Register this skill with your Claw GRC agent for automated execution:

# Install via CLI
npx claw-grc skills add performing-soc2-type2-audit-preparation

# Or load dynamically via MCP
grc.load_skill("performing-soc2-type2-audit-preparation")

Audit Trail Integration

When executed through Claw GRC, every step of this skill generates tamper-evident audit records:

• SHA-256 chain hashing ensures no step can be modified after execution
• Evidence artifacts (configs, scan results, logs) are automatically attached to relevant controls
• Trust score impact — successful execution increases your agent's trust score

Continuous Compliance

Schedule this skill for recurring execution to maintain continuous compliance posture. Claw GRC monitors for drift and alerts when re-execution is needed.

References

• AICPA Trust Services Criteria 2017 (updated 2022): https://www.aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2
• AICPA SOC 2 Reporting Guide
• COSO Internal Control Framework 2013
• Secureframe SOC 2 Trust Services Criteria Guide: https://secureframe.com/hub/soc-2/trust-services-criteria