Date
August 3, 2026
Author
Karan Patel
,
CEO

Almost every SaaS company preparing for its first SOC 2 report asks the same question: do we actually need a penetration test? Compliance platforms, auditors and enterprise customers all seem to treat it as mandatory. The AICPA framework itself is a bit less direct. This guide covers what the Trust Services Criteria actually say, why auditors still expect a pentest, and what a test needs to look like for its report to hold up as audit evidence.

Is Penetration Testing Required for SOC 2?

The short answer is no, not explicitly. The longer answer is that skipping it is one of the fastest ways to get an exception, a qualified opinion or a stalled enterprise deal.

What the Trust Services Criteria Actually Say

SOC 2 reports are built on the AICPA Trust Services Criteria (TSC). The criteria are principles-based, not prescriptive. They describe what a control environment should achieve, not the specific tools or activities you have to use to get there.

Penetration testing appears in the "points of focus" that sit under some criteria, most notably:

  • CC4.1 (Monitoring Activities): The entity selects, develops and performs ongoing and/or separate evaluations to make sure the components of internal control are present and functioning. Penetration testing is listed as an example of a separate evaluation.
  • CC7.1 (System Operations): The entity uses detection and monitoring procedures to identify changes to configurations that introduce new vulnerabilities, and susceptibilities to newly discovered vulnerabilities. Vulnerability scanning and testing support this criterion.

Points of focus are guidance, not hard requirements. In principle you could satisfy CC4.1 and CC7.1 with other controls. In practice, few organizations can show equivalent assurance without a pentest.

Why Auditors Expect It Anyway

Auditors have to form an opinion on whether your controls are designed well (Type I) and operated effectively over time (Type II). For a cloud-hosted product that takes customer data, the most persuasive evidence that your security controls work is an independent third party trying to break them and documenting what happened.

There are three practical pressures:

  1. Auditor judgment. Most CPA firms that do SOC 2 work treat an annual pentest as the baseline for showing CC4.1 and CC7.1 are effective. Without one, expect questions and requests for alternative evidence.
  2. Customer due diligence. Enterprise security questionnaires ask for a recent pentest summary or attestation letter regardless of what your SOC 2 report says.
  3. Report credibility. A SOC 2 report with no adversarial testing behind it gets more scrutiny from the risk teams reading it.

So "required" may not be the right word, but "expected" certainly is.

Which SOC 2 Controls Does a Pentest Actually Support?

A well-scoped pentest produces evidence that touches several criteria at once. Mapping findings to these controls ahead of time makes the auditor's job easier and cuts down on follow-up requests.

Trust Services Criterion What the Pentest Demonstrates
CC4.1 Independent, separate evaluation of control effectiveness
CC4.2 Deficiencies are communicated to responsible parties
CC6.1 Logical access controls resist unauthorized access
CC6.6 Boundary protections against external threats work
CC6.7 Data in transit is protected
CC7.1 Vulnerabilities are identified through detection procedures
CC7.2 Security events and anomalies are monitored (detection of the test)
CC8.1 Changes are tested before and after deployment

If you also report against the Availability or Confidentiality categories, findings about resilience or data exposure support those criteria too.

What Do SOC 2 Auditors Want to See in a Pentest Report?

Not all pentest reports are equal in an auditor's eyes. A cheap automated scan dressed up as a "penetration test" will not hold up. These are the elements auditors consistently look for.

Scope That Matches Your System Description

Your SOC 2 report contains a system description covering the infrastructure, software, people, procedures and data in scope. The pentest scope must line up with it. If your system description includes a production AWS environment, a customer-facing web app, a public API and a Kubernetes cluster, the pentest should cover all four. A gap between the two is a red flag for the auditor.

A Documented, Recognized Methodology

Auditors want to know the test followed a repeatable standard. References to OWASP WSTG, the OWASP API Security Top 10, PTES or NIST SP 800-115 show the testing was structured and not ad hoc. The report should state which methodology was used and how it was applied.

Clear Dates Inside the Audit Period

For a Type II report, the pentest has to fall within the observation window, usually 3 to 12 months. A test completed two weeks before the window opens does not count as evidence of operating effectiveness during that window.

Risk-Rated Findings With Business Context

