Guide

Does SOC 2 require a penetration test?

SOC 2 doesn't strictly require a penetration test, yet almost every SOC 2 company has one. This is what the Trust Services Criteria actually say, why auditors expect a pentest anyway, and what evidence holds up in a Type II audit.

Updated 11 November 2026 · By the Closeout team

Does SOC 2 require a penetration test?

Not explicitly. SOC 2 reports against the AICPA's 2017 Trust Services Criteria (with points of focus revised in 2022), and no criterion says “perform a penetration test”. But the criteria ask the company to evaluate its controls and detect vulnerabilities, penetration testing is named as an example of how, and most auditors and the customers reading the report expect one, usually every year.

What the criteria say

  • CC4.1: the entity selects, develops and performs ongoing and/or separate evaluations to check that controls are present and working. Its points of focus give penetration testing as an example of a separate evaluation.
  • CC7.1: the entity uses detection and monitoring procedures to identify configuration changes that introduce new vulnerabilities and susceptibility to newly discovered vulnerabilities.
  • CC4.2: deficiencies are communicated to those responsible for corrective action, which is where pentest findings and their remediation come in.

Points of focus are not requirements: the AICPA says an auditor doesn't have to check each one. That's why “SOC 2 requires a pentest” is wrong in the letter and right in practice.

Type I, Type II and timing

A Type I report looks at control design on one date; a Type II looks at whether controls operated over a period, usually 6 to 12 months. For a Type II, the pentest should fall inside the review period, and the auditor will look at what happened to the findings afterwards: who owned them, when they were fixed and whether the fix was verified.

Evidence the auditor will ask for

  • The report, with scope, dates, methodology, who tested and every finding with its severity.
  • The remediation record: owner, due date and status of each finding, with dates.
  • The retest, which proves each fix works, not just that someone marked it done. See our guide to pentest retesting.
  • Accepted risks, in writing, by someone with the authority, with a reason and a review date.
  • An attestation letter if the client must show the result to third parties without sharing the full report. You can make one with the attestation letter generator.
Closeout keeps that record for you: it delivers the report in a branded portal, tracks each finding against its deadline, verifies fixes with a retest and issues the attestation letter that cites the report by its SHA-256 hash.

The 2027 criteria draft

In October 2026 the AICPA published an exposure draft of revised Trust Services Criteria. It is a proposal, not a final standard, so reports today still use the 2017 criteria. We'll update this page if the final text changes anything about testing.

Sources

Official texts, checked in November 2026. This is a practical guide, not legal or audit advice.

Frequently asked questions

Is a penetration test mandatory for SOC 2?

No criterion explicitly requires one. Penetration testing is named in the CC4.1 points of focus as a type of separate evaluation, and auditors and customers commonly expect an annual test.

How often should a SOC 2 company run a pentest?

Usually once a year and after major changes. For a Type II report, the test should fall within the review period.

Does the auditor need the full pentest report?

Usually the auditor reviews the report or a summary, plus evidence that findings were tracked and fixed. Customers often get an attestation letter instead of the full report.

Are vulnerability scans enough for SOC 2?

Scans help meet CC7.1, but most auditors expect a penetration test as well, as an independent evaluation under CC4.1.