1. Home
  2. Solutions
  3. SOC 2 compliance

Solutions · Compliance · SOC 2

SOC 2 penetration testing your auditor can map to the Trust Services Criteria

SOC 2 compliance is more than a checkbox. ioSENTRIX tests the systems in your SOC 2 scope the way an attacker would, maps every finding to the criteria your auditor examines, and includes a retest of your fixes so the evidence holds up in a Type 1 or Type 2 report.

FrameworkAICPA SOC 2 · Trust Services Criteria, Security (common criteria)
Who asksYour customers, their vendor-risk teams and your CPA firm
What you getA scoped test, proven findings, retest results and an auditor-ready report
Reviewed by Omair Manzoor, Founder & CEO, ioSENTRIX · Updated November 2026Key terms: SOC 2, Penetration testing, Vulnerability scanning
Trusted by security teams at

01The requirement

Is penetration testing required for SOC 2?

Not by name. None of the AICPA Trust Services Criteria names a penetration test. But criterion CC4.1 calls for ongoing and/or separate evaluations of whether controls are present and functioning, and CC7.1 expects you to detect new vulnerabilities. An independent penetration test is direct evidence for both, which is why most SOC 2 auditors ask for one.

Mandatory?No criterion says "pentest"

Points of focus describe important characteristics, but the criteria do not require each one to be addressed.

Expected?Auditors and customers ask

A pentest is the most direct evidence that your security controls work as described.

Type 2Inside the review period

Test within the window, track findings to closure and keep the retest results.

What is SOC 2 penetration testing?

SOC 2 penetration testing is a penetration test scoped to the system described in your SOC 2 report: the applications, APIs, cloud infrastructure and networks that process customer data. It is documented so that findings, remediation and the retest can be presented to your auditor as evidence for the Security criteria.

What does SOC 2 compliance require?

A SOC 2 report is an attestation by an independent CPA firm on controls relevant to security, availability, processing integrity, confidentiality or privacy. Security (the common criteria) is in every report. You need controls that meet the criteria, evidence that they operate, and an auditor who examines both. Compare frameworks in SOC 2 vs ISO 27001.

02See it in action

From control to accepted evidence

How one control in your SOC 2 matrix is tested like an attacker would, fixed, retested and handed to your auditor as evidence.

A control, not a scan

We start from the control in your SOC 2 matrix and test whether it holds against a real attacker, so the result answers the auditor's question directly.

Proof your auditor can read

Each finding carries evidence, business impact and the criteria it supports, written so a CPA firm can follow it without a tester in the room.

Done when the evidence is accepted

A retest of your fixes is included, and we answer your auditor's questions about our report until it is accepted.

Illustrative example. The control, endpoint and statuses are a composite for explanation only and do not describe any client.

Text version of the exhibit
  1. Control: your SOC 2 control matrix says customers can only see their own organization's data. The test supports criteria CC6.1, CC4.1, CC3.2, CC6.6 and CC7.1.
  2. Test: testers sign in as one tenant and request another tenant's report by changing its ID.
  3. Finding: the report is returned. The finding is rated High and mapped to OWASP A01 Broken Access Control, with evidence of the impact.
  4. Fix: we describe a server-side ownership check for your engineers.
  5. Retest: the same request is refused, the fix is confirmed, and the change is linked to CC8.1.
  6. Accepted: the evidence folder (scope, finding with proof, fix, retest and criteria mapping) is handed to your auditor, and we answer questions until the report is accepted.

03Requirement to evidence

How does penetration testing map to the SOC 2 Trust Services Criteria?

One test can support several common criteria at once. This is the mapping we put in your report, so your auditor can trace each piece of evidence back to the criterion it supports.

CriterionWhat the criterion asksWhat ioSENTRIX testsEvidence for your auditor
CC3.2Risk assessmentIdentify and analyze risks to objectives, including threats to and vulnerabilities of your information assets.Threat modeling and attack-surface review of the in-scope system.Threat model and risk-ranked findings
CC4.1Monitoring activitiesOngoing and/or separate evaluations of whether the components of internal control are present and functioning.An independent penetration test of the applications, APIs, cloud and network in scope.Report with scope, dates, method and testers
CC6.1Logical accessLogical access security over protected information assets.Authentication, authorization, session handling and tenant isolation in your web apps and APIs.Access-control findings with proof and fix guidance
CC6.6Threats from outsideLogical access measures that protect against threats from sources outside your system boundaries.External network penetration test and exposed-service review.External test results and exposed services list
CC7.1Detection of vulnerabilitiesDetect configuration changes that introduce vulnerabilities, and susceptibility to newly discovered ones. Points of focus include vulnerability scans.Cloud configuration review and manual validation of your scanner's results.Misconfiguration findings and scan validation notes
CC7.2Monitoring for anomaliesMonitor system components for anomalies that indicate malicious acts, and analyze them.Optional red team or purple team exercise to see whether your monitoring raises an alert.Detection timeline: what alerted and what did not
CC8.1Change managementChanges to infrastructure, data and software are authorized, tested and approved before implementation.Retests after significant changes, or PTaaS for teams that release often.Retest results tied to each change