Each finding should include a severity rating (CVSS v3.1 or v4.0 is common), affected assets, evidence, and specific remediation guidance. Auditors use severity ratings to judge whether your remediation timelines were reasonable.

Remediation and Retest Evidence

This is where many organizations fall short. Auditors don't expect a clean report. They expect proof that you handled what was found. A retest letter confirming critical and high findings were fixed, together with tickets showing when each was resolved, closes the loop on CC4.2 and CC7.1.

Tester Independence and Qualifications

The test should be done by a party independent of the people who built and run the system. Auditors may also ask about tester qualifications, such as OSCP, OSWE, CRTO or equivalent experience.

Redfox Cybersecurity's penetration testing services are scoped against your SOC 2 system description from the start, so the report maps directly onto the controls your auditor will test.

How Often Should You Run a SOC 2 Penetration Test?

The industry standard is at least once a year, with extra testing after significant changes. What counts as significant:

  • A new major product feature or public API
  • Migration to a new cloud provider or region
  • Large infrastructure changes, such as moving from VMs to Kubernetes
  • A merger or acquisition that brings new systems into scope
  • A security incident that revealed control weaknesses

Type I vs Type II Timing

For a Type I report, which is a point-in-time assessment, a pentest done shortly before the report date shows the controls are designed appropriately. For a Type II report, schedule the pentest early enough in the observation window to leave time for remediation and retest before the window closes. A good rule is to test in the first third of the period.

What a SOC 2-Ready Penetration Test Looks Like in Practice

The technical depth of the test decides whether the report actually shows control effectiveness. Below is a realistic view of the phases a professional engagement covers and the tooling experienced testers use to produce auditable evidence.

Defining Scope as Code

Good engagements start by turning the system description into a machine-readable scope file. This prevents out-of-scope testing and gives the auditor a clear record of what was covered.

# soc2_pentest_scope.yaml
engagement: "SOC 2 Type II Annual Pentest"
audit_period: "2026-01-01 to 2026-12-31"
test_window: "2026-03-02 to 2026-03-20"
methodology: ["OWASP WSTG v4.2", "OWASP API Top 10 2023", "NIST SP 800-115"]
in_scope:
 web_apps:
   - https://app.example.com
 apis:
   - https://api.example.com/v2
 cloud:
   - provider: aws
     accounts: ["111122223333", "444455556666"]
 kubernetes:
   - cluster: prod-eks-use1
out_of_scope:
 - https://status.example.com   # third-party hosted
 - denial_of_service_testing
contacts:
 emergency: secops@example.com

[cta]

External Attack Surface Reconnaissance

Testing begins by mapping everything an attacker can see. This confirms CC6.6 boundary protections and often surfaces shadow IT that is missing from your asset inventory.

# Enumerate subdomains from passive sources
subfinder -d example.com -all -recursive -o subdomains.txt

# Probe live hosts with tech fingerprinting
httpx -l subdomains.txt -title -tech-detect -status-code \
 -follow-redirects -o live_hosts.txt

# Service discovery on in-scope IP ranges
nmap -sS -sV -p- --min-rate 2000 -T4 -iL scoped_ips.txt -oA external_full

# Templated detection of known misconfigurations and exposures
nuclei -l live_hosts.txt -severity critical,high,medium \
 -etags dos,fuzz -rl 50 -o nuclei_external.txt

[cta]

Each discovered asset is checked against the system description. A forgotten staging environment holding production data is a common finding, and it is far better for a tester to find it than an attacker.

TLS and Transport Security Validation

Encryption in transit is a frequent auditor focus under CC6.7. Testers check protocol versions, cipher suites and certificate configuration, and keep the output as evidence.

# Full TLS assessment with exportable evidence
testssl.sh --severity MEDIUM --jsonfile-pretty tls_results.json \
 --htmlfile tls_report.html https://app.example.com

# Quick cipher enumeration
nmap --script ssl-enum-ciphers -p 443 app.example.com

[cta]

Web Application and API Testing

For most SaaS companies the application layer is where the real risk sits. This phase is mainly manual and is done in Burp Suite Professional against the OWASP WSTG and API Security Top 10. The areas auditors care most about are:

  • Tenant isolation and authorization: confirming that one customer can never read or modify another customer's data. Failures here map straight to CC6.1.
  • Authentication and session management: MFA enforcement, session expiry, token handling and password reset flows.
  • Input handling: injection classes, server-side request forgery and file upload controls.
  • Business logic: pricing, role changes and workflow steps that automated scanners can't reason about.

