Skip to main content

Penetration Testing

Prepare for Audit Execution

Scope and estimate penetration tests correctly before engaging vendors to ensure audit acceptance.

Guidance only; align scope with your auditor. Last updated: 2026-01-05.

What is a penetration test?

A penetration test is a time-boxed security assessment where a qualified tester simulates real-world attacks to identify exploitable weaknesses. For SOC 2, it provides evidence of effective technical controls and vulnerability management within your production environment.

Learn more

Why this matters for SOC 2

Penetration testing is often a required activity for the Security, Availability, and Confidentiality trust service criteria. It proves your vulnerability management process isn't just theoretical.

  • Auditors look for clear scope that matches your system description.
  • Enterprise buyers use the pentest executive summary as a key trust signal.
  • Retesting is critical to show that findings were actually remediated.

How it works

  1. Use the Scoping Worksheet to define your technical targets and auth complexity.
  2. Run the Cost Estimator to set budget expectations and timeline windows.
  3. Align the test with your SOC 2 observation window and share the SOW with your auditor.

Use as guidance—align technical scope with your security lead and auditor.

SaaS pentests

Focus on multi-tenant data isolation, API auth, and session management. Usually requires annual testing.

Review SaaS Scoping

Fintech pentests

High scrutiny on payment flows, encryption, and segregation of duties. Often includes API and network layers.

Review Fintech Scoping

Healthcare pentests

Deep review of ePHI access controls and breach notification triggers. Cadence often tied to HIPAA/SOC 2 cycles.

Estimate cost

Marketplace pentests

Fraud-abuse focus and buyer/seller data separation. Scope typically covers full web+API stacks.

Run estimator