Does SOC 2 Require a Penetration Test?
SOC 2 doesn't explicitly mandate a pentest, but auditors expect evidence that you test your controls, and a pentest is the standard way to show it. Here's what auditors look for.
By Jay Dabhi, CISM · Cybersecurity Analyst
Updated
No, SOC 2 does not explicitly require a penetration test. But SOC 2 auditors expect evidence that you evaluate whether your security controls work, and the AICPA criteria list penetration testing as one way to do that (under CC4.1, monitoring activities). In practice, most startups going through SOC 2 get a pentest, because it's the clearest evidence an auditor and an enterprise customer will accept.
What SOC 2 actually says
SOC 2 reports are based on the AICPA Trust Services Criteria. The criteria describe outcomes, not specific tools. Two criteria are where penetration testing usually comes in:
- CC4.1, monitoring activities. You select, develop and perform evaluations to confirm your controls are present and functioning. Penetration testing is listed among the types of evaluation that can satisfy this.
- CC7.1, system operations. You use detection and monitoring to identify vulnerabilities and configuration changes. Vulnerability scanning is the usual evidence here; a pentest strengthens it.
Because the criteria are outcome-based, your auditor decides whether your evidence is sufficient. That's why the answer to "is it required?" is technically no, but practically yes.
Why most startups do it anyway
- Auditors expect it. Without a pentest, you need another convincing way to show you test your defenses. Few startups have one.
- Customers ask for it separately. Enterprise security questionnaires routinely ask, "Do you perform annual third-party penetration tests? Provide the latest summary." A SOC 2 report doesn't answer that on its own.
- It finds real problems. Broken access control, authentication flaws and insecure APIs don't show up in policy documents or automated scans.
What auditors look for in pentest evidence
- Independence. A third party, or at least someone who didn't build the system.
- Scope that matches the audit. The product and infrastructure in your SOC 2 system description: your web app, APIs and cloud environment.
- Recency. Within the last 12 months, or inside the audit period.
- Remediation. Evidence that you fixed findings, ideally with a retest showing they're closed.
An executive summary or attestation letter is often enough to share with customers. The full report usually stays with your team and auditor.
When to schedule it
Run the test early enough to fix what it finds before the audit window closes. For a Type I report, test before the "as of" date. For a Type II, test before or early in the observation period, then retest after fixes so the auditor sees the full cycle. See SOC 2 Type I vs Type II for how the two differ.
How startups handle it
- Once a year, manual: a human-led pentest with a report and attestation letter your auditor and customers accept. Bluefire Redteam delivers these for startups.
- Continuously, automated: autonomous testing on every release catches regressions between annual tests. PentestLive is in early access.
Not sure where you stand? Start with the free security score to see what an auditor or buyer would notice first.
Frequently asked questions
Can I pass SOC 2 without a penetration test?
It's possible, because SOC 2 doesn't name a pentest as mandatory, but you'd need other convincing evidence that you evaluate your controls and find vulnerabilities. Most auditors expect a pentest, and most enterprise customers ask for one regardless, so skipping it rarely saves effort.
Does a vulnerability scan count instead of a pentest?
Scans are good evidence for ongoing vulnerability monitoring (often mapped to CC7.1), but they don't show whether weaknesses can actually be exploited. Auditors and buyers usually treat them as complementary, not interchangeable.
When should the pentest happen relative to the audit?
Before or early in your audit period, leaving time to fix findings and retest. For a Type II report, the test should fall inside or just before the observation period so the auditor sees remediation happen.