Testers usually work with two accounts per role across at least two tenants, so cross-tenant access can be checked across every object type the API exposes. If your product is multi-tenant, Redfox Cybersecurity's web application and API penetration testing puts tenant isolation first, because it is the finding that matters most to your auditor and your customers.

Cloud Configuration Review

Most SOC 2 environments live in AWS, Azure or GCP. A configuration review against CIS benchmarks provides evidence for CC6.1, CC6.6 and CC7.1 in one pass.

# AWS: CIS benchmark and SOC 2 mapped checks with Prowler
prowler aws --compliance soc2_aws cis_2.0_aws \
 --output-formats csv html json-ocsf \
 --output-directory ./evidence/prowler

# Multi-cloud posture review with ScoutSuite
scout aws --profile audit-readonly --report-dir ./evidence/scoutsuite

# Azure equivalent using Prowler
prowler azure --az-cli-auth --compliance cis_2.0_azure \
 --output-directory ./evidence/prowler-azure

[cta]

Prowler's SOC 2 compliance mapping is especially useful because it tags each check with the related Trust Services Criterion, which saves hours of manual mapping. Typical findings include overly permissive IAM policies, public storage buckets, missing CloudTrail coverage in some regions, and security groups exposing management ports.

Container and Kubernetes Posture

If your system description includes containers, auditors expect them in scope. Testers assess cluster configuration, image vulnerabilities and RBAC.

# CIS Kubernetes benchmark checks on EKS worker nodes
kubectl apply -f https://raw.githubusercontent.com/aquasecurity/kube-bench/main/job-eks.yaml
kubectl logs job/kube-bench > ./evidence/kube-bench-eks.txt

# Scan production images for known vulnerabilities and misconfigurations
trivy image --severity HIGH,CRITICAL --format json \
 -o ./evidence/trivy_api.json registry.example.com/api:2026.03.1

# Cluster-wide misconfiguration and RBAC review
trivy k8s --report summary --compliance k8s-cis-1.23 cluster

# Identify overly broad RBAC bindings
kubectl get clusterrolebindings -o json | \
 jq -r '.items[] | select(.roleRef.name=="cluster-admin") |
 "\(.metadata.name): \(.subjects[]?.name)"'

[cta]

Internal Network and Identity Testing

When corporate identity systems such as Entra ID, Okta or Active Directory govern access to production, auditors increasingly expect them in scope. This phase tests whether a compromised employee laptop or phished account could reach customer data. The report should document which paths were tried, which controls stopped them (conditional access, privileged access management, network segmentation) and where gaps exist. That gives evidence for CC6.1, CC6.2 and CC6.3 on user access provisioning and least privilege.

Redfox Cybersecurity's internal and cloud identity assessments are built to show auditors how your access controls hold up against realistic attack paths, not just that they exist on paper.

How to Turn Pentest Findings Into SOC 2 Audit Evidence

A report sitting in a shared drive is not evidence on its own. Auditors want to see the full lifecycle: finding, ticket, fix, verification.

Set Remediation SLAs by Severity

Define remediation timelines in your vulnerability management policy and stick to them. A common baseline:

Severity Remediation SLA
Critical 7 to 15 days
High 30 days
Medium 90 days
Low 180 days or risk accepted

Your auditor will sample findings and compare remediation dates against these SLAs. Missed SLAs without documented risk acceptance are a common source of exceptions.

Track Findings Programmatically

Linking pentest findings to your ticketing system creates a clean audit trail. Here is a simple script that imports findings from a JSON report into Jira with severity-based due dates:

import json
from datetime import date, timedelta
from jira import JIRA

SLA_DAYS = {"Critical": 15, "High": 30, "Medium": 90, "Low": 180}

jira = JIRA(server="https://example.atlassian.net",
           basic_auth=("secops@example.com", "API_TOKEN"))

with open("pentest_findings.json") as f:
   findings = json.load(f)

