The AICPA never wrote the words penetration test required into SOC 2. Yet a service organization that walks into a Type II audit without one should expect follow-up questions, extra evidence requests, or a delayed report. Most companies trip on the difference between what the standard says and what auditors expect to see.
This article breaks down the real SOC 2 penetration testing requirements: where they sit in the Trust Services Criteria, what auditors look for during Type I and Type II engagements, how often you should test, and what a good pen test report needs to contain to satisfy your auditor without inflating your budget.
Quick Summary
SOC 2 does not require a penetration test by name: the AICPA’s Trust Services Criteria list penetration testing only as one example of a separate evaluation under CC4.1. In practice, auditors expect a third-party test at least once a year that covers the SOC 2 system boundary, falls inside the Type II observation period (or within 12 months of a Type I report date), and has its critical and high findings fixed and retested before the period ends.
Understanding SOC 2 and Its Security Expectations
What Is SOC 2?
SOC 2 is an attestation framework developed by the American Institute of Certified Public Accountants (AICPA) for service organizations that handle customer data. Unlike a certification, SOC 2 is an opinion: a licensed CPA firm reviews your security controls and issues a report stating whether those controls are designed (Type I) or operating (Type II) effectively. SOC 2 reports are read by enterprise procurement teams, security reviewers, and risk officers, and enterprise buyers commonly ask for one during vendor security review.
What Controls Does SOC 2 Require?
Rather than dictating specific technologies, SOC 2 requires that you design and operate controls that demonstrably meet each criterion under the Trust Services Criteria (TSC). That gives you flexibility, and it also gives auditors latitude to ask hard questions.
Does SOC 2 Require Penetration Testing?
The Official SOC 2 Position on Penetration Testing
Penetration testing appears once in the AICPA’s 2017 Trust Services Criteria (with revised points of focus, 2022): in a point of focus under CC4.1, the monitoring criterion that asks the entity to perform ongoing and separate evaluations to confirm that controls are present and functioning. That point of focus says management uses a variety of ongoing and separate evaluations, including penetration testing. CC7.1, the vulnerability management criterion, has its own point of focus on vulnerability scans run periodically and after significant changes.
Points of focus illustrate how a criterion can be met; they are not requirements. The criteria contain no clause that mandates an annual external pentest, no specification of scope, and no required methodology.
Short Answer: There Are No Mandatory SOC 2 Pen Test Requirements
You can technically obtain a SOC 2 report without a penetration test, provided you can show your auditor that you use alternative evaluations to satisfy CC4.1 (ongoing monitoring) and CC7.1 (vulnerability identification). In practice, almost nobody does this successfully.
Long Answer: You Still Need SOC 2 Penetration Testing
Auditors view penetration testing as the strongest available evidence that your controls work against a determined adversary, not just on paper. CC4.1 asks the entity to perform ongoing monitoring to ascertain whether internal controls are present and functioning; a pen test is the most direct way to evaluate that. CC6.1 asks whether logical access controls can be bypassed; a pen test answers that question directly. CC7.1 ties this together by requiring you to detect newly introduced vulnerabilities.
If you skip pen testing, you carry the burden of proving your alternative evidence is at least as good. That is a steeper hill than most organizations realize.
What Auditors Expect During Type I and Type II Engagements
Auditors expect a SOC 2 Type I report to be backed by a penetration test completed within roughly the 12 months before the report date, and a Type II report to be backed by a test run inside the observation period. According to the AICPA’s SOC suite of services guidance, a Type I report covers the design of controls at a point in time, while a Type II report covers how those controls operated over a period, which in practice runs 3 to 12 months. For Type II, auditors also expect documented remediation of any critical or high findings before the period closes.
| Requirement | SOC 2 Type I | SOC 2 Type II |
|---|---|---|
| What the report covers | Control design at one date | Control operation over a 3 to 12 month period |
| When the pentest should happen | Within about 12 months before the report date | Inside the observation period |
| Remediation evidence | Remediation plan for open critical and high findings | Fixes and retest results before the period ends |
| How often | Before the first report | At least annually, plus after material changes |
Once your security policy or SOC 2 control set commits to an annual penetration test, that commitment becomes a control the auditor tests. A missing or out-of-window test then appears as an exception in the report’s test results, which every customer reviewing the report will read. Confirm the testing window with your auditor before you book the engagement.
What Are the Actual SOC 2 Penetration Testing Requirements?
Alignment with Trust Services Criteria
A pen test that supports a SOC 2 audit should map its findings to specific criteria. Ask the testing firm for a Trust Services Criteria mapping appendix that ties identified vulnerabilities back to CC4.1, CC6.1, CC7.1, and where relevant CC7.2 through CC7.4. Without that mapping, your auditor has to do the interpretive work themselves, which typically means a follow-up request and a slower report.
Scope Definition Requirements
Scope should match your SOC 2 system boundary, not your entire infrastructure. If your audit covers a single SaaS product, its API, and its AWS account, that is what should be tested. Auditors look for evidence that the pen test scope was derived from the system description in your SOC 2 report. A mismatch between the two leads to follow-up requests and slows fieldwork.
Insider Note: In the SOC 2 audits Axipro supports, a pen test whose scope does not match the system description is one of the issues auditors flag most often. Before the test is booked, put the system description next to the statement of work and check that every product, API and cloud account named in one appears in the other.
Testing Frequency and Timing Requirements
SOC 2 does not specify a frequency. Annual testing has become the de facto standard, with additional testing after material changes to architecture, authentication, or hosting. For organizations on continuous deployment, some auditors now accept a combination of annual deep-dive testing and continuous automated assessment as sufficient coverage, but this should be confirmed with your auditor before you rely on it. Whatever cadence you choose, write it into your security policy, because the auditor tests you against your own stated frequency.
Remediation Evidence Requirements
Findings without remediation are findings against you. Auditors expect documented remediation plans for every critical and high-severity issue, with closed tickets, retest results, or compensating controls recorded before the audit period ends. A finding sitting open in a backlog at audit time is treated almost identically to a finding that was never addressed.
What Should a SOC 2 Penetration Test Report Include?
A SOC 2 penetration test report should give the auditor enough detail to confirm what was tested, when, by whom, and what happened to each finding. Enterprise customers reviewing your security package look for the same elements. An audit-ready report contains:
- Executive summary: testing dates, overall risk rating, and the count of findings by severity.
- Scope: every application, API, network range and cloud account tested, matched to the SOC 2 system description, with any exclusions explained.
- Methodology: the standard followed, such as NIST SP 800-115 or the OWASP Web Security Testing Guide, and whether testing was black box, grey box or white box.
- Tester details: the testing firm, tester qualifications, and a statement that the testers are independent of the team that runs the system.
- Findings: each with a severity rating such as a CVSS score, reproduction steps, evidence, business impact and remediation guidance.
- Trust Services Criteria mapping: which findings relate to CC4.1, CC6.1, CC7.1 and other criteria.
- Retest results: confirmation that critical and high findings were fixed, appended or issued as a follow-on letter.
A letter of attestation is a one or two page summary that a testing firm issues so you can share proof of testing with customers without handing over the full findings. It works well for customer security reviews, but your SOC 2 auditor will still ask for the full technical report. Our guide to what a VAPT report includes walks through each section in more detail.
Penetration Testing vs. Vulnerability Scans for SOC 2
Both belong in your control set, but they answer fundamentally different questions. Vulnerability scanning is automated and broad: it identifies known CVEs and misconfigurations across your environment quickly and consistently. Penetration testing is manual and adversarial: it simulates what a real attacker would do with the access and information they can obtain. The CC7.1 points of focus name vulnerability scans, the CC4.1 points of focus name penetration testing, and your auditor will want to see evidence of each.
Why Automated Scans Are Not Sufficient for SOC 2 Compliance
Scanners cannot reason about business logic. They will not find a privilege escalation chain through a multi-tenant API, an authorization flaw that lets one customer view another customer’s data, or an authentication bypass via a forgotten admin endpoint. SOC 2 cares about whether your controls actually protect customer data, and those classes of failure only surface under manual penetration testing. Submitting scanner output as your primary evidence under CC4.1 is one of the fastest ways to generate a finding.
When to Use Vulnerability Scanning vs. Penetration Testing
Use scanning continuously as ongoing evidence of monitoring. Use penetration testing periodically as deep validation. They are complements, not substitutes, and your SOC 2 control narrative should describe them as such.
Required Types of Penetration Testing for SOC 2
A SOC 2 penetration test covers five types of testing, chosen by what sits inside your system boundary. Most SaaS companies need web application, API and cloud testing at a minimum, and add network testing when they run their own perimeter or offices that reach production.
| Test type | What it covers | When SOC 2 scope needs it |
|---|---|---|
| External network | Public IPs, open ports, exposed services and edge devices | Any internet-facing infrastructure in scope |
| Internal network | Lateral movement, segmentation and privilege escalation after a foothold | Offices, VPNs or internal networks that can reach production |
| Web application | Injection, authentication, session and authorization flaws, usually following the OWASP Web Security Testing Guide | Every customer-facing application in the system description |
| API | REST and GraphQL endpoints, tenant isolation and business logic | Any product that exposes data or functions through an API |
| Cloud infrastructure | IAM policies, storage buckets and network rules in AWS, Azure or GCP | Every cloud account that hosts in-scope systems |
Cloud misconfigurations such as overly permissive IAM roles and exposed storage are a frequent source of material findings in SaaS environments. For scoping and pricing a web application test on its own, see our guide to web application penetration testing scope and cost.
What Makes a Good SOC 2 Penetration Test?
A good test pursues specific goals tied to your actual threat model: Can a customer access another customer’s data? Can an unauthenticated user reach administrative endpoints? Can an attacker pivot from a compromised application tier to the underlying cloud account? Generic test-everything engagements rarely produce findings that map cleanly to TSC controls, and they are harder for auditors to evaluate. Specificity is an asset, not a limitation.
The test must also match your SOC 2 audit scope precisely. If your system description names three products and the pentest covered only one, your auditor will issue a finding. Results must be actionable, CVSS scores alone are not enough. Each finding should include reproduction steps, business impact, and prioritized remediation guidance. Anything less wastes engineering time and adds friction at audit fieldwork.
Pro Tip: Avoiding Failed Audits
Auditors push back on a pentest report that is only automated scanner output rebadged as a penetration test. Ask the provider for a sample report before you sign: if it reads like scanner output with a new cover page, your auditor will read it the same way.
When Should You Perform Penetration Tests for SOC 2 Compliance?
Time a SOC 2 penetration test around four triggers: the audit window, a security trigger event, a material architecture change, and the annual cadence. The first is the audit deadline itself: a pentest performed too early in the audit window leaves stale findings; too late, and there is no time to remediate before the period closes. The second is a trigger event, such as a security incident or a newly disclosed CVE affecting your stack. The third is a material architecture change, a major deployment, a new authentication system, or a cloud migration that changes your attack surface significantly. The fourth is the basic annual cadence that maintains posture between audits regardless of whether anything has changed.
Worth Knowing: Scheduling a Pentest
On a 12-month observation period, schedule your pentest 90 to 120 days before the period closes. That gives engineering time to remediate critical findings, your testing firm time to retest, and your auditor time to validate evidence. On a 3-month period, test in the first two or three weeks so the fixes and the retest still land inside the window.
How to Prepare for and Perform Effective SOC 2 Penetration Testing
Preparation starts with scope definition aligned to your SOC 2 system boundary. Document every in-scope application, API, and cloud account. Confirm authentication paths and provision tester accounts before the engagement starts. Brief your testing firm on your threat model and share prior findings so they are not duplicating work.
Choose a testing team with explicit SOC 2 experience. Certifications worth verifying include OSCP, OSWE, CREST, and CISSP. Ask specifically whether the firm produces TSC-mapped reports and whether retests are included in scope, both are non-negotiable for audit-quality evidence. Axipro, a compliance readiness and cybersecurity consultancy and Drata Elite Partner that helps SaaS and technology companies get audit-ready for SOC 2, ISO 27001, ISO 42001 and other frameworks, is CREST certified and offers penetration testing alongside SOC 2 readiness. For how the pentest fits the wider audit workflow on a GRC platform, see the Drata SOC 2 guide.
Can Your SOC 2 Auditor Also Run the Penetration Test?
Your SOC 2 auditor can run the penetration test only if the CPA firm concludes that doing so does not impair its independence, so most companies hire a separate testing firm. The AICPA Code of Professional Conduct requires the firm issuing the SOC 2 opinion to stay independent of the controls it examines, and testing a control it will later attest to creates a self-review threat. Auditors routinely accept reports from third-party testing firms, so separating the two adds no audit risk. Our comparison of SOC 2 consultant and auditor roles explains where the AICPA draws the independence line.
Remediate every critical and high finding before the audit period closes. Document medium and low findings with risk acceptance memos or remediation timelines. Then present everything to your auditor as a structured package: pentest report, remediation evidence, retest results, and a control-mapping summary. Auditors appreciate a clean folder: it signals operational maturity.
SOC 2 Penetration Testing Checklist for 2026
Use the SOC 2 checklist as your master reference, and layer in the following for penetration testing specifically.
- Confirm the test scope matches your SOC 2 system description.
- Write the testing frequency into your security policy.
- Schedule the test inside the observation period, leaving time to remediate and retest.
- Require Trust Services Criteria mapping in the final report.
- Make sure testers manually test authorization flows and business logic, not just infrastructure.
- Remediate all critical and high findings before the period ends.
- Keep retest evidence alongside the original findings.
- Store the report, remediation tickets, retest results and control mapping in one audit folder before fieldwork begins.
What Are the Benefits of SOC 2 Penetration Testing?
Beyond audit evidence, a properly scoped pentest delivers compounding value. It reduces breach risk by surfacing exploitable vulnerabilities before an attacker does. It validates your engineering investment in security controls, giving your team actionable signal rather than theoretical risk scores. It supplies ready-made evidence for customer security reviews and third-party questionnaires that would otherwise require custom responses. And it provides a legally defensible position if a breach later occurs, demonstrating reasonable due diligence is increasingly relevant in regulatory and litigation contexts.
How Much Does a SOC 2 Penetration Test Cost?
For a standard SaaS scope covering one product, its API, and one cloud account, expect to budget $1,500 to $20,000 in 2026. Scope size is the largest cost driver: additional applications, multiple cloud environments, complex authentication flows, and Active Directory all push costs higher. Our SOC 2 penetration testing cost breakdown covers price ranges by scope and company size.
The hidden cost is retesting. Many providers quote a low headline price that excludes retest fees. A finding without retest evidence does not satisfy your auditor, so retests are not optional; they are part of the deliverable. Ask explicitly whether retesting is included before signing an engagement letter.
Closing Note
A penetration test is effectively mandatory for SOC 2, even though the Trust Services Criteria never require one by name. Auditor expectations, enterprise procurement and customer security reviews all assume one exists. Treat the pentest as the most efficient piece of evidence you can produce for CC4.1, CC6.1, and CC7.1, scope it tightly to your system boundary, remediate findings before the audit window closes, and make sure the report can be read by an auditor without translation. Done well, one engagement produces evidence for three criteria and a report your customers will also ask to see.
Frequently Asked Questions About SOC 2 Penetration Testing Requirements
Is penetration testing required for SOC 2 Type I?
Not strictly, but most auditors expect one as evidence of control design. A Type I report without a recent pentest is harder to defend and more likely to generate follow-up requests during fieldwork.
Is penetration testing required for SOC 2 Type II?
Same answer, more emphatically. Type II tests operating effectiveness over time, and a pentest is the strongest available evidence that controls operate as designed across the audit period.
How often should penetration testing be performed for SOC 2?
Annually at minimum, plus additional tests after material changes to architecture, authentication systems, or cloud infrastructure. Some high-velocity engineering organizations supplement annual testing with continuous automated assessment, though this should be discussed with your auditor before relying on it as a substitute.
What does a SOC 2 penetration test report need to include?
An executive summary, defined scope and methodology, severity-rated findings with reproduction steps, CVSS scores, Trust Services Criteria control mapping, and prioritized remediation guidance. Retest evidence should be appended or submitted as a follow-on document before the audit period closes.
Can I use a vulnerability scan instead of a penetration test for SOC 2?
No. Vulnerability scans support CC7.1 as evidence of ongoing monitoring but do not substitute for the manual evaluation evidence auditors expect under CC4.1 and CC6.1. The two serve different evidentiary purposes and both should appear in your control set.
Who can perform a SOC 2 penetration test?
Any qualified third-party firm with a documented testing methodology and credentialed testers. SOC 2 does not specify required accreditations, but auditors look for evidence of tester independence, a recognized methodology, often referencing NIST SP 800-115, and verifiable tester qualifications such as OSCP or CREST membership.
Does the penetration test have to happen during the SOC 2 Type II observation period?
Yes, in most audits. A SOC 2 Type II report covers how controls operated over the observation period, so auditors expect the penetration test, its remediation and its retest to fall inside that window. A test completed before the period starts usually counts only as background, not as evidence of operation.
Can my SOC 2 auditor also perform the penetration test?
Only if the CPA firm concludes it can do so without impairing its independence under the AICPA Code of Professional Conduct. Testing controls the firm will later attest to creates a self-review threat, so most companies use a separate penetration testing firm and share its report with the auditor.
Will SOC 2 auditors accept an automated or AI-driven penetration test?
SOC 2 auditors judge the evidence, not the tooling. An automated or AI-assisted test is more likely to be accepted when a qualified person validated the findings and the report shows manual testing of authorization and business logic. Confirm with your auditor before relying on an automated-only report as CC4.1 evidence.
Is a pentest letter of attestation enough for SOC 2?
No. A pentest letter of attestation is a short summary for customers that confirms a test took place, and SOC 2 auditors ask for the full technical report with findings, remediation and retest results. Keep the letter for customer security reviews and give the full report to your auditor.