Compliance / SOC 2
SOC 2 penetration testing, without the audit scramble.
The honest requirement
Pen testing isn't literally in the TSC — but auditors expect it anyway.
The AICPA's Trust Services Criteria do not name "penetration testing" as a mandatory control. The word doesn't appear in CC1–CC9. So technically, no — SOC 2 does not require a pen test to pass.
In practice: assessors want evidence of vulnerability identification and control-effectiveness testing, particularly under CC4.1 (monitoring of controls) and CC7.1 (detection and monitoring of new vulnerabilities). An annual third-party pen test has become the de facto way service organizations satisfy those criteria, and most SOC 2 audit programs now list it in the request-for-evidence template. Skip it and you'll spend the audit explaining why you didn't do it — that's the "audit scramble."
Which criteria your report ends up supporting: CC4.1 (separate evaluations),CC6.1 / CC6.6 / CC6.8 (logical access, boundary protection, unauthorized software), CC7.1 / CC7.2 (vulnerability detection and anomaly monitoring), and CC8.1 (change verification, via the retest). Whether you're pursuing Type I or Type II changes the timing of the test, not the criteria — the comparison and window sequencing below lay out the difference.
Type I vs Type II
Same test. Very different timing.
Type I
Design of controls, at a point in time.
- Auditor asks: were the controls suitably designed as of the report date?
- One pen test, run in the weeks before the report date.
- Report freshness matters more than remediation history.
Type II
Operating effectiveness, across the observation window.
- Auditor asks: did the controls operate effectively throughout the period?
- Pen test run early in the window, so remediation and retest also land inside it.
- Dated artifacts prove the vulnerability-management control actually works.
Sequencing
Where the pen test belongs in a 12-month window.
Run the engagement in the first months of the observation period. That leaves room for remediation and a retest well before fieldwork, so the auditor sees a complete cycle rather than a snapshot. If your window is already underway, we sequence to whatever time is left and tell you honestly what evidence is still achievable.
- 01 · Test
- First findings within 72 hours of kickoff, every engagement. Focused 5 to 7 business days. Standard 7 to 10 business days. Extended 2 to 4 weeks. Dated engagement letter and scope memo.
- 02 · Remediate
- Your engineers work the severity-ranked fix order, with the AI-actionable companion file.
- 03 · Retest
- Free retest of remediated findings within 60 days. Signed retest letter confirming closure.
- 04 · Fieldwork
- Auditor reviews the full cycle — finding, fix, verification — all dated inside the period.
Coverage
Which criteria the engagement produces evidence for.
What auditors accept
Evidence, in the format your assessor already uses.
Dated engagement letter and scope memo on firm letterhead
Severity-ranked findings register with working proof-of-concept and discovery dates
Remediation guidance mapped to CC4.1, CC6.x, CC7.1, and CC7.2
Signed retest letter confirming remediated findings are closed
Control-testing narrative your auditor can attach directly as evidence
Sigma detection rules and attack-chain diagrams for monitoring criteria
Engagement mapping
The D1–D9 engagement, mapped to SOC 2 evidence.
Testing window
D1
Recon & scoping, rules of engagement signed.
D2–3
Surface mapping across external, authenticated, and cloud config surfaces.
D4–6
Exploit reasoning and vulnerability chaining, human-validated.
D7–8
Controlled PoC and lateral-movement testing in lab.
D9
Reporting and live client walkthrough.
SOC 2 FAQ
Frequently asked.
Evidence by framework
Same engagement. Different paperwork.
Auditors read the report as evidence of separate evaluations and vulnerability detection.
Mapped to CC4.1 · CC7.1 · CC7.2
Next step
Scope a SOC 2 pen test.
Thirty-minute scoping call. Fixed-scope quote within one business day. Report and evidence bundle ready for your auditor.