Penetration Testing for SOC 2: What to Test, When, and How to Document It
Understand how penetration testing fits into your SOC 2 program, what scope to specify, and how to turn results into evidence.
Does SOC 2 Require a Pen Test?
Technically, no. The AICPA Trust Services Criteria don't explicitly require penetration testing. However:
For any company beyond the seed stage, an annual pen test is effectively required by market expectations, even if not by the standard.
What to Test
External Network Test
Simulates an attacker from the internet with no prior knowledge. Tests your perimeter: web application firewalls, exposed services, domain configuration, certificate issues. This is the most important test for most SaaS companies.Web Application Test (DAST)
Deep testing of your web application and API endpoints: authentication bypass, injection attacks, broken access control, SSRF, business logic flaws. Usually the highest-value test for SaaS products.Internal Network Test
Simulates an attacker who has already gained a foothold inside your network. Important if you have significant on-premise infrastructure or internal-only services.Social Engineering
Phishing simulation targeting specific individuals. Validates your security awareness training program.
Finding the Right Tester
For SOC 2 purposes, testers should be CREST-accredited or hold relevant certifications (OSCP, CEH). The report needs to be attributable to a qualified, independent third party.
Budget: $10,000 – $30,000 for a web application + external network test from a reputable firm.
The Testing Scope Document
Before testing begins, agree on scope in writing:
- In-scope IP ranges and domains
- Out-of-scope systems (production databases, third-party services)
- Testing window (dates and hours)
- Rules of engagement (no DoS, no data exfiltration)
- Emergency contact procedures if critical infrastructure is affected
Interpreting and Acting on Results
Pen test reports classify findings by severity. Your response SLAs should be:
| Severity | Remediation target |
| Critical | 72 hours |
| High | 2 weeks |
| Medium | 60 days |
| Low | Next quarterly review |
Inform (not just track) remediation status in SecureSpect's pen test module. Each finding has an owner, due date, and remediation notes. Auditors want to see that findings were acted on, not just documented.
Evidence for Auditors
Your auditor will typically ask for:
Share the summary, not the full detailed findings — detailed findings contain vulnerability descriptions that you don't want to distribute broadly.