BY BUSINESS OBJECTIVE
ASSESS & VALIDATE — FIND WEAKNESSES
Digisecuritas logo
Compliance

Does SOC 2 Require Penetration Testing? What Auditors Expect to See

H

Harsh

Cybersecurity Experts

·4 min read

Does SOC 2 require penetration testing? The short answer

No. The AICPA Trust Services Criteria do not contain a line that says a service organization must run a penetration test. SOC 2 is written as criteria, and each company chooses the controls that meet them.

In practice, most companies going through SOC 2 still get one. Auditors look for evidence that you find and fix technical weaknesses, and enterprise customers ask for a pen test summary in the same security review where they ask for the SOC 2 report. A company that skips the test usually ends up explaining why to both.

This guide covers what the criteria say, what auditors accept as evidence and how to time a test so it counts.

What the Trust Services Criteria say

Two parts of the Security category (the Common Criteria) are where penetration testing comes up.

Criterion

What it asks for

How a pen test fits

 

CC4.1

The organization selects and performs ongoing or separate evaluations to confirm controls are present and working

The AICPA points of focus list penetration testing as one type of separate evaluation, along with internal audit and independent certification

CC7.1

The organization uses detection and monitoring procedures to identify new vulnerabilities and configuration changes

Vulnerability scanning is the usual control here, and a pen test adds evidence that scanning results are validated

Points of focus are guidance. An auditor does not fail you for missing one. They do ask how you meet the criterion without it, and "we run a scanner" is a weaker answer than a scan program plus an annual manual test.

What auditors expect to see

If your control list includes penetration testing, the auditor tests that control like any other. They will ask for:

  • The report itself. Dated, with scope, methodology, findings and severity ratings.

  • Evidence of independence. A third-party firm, or an internal team that is separate from the people who built the system.

  • Scope that matches the SOC 2 system boundary. A test of the marketing website does not cover the production application named in your system description.

  • Tracked remediation. Tickets for each finding, with owners and dates that meet the timelines in your vulnerability management policy.

  • A re-test or closure evidence. Proof that critical and high findings were fixed and verified.

The fourth item is where exceptions come from. If your policy says critical findings are fixed in 15 days and the ticket shows 60, the auditor records an exception, even though you ran the test.

Does SOC 2 Type 2 require penetration testing?

The criteria are the same for Type 1 and Type 2, so the answer does not change: it is not named as mandatory. What changes is timing.

A Type 1 report describes controls at a point in time. A recent pen test report shows the control is designed and in place.

A Type 2 report covers a period, commonly 6 to 12 months. If your control says "a penetration test is performed annually," the auditor wants the test to have happened inside the review period, with remediation tracked inside it too. A test completed two months before the period started leaves a gap. Schedule the test early in the window so fixes and the re-test land before it closes.

SOC 2 penetration testing requirements in practice

There is no official list of SOC 2 penetration testing requirements. These are the conditions that auditors and buyers apply in practice:

  1. Cover the in-scope system. Include the production web application, APIs, cloud environment and external network that sit inside your SOC 2 boundary.

  2. Use manual testing. An automated scan relabeled as a pen test will not satisfy a buyer's security team, and many auditors now ask about methodology.

  3. Test at least once a year and after significant changes to architecture or authentication.

  4. Rate findings with a recognized scale such as CVSS, so remediation timelines can be tied to severity.

  5. Keep the full chain of evidence: statement of work, report, tickets, re-test report.

  6. Write the control the way you operate it. If you test annually, do not write "quarterly" in the control description.

Vulnerability scanning and penetration testing are separate controls

Companies sometimes hope one will stand in for the other. A scan is automated, runs often and lists known weaknesses. A penetration test is a person trying to exploit weaknesses, including logic and access control flaws that no scanner detects.

Most SOC 2 programs include both: scanning monthly or continuously under CC7.1, and a pen test annually under CC4.1. Removing the pen test is allowed. It also removes the one piece of independent technical evidence your buyers ask for most.

What a SOC 2-ready pen test report contains

A report that works for the audit and the sales cycle has:

  • An executive summary a non-technical reader can follow

  • A scope section that names the same systems as your SOC 2 system description

  • Methodology, with reference to standards such as the OWASP Top 10

  • Findings with CVSS scores, proof of exploitation and remediation guidance

  • A mapping of findings to SOC 2 criteria

  • A re-test section or a separate re-test report showing closed findings

  • A short attestation letter you can share with customers without exposing technical detail

Digisecuritas delivers these as standard: executive and technical reports, a CVSS risk matrix, compliance mapping and a re-test report at no extra charge. Our SOC 2 team can align the test scope with your system boundary before work starts. See the VAPT services page and the SOC 2 readiness page.

Book a pen test with a SOC 2-ready report

Tell us your review period and the systems in your SOC 2 scope. We will schedule the test so the report, remediation and re-test all fall inside your audit window.

Book a pen test with a SOC 2-ready report


Frequently Asked Questions

Related reading