SOC 2 does not mandate a penetration test. The AICPA criteria name pen testing as one way to evaluate controls under CC4.1. Auditors and enterprise customers treat it as expected evidence. Most companies test at least once a year and after major changes. The test should cover the full SOC 2 system boundary.
"Do we actually need a penetration test for SOC 2?" It is one of the most common questions in any SOC 2 project. The short answer is no on paper and yes in practice. This guide covers what the criteria say and how often to test. It also covers what to scope, what the report needs, and what it costs.
Does SOC 2 require a penetration test?
Not by name. SOC 2 is built on the AICPA's Trust Services Criteria , which describe goals instead of required tests. Organizations design their own controls to meet those goals. The CC4.1 point of focus does name penetration testing as one way to evaluate whether controls work.
In practice the pen test is expected. Drata frames it as a preference and a tradition more than a formal requirement. Skip it and auditors will look hard at how else you proved your controls work. Enterprise buyers usually ask for the pen test report right after your SOC 2 report.
What are the SOC 2 penetration testing requirements at a glance?
None of these items is mandated word for word. They are what auditors commonly expect to see.
| Requirement | Mandated by SOC 2? | What auditors expect | Evidence to keep |
|---|---|---|---|
| A penetration test | No | A test that shows controls work under attack | The full pen test report |
| Frequency | No | At least annually and after major changes | Test dates mapped to your audit window |
| Scope | No | Coverage that matches your SOC 2 system boundary | Scope statement in the report |
| Methodology | No | A documented testing approach | Methodology section of the report |
| Remediation | No | Fix timelines that match severity | Tickets and fix dates for each finding |
| Retesting | No | Proof that fixes work | Retest report or attestation letter |
| Vulnerability scanning | No | Scans at least quarterly | Scan reports and triage records |
Which Trust Services Criteria does a SOC 2 pen test map to?
One test produces evidence for several criteria. CC4.1 and CC7.1 are the two auditors cite most. Blaze InfoSec notes that pen testing is often used to satisfy both.
| Criterion | What it requires | How a pen test maps |
|---|---|---|
| CC4.1 (Monitoring Activities) | Evaluations confirming controls are present and working | The AICPA names penetration testing as an evaluation method |
| CC7.1 (System Operations) | Procedures to find vulnerabilities and misconfigurations | A pen test finds logic flaws and auth bypasses that scanners miss |
| CC7.2 to CC7.4 | Detect, evaluate, and respond to security events | The fix and retest loop mirrors incident response |
| A1.2 (Availability) | System resilience | Testing finds weaknesses that could take systems down |
| C1.1 (Confidentiality) | Protecting confidential data | A pen test shows how an attacker could reach customer data |
How often do you need a pen test for SOC 2?
Plan on at least once a year. Netragard's guidance adds targeted testing after significant changes. A cloud migration or a major release counts. A test from eighteen months ago says little about your controls today.
CC7.1 also asks for ongoing vulnerability detection. That is why more teams now test continuously. Every deploy then adds to the evidence trail.
Does a SOC 2 Type I or Type II audit change the pen test?
Yes, mostly in timing. A Type I report checks control design on a single date. A Type II report checks how controls operated over an observation period of 3 to 12 months. A recent pen test supports either one.
For Type II the test should fall inside the observation period or shortly before it . Many teams test early in the window. That leaves time to fix findings and retest before fieldwork. Confirm the timing with your auditor before you book the test.
Can you do SOC 2 and a penetration test in the same engagement?
You can run both in the same audit cycle. That is the normal pattern. Test early in the observation period and fix what you find. Then hand the report and retest evidence to the auditor.
Having your SOC 2 audit firm also run the pen test is a different question. Independence rules treat some technical services for an audit client as a threat to independence. Ask your auditor in writing before you combine the two. Most companies keep the tester and the auditor separate.
What should a SOC 2 penetration test scope include?
Scope should mirror your SOC 2 system boundary. TechPause puts it plainly . If the boundary includes your app and its API, the test covers both. The same goes for supporting infrastructure. For most SaaS companies that means the web app and every API endpoint. It also means cloud configuration and authentication across every layer.
Make sure your policies match the work. Asteros describes a common gap where policy promises an application test but the vendor delivers a network scan. Auditors catch that mismatch. Bastion recommends gray box testing for most SaaS teams because testers start with real user credentials.
What does a SOC 2 pentest report need to include?
Auditors want proof that the work was real and that you acted on it. A list of findings with no methodology looks like scanner output.
| Report section | Why auditors want it |
|---|---|
| Executive summary | Shows overall risk in business terms |
| Scope and system boundary | Proves coverage matches the SOC 2 scope |
| Methodology | Shows how the testing was done |
| Findings with severity scores | Ranks each issue by risk |
| Evidence of exploitation | Proves each finding is real |
| Remediation guidance | Shows how to fix each issue |
| Retest results or attestation letter | Proves the fixes work |
The retest is the part teams forget. TechPause notes that findings without remediation records can look worse than no findings at all. They show you found the risk and left it open.
Can vulnerability scanning replace a pen test for SOC 2?
No. Scanners find known issues across a wide surface. They cannot judge business logic or chain weaknesses together. A pen test proves what an attacker can actually exploit .
Auditors expect both. CYBRI's guide describes scans as breadth and pen tests as depth. Most auditors expect scans at least quarterly.
What pen test mistakes cause SOC 2 audit findings?
Most audit friction comes from gaps between what you claim and what you can show. Asteros lists the patterns auditors flag most often.
- Policy and evidence don't match. The policy promises an app test and the report shows a network scan.
- Remediation windows are too long. Giving yourself 90 days to fix a critical bug raises questions.
- No retest evidence. Open findings with no follow-up can lead to noted exceptions.
- The test falls outside the audit window. An old test has little value in a Type II audit.
- The test was too shallow. Blaze InfoSec warns that one-to-three-day "express" tests often rely on scanners.
How much does a SOC 2 penetration test cost?
A manual SOC 2 pen test usually costs $5,000 to $25,000. Scope and complexity drive the number. For a full breakdown by test type and pricing model, see our penetration testing cost guide.
| Engagement type | Typical cost | Source |
|---|---|---|
| SOC 2 pen test from a credible firm | $5,000 to $25,000 | Blaze InfoSec |
| Hourly rate | $200 to $300 per hour | Blaze InfoSec |
| Typical SaaS app, gray box | $10,000 to $30,000 | Bastion |
| Traditional pen test, general market | $20,000 to $50,000 | Cobalt |
| Continuous AI pentesting | From $499 per month | MindFort pricing |
Be wary of very cheap quotes. Blaze says a SOC 2 test under about 40 hours for a small or mid-sized scope may be too shallow. A cheap report can pass an audit and still miss real bugs.
How do you choose a SOC 2 pentest vendor?
Pick a vendor whose deliverables an auditor will accept without follow-up questions. Check each candidate against this list.
- Mapped evidence. Findings tie back to CC4.1 and CC7.1.
- Documented methodology. The report explains how testing was done.
- Full scope. The test covers the app, APIs, and cloud inside your boundary.
- Retests included. Fixes get verified without a new contract.
- Attestation letter. You get a letter you can hand to your auditor and customers.
- Fits your release pace. Annual tests suit slow release cycles. Continuous testing suits teams that ship weekly.
For a comparison of AI-driven options, see our guide to the best AI pentesting tools.
How does MindFort help you stay SOC 2 audit-ready?
MindFort runs autonomous security agents that pen test your web apps and APIs on every deploy. Each finding comes with a working exploit. The agents open a pull request with the fix and retest it once it merges. That builds the ongoing evidence CC7.1 asks for.
Reports map findings to CC4.1 and CC7.1. MindFort also provides an attestation letter you can give to your auditor or a customer's security team. You walk into the audit with months of testing evidence already in hand.
Start continuous security testing with MindFort →
FAQ
Does SOC 2 require a penetration test?
Not by name. The AICPA's Trust Services Criteria list penetration testing as one way to evaluate controls under CC4.1. In practice auditors expect it. Enterprise customers usually ask for the report too.
How often should you pen test for SOC 2?
At least once a year and after significant system changes. For a Type II audit the test should fall inside the observation period or shortly before it. Continuous testing gives you evidence across the whole window.
What should a SOC 2 pentest report include?
An executive summary, the scope, and the methodology. It should list each finding with a severity score and evidence of exploitation. It also needs remediation guidance and retest results that prove each fix worked.
Can your SOC 2 auditor also do your pen test?
Sometimes, but it can raise independence concerns. Professional ethics rules treat some technical services for an audit client as a threat to independence. Ask your auditor in writing before you combine them. Most companies use a separate testing provider.
How much does a SOC 2 penetration test cost?
A manual SOC 2 pen test from a credible firm usually costs $5,000 to $25,000. A thorough gray box test of a typical SaaS app can reach $30,000. Continuous AI pentesting is sold as a subscription. MindFort plans start at $499 a month.
Can vulnerability scanning replace penetration testing for SOC 2?
No. Scanners flag known issues across a wide surface. A pen test proves what an attacker can actually exploit. Auditors expect scans at least quarterly and a pen test for depth.
About the author

Brandon Veiseh
Co-Founder & CEO · MindFort
Founded his first startup building NLP models for network packet inspection. Led product at ProjectDiscovery, built their enterprise platform from scratch. At NetSPI, led development of AI tools for offensive security.