for item in findings:
   due = date.today() + timedelta(days=SLA_DAYS[item["severity"]])
   issue = jira.create_issue(
       project="SEC",
       summary=f"[Pentest 2026] {item['id']}: {item['title']}",
       description=(
           f"Severity: {item['severity']} (CVSS {item['cvss']})\n"
           f"Affected: {', '.join(item['assets'])}\n"
           f"TSC Mapping: {', '.join(item['tsc'])}\n\n"
           f"Remediation:\n{item['remediation']}"
       ),
       issuetype={"name": "Vulnerability"},
       duedate=due.isoformat(),
       labels=["soc2", "pentest-2026", item["severity"].lower()],
   )
   print(f"Created {issue.key} due {due}")

[cta]

Get a Retest Letter

Once critical and high findings are fixed, the testing firm should verify each fix and issue a retest letter or updated report. This independent confirmation is far stronger evidence than an internal "fixed" status on a ticket.

Produce an Evidence Package

Organize everything the auditor will ask for in one place:

soc2-evidence-2026/
├── 01_scope/
│   ├── soc2_pentest_scope.yaml
│   └── rules_of_engagement_signed.pdf
├── 02_reports/
│   ├── pentest_report_2026-03.pdf
│   └── retest_letter_2026-04.pdf
├── 03_tool_output/
│   ├── prowler/
│   ├── kube-bench-eks.txt
│   └── tls_report.html
├── 04_remediation/
│   ├── jira_export_pentest_2026.csv
│   └── risk_acceptances_signed.pdf
└── 05_detection/
   └── siem_alerts_during_test_window.csv

[cta]

The detection folder is often overlooked. If your SIEM or EDR flagged the testers' activity, export those alerts. They are direct evidence for CC7.2, showing your monitoring controls work.

Common SOC 2 Pentest Mistakes That Trigger Auditor Questions

These are the issues that most often lead to follow-up requests or exceptions:

  • Vulnerability scan passed off as a pentest. Auditors can tell the difference. A pentest involves manual testing, exploitation validation and business logic review.
  • Scope gaps. Testing the web app but leaving out the API or cloud environment named in your system description.
  • Testing outside the observation window. The test date must fall within the Type II audit period.
  • No remediation evidence. A report full of open highs with no tickets, retest or risk acceptance.
  • Undocumented risk acceptance. If you choose not to fix something, record the business rationale, compensating controls and executive sign-off.
  • Testing by internal staff only. Internal red teams add value, but auditors usually want third-party independence for the annual test.
  • Stale reports. Handing over last year's report because this year's test slipped.

How to Choose a Penetration Testing Partner for SOC 2

The right partner makes your audit smoother. When evaluating providers, ask:

  1. Do you map findings to Trust Services Criteria? This saves your compliance team significant time.
  2. Is testing primarily manual? Ask for the ratio of manual to automated work and sample findings from previous reports.
  3. Is a retest included? Retest pricing and turnaround matter for meeting audit timelines.
  4. Do you provide an attestation letter? Customers will ask for a shareable summary that doesn't expose detailed findings.
  5. What are your testers' qualifications? Look for recognized offensive certifications and relevant cloud and application experience.
  6. Can you work with my auditor? Some auditors want to talk with the testing firm about methodology.

Redfox Cybersecurity offers SOC 2-aligned penetration testing with TSC-mapped findings, a retest, and a customer-ready attestation letter, built for teams on an audit deadline. Current packages and pricing for web application, API, cloud and network engagements are listed on the Redfox Cybersecurity website.

Key Takeaways

SOC 2 doesn't explicitly require penetration testing, but in practice it is one of the most important pieces of evidence you can give an auditor. Pentesting appears as a point of focus under CC4.1, supports CC6 and CC7 controls, and is something enterprise customers will ask for no matter what the framework says.

To make your pentest count:

  • Match the test scope to your SOC 2 system description
  • Schedule testing early in your Type II observation window
  • Require a recognized methodology and TSC-mapped findings
  • Track every finding through to remediation within defined SLAs
  • Get a retest letter for critical and high findings
  • Package scope, reports, tool output, tickets and detection evidence together

Treated as a compliance checkbox, a pentest produces a PDF. Treated as a real control evaluation, it gives you evidence your auditor can rely on and a security posture your customers can trust. If your audit window is coming up, talk to Redfox Cybersecurity about scoping a test that fits your timeline.

Copy Code