Performing Soc2 Type2 Audit Preparation

---
name: performing-soc2-type2-audit-preparation
description: Use when automating SOC 2 Type II audit preparation including gap assessment
  against AICPA Trust Services Criteria (CC1-CC9), evidence collection from cloud
  providers and identity systems, control testing validation, remediation tracking,
  and continuous compliance monitoring. Covers all five TSC categories (Security,
  Availability, Processing Integrity, Confidentiality, Privacy) with automated evidence
  gathering from AWS, Azure, GCP, Okta, GitHub, and Jira.
domain: cybersecurity
tags:
- performing
- soc2
- type2
- audit
- preparation
- compliance
- grc
subdomain: governance-risk-compliance
version: '1.0'
author: oyi77
license: Apache-2.0
nist_csf:
- GV.OC-01
- GV.RM-01
- GV.PO-01
- GV.OV-01
category: cybersecurity
---

# Performing Soc2 Type2 Audit Preparation

## Overview

Cybersecurity skill for performing soc2 type2 audit preparation. Follows industry best practices and security standards.

## When to Use
**Trigger phrases:**
- "performing soc2 type2 audit preparation"
- "Automates SOC 2 Type II audit preparation including gap assessment against AICPA"


- When preparing for a SOC 2 Type II audit engagement with a CPA firm
- When conducting a gap assessment against AICPA Trust Services Criteria
- When automating evidence collection across cloud infrastructure and identity providers
- When validating that controls have operated effectively over the audit period (3-12 months)
- When building continuous compliance monitoring to maintain SOC 2 posture between audits
- When remediating control gaps identified during readiness assessment


## When NOT to Use

- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope


## Prerequisites

- Familiarity with AICPA Trust Services Criteria (CC1-CC9)
- Access to cloud provider APIs (AWS, Azure, or GCP) with read-only permissions
- Access to identity provider (Okta, Azure AD, Google Workspace)
- Access to version control system (GitHub, GitLab)
- Access to ticketing system (Jira, Linear, ServiceNow)
- Python 3.8+ with `boto3`, `requests`, `pyyaml` dependencies
- Appropriate authorization to collect compliance evidence

## Workflow

```python
# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> dict:
    return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
```

1. **Plan Operations** — Define objectives, scope, and success criteria for soc2 type2 audit preparation operations.
2. **Prepare Environment** — Set up tools, access, and data sources required for soc2 type2 audit preparation.
3. **Execute Core Workflow** — Perform the soc2 type2 audit preparation operations following established procedures.
4. **Validate Results** — Verify that results meet quality standards and objectives.
5. **Report Findings** — Document results, observations, and recommendations.
6. **Follow Up** — Track remediation actions and verify fixes where applicable.

## Tools

- **Analysis Platform** — Data processing and visualization
- **Collaboration Tools** — Team coordination and knowledge sharing


## Process

1. **Design** — Define interface, identify patterns, plan implementation
1. **Implement** — Write code following existing conventions, add tests
1. **Verify** — Run tests, check integration, validate behavior

## Verification

- [ ] All soc2 type2 audit preparation procedures executed completely and documented
- [ ] Findings validated against multiple data sources
- [ ] False positives identified and filtered
- [ ] Results documented with evidence and timestamps
- [ ] Recommendations provided with risk-based prioritization

## Anti-Rationalization Table

| Rationalization | Reality |
|---|---|
| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |
| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |