Skip to main content
Cloudflare Launchpad About the Launchpad

SOC 2 penetration testing

SOC 2 penetration testing your assessor can follow.

We pentest your web apps, APIs, networks and servers within an agreed scope. Scope, finding, fix and retest stay in one dated record for your assessor.

  • A named consultant approves each finding before you see it. The gate is enforced in our database.
  • Report in 48 hours, then retests of fixed findings for 12 months, under agreed scope, ready access and engagement terms.
Illustrative evidence file / SP-014Fictional dates and records

Cross-customer
order access

Customer A can retrieve an order that belongs to Customer B.

Test boundary
Example Store / agreed API roles
Observed
12 October / request and response retained
Review
Named ManticoreAI consultant approves before you see it
Limitation
One tested behavior, at one point in time
Open the illustrative report

Attach the next evidence, keep the earlier record.

  1. Agreed scope

    Systems, roles and method, plus the audit scope and period.

  2. Reviewed finding

    Request, response, impact and limitations.

  3. Fix record

    Owner, change and deployment reference.

  4. Retest record

    The same request replayed, normal use checked, anything still open.

Does SOC 2 require a pentest?

SOC 2 does not mandate one. The criteria list penetration testing as one way to evaluate controls, and we scope the test to fit your examination.

SOC 2 is a wider examination of controls. A pentest report alone does not establish SOC 2 compliance.

Wider examination period
A scoped test is a point within it.

Type I looks at one date. Type II covers a period: plan the test and any retest inside it.

Make the report useful after the test date.

Security needs demonstrated impact and priorities. Engineering needs reproduction steps and a fix. Assurance needs the scope, method, reviewer and dated record.

The record shows what was tested and what was excluded, and keeps each fix, its owner and its retest result with the finding.

What the report gives your assessor

  • Tested scope and method, with exclusions and limitations stated.
  • Request and response evidence for each demonstrated impact.
  • Severity rationale for each finding.
  • The named consultant who approved each finding before release.
  • Dated retest results for fixed findings, under the agreed retest terms.

Read the framework. See the report.

AICPA defines the SOC reporting framework and the criteria your assessor applies.

See what you receive.

The illustrative sample report uses fictional data. See what we test across web apps, APIs, networks and servers.

Our guide answers the requirement questions in more depth.

Testing supports your assessment. We agree scope and evidence with you and your assessor.

Bring the evidence requirements to the scoping call.

Tell us the systems, audit scope and period, and desired report date. We will agree the assessment boundary and deliverables.

Discuss SOC 2 evidence