Home / Guides / A penetration test is not required for a SOC 2, and NIST SP 800-115 gives 4 phases to scope against
Guide, read 12 Nov 2026
A penetration test is not required for a SOC 2, and NIST SP 800-115 gives 4 phases to scope against
Open the glossarySee the ranked index
SOC 2 requires risk management, and a penetration test is one way to evidence it
BARR's page of May 4, 2022 says neither a vulnerability scan nor a penetration test is technically required before a SOC examination. What is required is that the company assess and manage security risks from internal and external sources in some way. Whether it uses scans, penetration tests or both is up to the company. BARR's own recommendation is regular scans run by the company plus an annual external penetration test by a third party.
Auditors still ask. Insight Assurance says most auditors and risk managers recommend third-party penetration testing at least annually, and more often for higher-risk environments or those undergoing significant change. BARR says penetration tests often satisfy requirements for SOC 2 Type 2. The criteria groups involved are Monitoring Activities (CC4) and System Operations (CC7). This guide names them by title only, because the AICPA criteria PDF returned a script-only page on 12 Nov 2026 and no criterion wording could be read.
Write the control to match what the company does. A workable statement says the company obtains a penetration test from a qualified third party at least annually and after significant change, tracks every finding to closure, and retests critical and high findings. If the document promises quarterly tests and the company runs one a year, the auditor tests the promise, not the intent. Promise only what the calendar supports.
The auditor tests the control, not the penetration test itself
BARR's article of May 5, 2026 says a SOC 2 opinion rests on three components: the system description, the design of controls, and their operating effectiveness. For a penetration test, the auditor's focus is on the second and third: does the control exist as written, and did it run. BARR adds that auditors are generally expected to stay agnostic about which provider performed the test.
Auditors can still challenge the design. BARR says that if a report makes explicit that the work was an automated scan labeled as a penetration test, that is a design deficiency to document. It also says an auditor risks overstepping by rejecting a report on inference alone, so concrete evidence is needed. Expect the auditor to read the scope and methodology pages first, then the findings and the retest.
That sets the evidence list: the signed statement of work, the rules of engagement, the test dates, the final report, proof of remediation and the retest report. BARR warns about penetration test 'certificates' and calls them misleading, because a test is not a pass or fail exercise and a certificate usually lacks scope and context. A one-line certificate from a tester is weaker evidence than the report behind it.
NIST SP 800-115 defines four phases that give the engagement a structure
NIST SP 800-115, published in September 2008, divides a penetration test into planning, discovery, attack and reporting. A footnote says this is an example of how the process can be divided and that many acceptable groupings exist. In planning, rules are identified, management approval is finalized and documented, and testing goals are set. NIST says no actual testing occurs in the planning phase.
Discovery has two parts: information gathering and scanning, then vulnerability analysis. The attack phase verifies previously identified potential vulnerabilities by attempting to exploit them, and it can loop back to discovery when new hosts or access appear. NIST contrasts this with vulnerability scanners, which check only for the possible existence of a vulnerability. Reporting runs alongside the other phases and ends in a report with vulnerabilities, a risk rating and guidance for mitigation.
Appendix B of the publication is a rules of engagement template. Its sections include purpose, scope, assumptions and limitations, risks, personnel, a test schedule and reporting requirements. Ask the tester for a rules of engagement document or an equivalent section in the statement of work. It is the single page that proves what the company authorized and when, and an auditor can use it to match dates to the examination period.
| NIST phase | What NIST says happens | Evidence to keep for the auditor |
|---|---|---|
| Planning | Rules identified, management approval documented, goals set | Rules of engagement, approval, target list |
| Discovery | Information gathering, scanning and vulnerability analysis | Target scope, scan dates |
| Attack | Verify vulnerabilities by attempting exploitation; may loop back to discovery | Tester narrative of findings |
| Reporting | Vulnerabilities, risk rating and mitigation guidance | Final report and retest report |
Scope should follow the SOC 2 system boundary and state the credential level
Start from the system description. Every internet-facing host, application and API that belongs to the in-scope service goes on the target list: the production web application, the customer API, authentication endpoints and the cloud accounts behind them. Schellman says an external test works from a list of public IP addresses or domain names and that the tester focuses only on approved in-scope hosts. It also advises against restricting scope, since a limited test can miss vulnerabilities and force further assessments later.
Credentials change what the test can find. NIST describes external testing as working from target IP addresses and public information, and internal testing as working from the access a trusted user would hold, up to administrator privileges. For scanners, it separates scanning with host credentials from scanning without. Insight Assurance maps the idea onto black box, gray box and white box testing. For a web application, authenticated testing with a test account for each role covers more of the product than testing the login page alone.
Schellman's process asks that test accounts be onboarded before testing starts when credentials are required, and says missing or incomplete scope can be a reason projects get delayed. NIST adds that when both internal and external tests are done, the external test usually goes first, so the same testers do not carry insider knowledge into the outside view. Record exclusions, such as third-party tools the company cannot authorize testing against, in the rules of engagement.
| Test type | Tester starts with | Typical coverage for a SOC 2 service |
|---|---|---|
| Unauthenticated external (black box) | Public IP addresses or domain names only | Exposed hosts, login pages, public endpoints |
| Authenticated, per role (gray box) | Test accounts or limited access | Application behavior behind the login, by role |
| Internal (white box) | Network or administrator access | Systems behind the perimeter and privilege escalation |
Retesting and the report decide how much evidence the auditor gets
Schellman's published process gives a retest window of 30 to 45 days after the report is posted, with a retest report issued after the company remediates. It also offers a one-page pen test summary letter that shows scope, timing and, at a high level, the number of findings. A letter is easier to share with customers, but an auditor may ask for the full report, so ask the auditor which one it accepts before the test begins.
NIST says mitigation can be verified by retesting, and that the test team can verify implementation only if a mirror copy of the original test is performed. A retest should therefore repeat the original steps on the same targets, not spot check the one page that was fixed. BARR says retesting is often even more important than the initial test from a compliance perspective, because it validates that controls are functioning as intended.
BARR lists the elements of a credible report: detailed and actionable recommendations, a clear executive summary and scope, the number of findings by severity, and the outcomes of retesting. It also suggests asking for a draft and checking alignment to a standard such as OWASP's Application Security Verification Standard. Together these give the auditor a scope page, a method, severity counts and proof that the critical findings were closed.
The tester should be qualified and free of conflicts
NIST says organizations should take care in selecting assessors, because vetted, skilled and experienced assessors lower the risk of conducting security tests. External entities should be vetted for skills, experience and integrity, and should accept some of the risk, since they may be responsible for damages. NIST also warns about conflicts of interest, such as one individual conducting a formal assessment and then being responsible for addressing its findings.
NIST says third parties, including auditors, can offer an outside view that internal assessors cannot provide. Some audit firms also sell penetration testing. A-LIGN's article of May 14, 2025 says its penetration testing team is its own specialty and that information is not shared between that team and its SOC team. Whether to use the audit firm's test team is the company's decision. Auditor independence rules were not retrievable in primary form on 12 Nov 2026, so ask the firm for its written position.
Qualifications reach the auditor only through the report. Name the tester or firm, state the method used (NIST SP 800-115, OWASP's standard or the firm's own), give the dates, and avoid testers who built or operate the system under test. If a reviewer asks why the test counts, the report should answer with scope, method, dates and tester without a phone call.
More guides
- A SOC 2 readiness assessment is a 4-phase gap review that ends without an auditor opinion
- A SOC 3 is the public summary of a SOC 2 examination, and AWS, Google and Microsoft publish one
- SOC 2 auditors test a sample of each control population, and one firm publishes a 3 to 30 item range
Sources
- BARR: Vulnerability Scans vs. Penetration Tests, read 12 Nov 2026
- BARR: Evaluating Pentest Quality, the Role of Auditors, read 12 Nov 2026
- BARR: Security Trust Services Criteria, read 12 Nov 2026
- Insight Assurance: What's a Penetration Test, and Do I Need One, read 12 Nov 2026
- NIST CSRC: SP 800-115 publication record, read 12 Nov 2026
- NIST SP 800-115: Technical Guide to Information Security Testing and Assessment, read 12 Nov 2026
- Schellman: Penetration Test Project Process, read 12 Nov 2026
- Schellman: What Is External Penetration Testing, read 12 Nov 2026
- A-LIGN: Myths About Pen Testing With Your Audit Firm, read 12 Nov 2026
Last reviewed 12 Nov 2026.