Criterion wording summarized from the AICPA 2017 Trust Services Criteria (TSP section 100); the 2022 revision updated points of focus, not the criteria. Points of focus are not requirements; your auditor decides what evidence is sufficient. ioSENTRIX is not a CPA firm and does not issue SOC 2 reports.

04Timing

When should you run a SOC 2 penetration test?

Early enough to fix and retest before the evidence is due. This is how a test fits into a SOC 2 cycle.

  1. Readiness

    Gap review against the Trust Services Criteria, documentation and audit preparation.

    Readiness assessment
  2. Scope

    Match the test to your system description: apps, APIs, cloud and network.

    Written scope
  3. Test

    Manual testing by certified engineers. A web application test typically takes 1–2 weeks.

    Manual testing
  4. Fix and retest

    Fix guidance for each finding, then a retest of your fixes.

    Retest included
  5. Audit window

    For Type 2, the test and retest fall inside your review period.

    Evidence pack
  6. Auditor questions

    We answer your CPA firm's questions about the report until it is accepted.

    Accepted
SOC 2 Type 1Design at a point in time

A penetration test shows that your testing control exists and was carried out by the report date. Useful evidence, often optional.

SOC 2 Type 2Operation over a period

The auditor needs to see the control operating during the review period: a test inside the window, findings tracked to closure and a retest.

05Evidence pack

What's in a SOC 2 penetration test evidence pack?

Everything your auditor and your customers' vendor-risk teams ask for, in one place.

  1. Executive summary

    Scope, method and results in plain language for executives, auditors and customers.

  2. Scope and method

    Systems, dates, testers and the standards followed, matched to your SOC 2 system description.

    OWASP Top 10OWASP ASVSNIST SP 800-115
  3. Findings with proof

    Each finding with evidence, severity, business impact and the steps to reproduce it.

  4. Fix guidance

    Specific remediation your engineers can act on, prioritized by risk.

  5. Retest results

    Fixes retested and recorded, so findings are tracked to closure.

  6. Criteria mapping

    Each result mapped to the Trust Services Criteria it supports.

    CC3.2CC4.1CC6.1CC6.6CC7.1CC8.1

06Independently verified

★★★★★
“The team at ioSENTRIX is professional and highly skilled at their craft.”
Awwab A.SVP, Chief Information Security Officer · Verified G2 review ↗
★★★★★
“We were impressed with ioSENTRIX's ability to independently validate the security of our customer-facing product.”
Zeehasham R.Data Scientist, Security Operations · Insurance · Verified Clutch review ↗

08Insights

Read before you scope your SOC 2 test

09FAQ

SOC 2 penetration testing questions

Short answers to what buyers and auditors ask us most.

Ask us something else

Is penetration testing required for SOC 2?

Not by name. None of the AICPA Trust Services Criteria names a penetration test. Criterion CC4.1 calls for ongoing and/or separate evaluations of whether controls are present and functioning, and a CC7.1 point of focus covers vulnerability scans. An independent penetration test is direct evidence for both, so most SOC 2 auditors ask for a recent report. Read our guide to SOC 2 penetration testing requirements.

How often should we run a SOC 2 penetration test?

SOC 2 does not set a fixed frequency. Your own control description and your auditor decide it, and many organizations test annually and after significant changes. For a Type 2 report, the test should fall inside the review period so the auditor can see the control operating, with findings tracked to closure.

What is the difference between SOC 2 Type 1 and Type 2 for penetration testing?

A Type 1 report covers the design of controls at a point in time, so a penetration test shows that a testing control exists by the report date. A Type 2 report covers design and operating effectiveness over a review period, so the auditor expects a test performed inside that period, remediation evidence and a retest.

Is a vulnerability scan enough for SOC 2?

Usually not on its own. A CC7.1 point of focus covers vulnerability scans, and a scan lists known weaknesses automatically. A penetration test is carried out by people who exploit and chain weaknesses, including business logic flaws, and prove the impact. Auditors treat them as different activities, and most SOC 2 programs need both.

What is a SOC 2 readiness assessment?

A SOC 2 readiness assessment is a gap review against the Trust Services Criteria before your audit starts. ioSENTRIX provides readiness assessments, documentation support and audit preparation, then runs the penetration test so the evidence is ready when your auditor asks for it.

Does ioSENTRIX issue the SOC 2 report?

No. A SOC 2 report is issued by an independent CPA firm. ioSENTRIX provides the testing, the evidence and readiness support, and answers your auditor's questions about our report until it is accepted.

How long does a SOC 2 penetration test take?

A web application penetration test typically takes 1–2 weeks, depending on scope. After a short scoping call you receive a written scope and timeline before testing starts, so you can plan it inside your audit window.

Ready when you are

Get SOC 2 evidence your auditor can use

Tell us your report type, review period and what is in scope. We will help you scope the right test and plan it inside your audit window.

  • Written scope and timeline before testing starts
  • Retest of fixes included
  • Report mapped to the Trust Services Criteria
Scope your SOC 2 penetration test

Takes about a minute.