# SOC 2 Penetration Testing or Vulnerability Scan: What Is Actually Required?

> SOC 2 penetration testing is not named as a requirement, but auditors and buyers usually expect it. Where it fits the criteria and what evidence to keep.

- Canonical: https://auditsuisse.com/soc-2-penetration-testing-requirements
- Language: en
- Author: Sébastien Ruosch, CPA — Director of Audits
- Published: 2026-11-14
- Updated: 2026-11-14
- Alternates: fr → https://auditsuisse.com/fr/tests-d-intrusion-soc-2-exigences, es → https://auditsuisse.com/es/pruebas-de-penetracion-soc-2-requisitos

SOC 2

 The short answer

The Trust Services Criteria do not state that a [penetration test](https://auditsuisse.com/penetration-testing) is mandatory. They require you to detect vulnerabilities (CC7.1) and to evaluate whether controls are working (CC4.1), and the points of focus mention vulnerability scans and penetration testing as ways to do that. In practice, most auditors expect regular vulnerability scanning, and most enterprise buyers expect an annual penetration test.

## Key takeaways

- Scanning is automated and frequent. Penetration testing is a skilled, time-boxed attempt to exploit weaknesses.
- You need a defined approach to both, and you need to follow it.
- The control that gets tested is often remediation: were findings fixed within your stated timeframes?
- If your policy says “annual penetration test”, you must have one within the period.

## Scan vs penetration test

|  | Vulnerability scan | Penetration test |
| --- | --- | --- |
| Performed by | Tool | Qualified tester, with tools |
| Frequency | Continuous, weekly or monthly | Annually and after major change |
| Finds | Known vulnerabilities and misconfigurations | Exploitable paths, logic and access-control flaws |
| Output | List of findings by severity | Report with reproduction steps and impact |
| Criteria link | CC7.1 | CC4.1, CC7.1 |

## What the auditor looks at

- Your policy: what you scan, how often, and remediation timeframes by severity.
- Scan results across the period.
- The penetration test report, its scope and date.
- Tickets showing findings were triaged and fixed on time, and retest results.
- Risk acceptance for anything not fixed, approved by management.

## Scoping a penetration test for SOC 2

Match it to the system description: the production web application and APIs, authenticated testing with more than one role, and tenant isolation for multi-tenant products. External infrastructure is commonly included. A test of a marketing website does not support a report on your product.

## Independence note

Penetration testing is a separate service from the SOC 2 examination. The tester’s findings are management’s to remediate, and the auditor evaluates your process, not the tester’s skill. See [penetration testing](https://auditsuisse.com/penetration-testing).

## Frequently asked questions

### Will an automated or AI-driven test satisfy an auditor?

The criteria do not specify a method. What matters is that the assessment is appropriate to your risks and that you act on it. Some buyers ask specifically for a human-led test.

### How recent must the test be?

Within the report period is the safe answer.

### Do we need both internal and external scans?

For cloud-hosted products, scan external endpoints, infrastructure configuration, container images and dependencies.

## Sources & further reading

AICPA 2017 Trust Services Criteria, CC4.1 and CC7.1 with points of focus.

**Related:** [SOC 2 controls list](https://auditsuisse.com/soc-2-controls-list-by-trust-services-criteria), [Most common SOC 2 findings](https://auditsuisse.com/soc-2-common-findings-and-how-to-fix-them), [SOC 2 risk assessment](https://auditsuisse.com/soc-2-risk-assessment), [SOC 2 on AWS and Azure](https://auditsuisse.com/soc-2-on-aws-and-azure).

---
Source: https://auditsuisse.com/soc-2-penetration-testing-requirements · This Markdown edition is generated from the same content as the HTML page.
