Compliance / SOC 2

    SOC 2 penetration testing, without the audit scramble.

    A pen-test report your auditor will accept, produced on your Type I or Type II timeline — not theirs. Fixed-scope, retest-included, mapped to the Trust Services Criteria your assessor is actually checking.
    Criteria coverageCommon criteria · Type IICC4.1CC5.2CC6.1CC6.6CC6.7CC6.8CC7.1CC7.2CC7.3CC7.4CC8.1CC9.17 raised · evidenced by test12 common criteria

    The honest requirement

    Pen testing isn't literally in the TSC — but auditors expect it anyway.

    The AICPA's Trust Services Criteria do not name "penetration testing" as a mandatory control. The word doesn't appear in CC1–CC9. So technically, no — SOC 2 does not require a pen test to pass.

    In practice: assessors want evidence of vulnerability identification and control-effectiveness testing, particularly under CC4.1 (monitoring of controls) and CC7.1 (detection and monitoring of new vulnerabilities). An annual third-party pen test has become the de facto way service organizations satisfy those criteria, and most SOC 2 audit programs now list it in the request-for-evidence template. Skip it and you'll spend the audit explaining why you didn't do it — that's the "audit scramble."

    Which criteria your report ends up supporting: CC4.1 (separate evaluations),CC6.1 / CC6.6 / CC6.8 (logical access, boundary protection, unauthorized software), CC7.1 / CC7.2 (vulnerability detection and anomaly monitoring), and CC8.1 (change verification, via the retest). Whether you're pursuing Type I or Type II changes the timing of the test, not the criteria — the comparison and window sequencing below lay out the difference.

    Type I vs Type II

    Same test. Very different timing.

    Type I

    Design of controls, at a point in time.

    • Auditor asks: were the controls suitably designed as of the report date?
    • One pen test, run in the weeks before the report date.
    • Report freshness matters more than remediation history.

    Type II

    Operating effectiveness, across the observation window.

    • Auditor asks: did the controls operate effectively throughout the period?
    • Pen test run early in the window, so remediation and retest also land inside it.
    • Dated artifacts prove the vulnerability-management control actually works.

    Sequencing

    Where the pen test belongs in a 12-month window.

    Run the engagement in the first months of the observation period. That leaves room for remediation and a retest well before fieldwork, so the auditor sees a complete cycle rather than a snapshot. If your window is already underway, we sequence to whatever time is left and tell you honestly what evidence is still achievable.

    Observation window · 12 months: Test — First findings within 72 hours of kickoff, every engagement. Focused 5 to 7 business days. Standard 7 to 10 business days. Extended 2 to 4 weeks. Dated engagement letter and scope memo.; Remediate — Your engineers work the severity-ranked fix order, with the AI-actionable companion file.; Retest — Free retest of remediated findings within 60 days. Signed retest letter confirming closure.; Fieldwork — Auditor reviews the full cycle — finding, fix, verification — all dated inside the period.
    Observation window · 12 monthsAudit report issued
    01 · Test
    First findings within 72 hours of kickoff, every engagement. Focused 5 to 7 business days. Standard 7 to 10 business days. Extended 2 to 4 weeks. Dated engagement letter and scope memo.
    02 · Remediate
    Your engineers work the severity-ranked fix order, with the AI-actionable companion file.
    03 · Retest
    Free retest of remediated findings within 60 days. Signed retest letter confirming closure.
    04 · Fieldwork
    Auditor reviews the full cycle — finding, fix, verification — all dated inside the period.

    Coverage

    Which criteria the engagement produces evidence for.

    Criteria evidenced by the engagement, grouped by control family: CC4.1, CC6.1, CC6.6, CC6.8, CC7.1, CC7.2, CC8.1
    Coverage7 / 7 criteria evidenced
    MonitoringLogical accessDetection & responseChange managementCC4.1CC6.1CC6.6CC6.8CC7.1CC7.2CC8.1
    CC4.1Ongoing and separate evaluations of whether controls are functioning.Independent third-party pen-test report on firm letterhead — the canonical separate evaluation.
    CC6.1Logical access controls restrict access to authorized users.Authentication, authorization, and privilege-escalation findings with working proof-of-concept.
    CC6.6Protection against threats from outside the system boundary.External and perimeter test results, exposed-service inventory, and attack-surface diff.
    CC6.8Detection and prevention of unauthorized or malicious software.Upload, deserialization, and code-execution testing with evidence of controls that held.
    CC7.1Monitoring for new vulnerabilities and configuration changes.Findings register with CVSS ratings, business-risk annotations, and configuration observations.
    CC7.2Monitoring for anomalies indicative of malicious acts.Attack-chain diagrams plus Sigma detection rules and a note on what did and did not alert.
    CC8.1Changes are authorized, designed, tested, and approved.Retest letter verifying remediated findings are closed — dated inside the observation window.

    What auditors accept

    Evidence, in the format your assessor already uses.

    • Dated engagement letter and scope memo on firm letterhead

    • Severity-ranked findings register with working proof-of-concept and discovery dates

    • Remediation guidance mapped to CC4.1, CC6.x, CC7.1, and CC7.2

    • Signed retest letter confirming remediated findings are closed

    • Control-testing narrative your auditor can attach directly as evidence

    • Sigma detection rules and attack-chain diagrams for monitoring criteria

    Engagement mapping

    The D1–D9 engagement, mapped to SOC 2 evidence.

    SOC 2 evidence timeline

    Testing window

    1. D1

      Recon & scoping, rules of engagement signed.

    2. D2–3

      Surface mapping across external, authenticated, and cloud config surfaces.

    3. D4–6

      Exploit reasoning and vulnerability chaining, human-validated.

    4. D7–8

      Controlled PoC and lateral-movement testing in lab.

    5. D9

      Reporting and live client walkthrough.

    D1
    Dated scope memo referencing in-scope TSC boundaries and CUEC assumptions.Recon & scoping, rules of engagement signed.
    D2–3
    Asset inventory supporting CC6.1 and CC6.6 evidence requests.Surface mapping across external, authenticated, and cloud config surfaces.
    D4–6
    Findings register with CVSS + business-risk annotations for CC7.1.Exploit reasoning and vulnerability chaining, human-validated.
    D7–8
    Proof-of-exploit captures and Sigma detection rules for CC7.2.Controlled PoC and lateral-movement testing in lab.
    D9
    Signed report + remediation plan filed in your SOC 2 evidence room.Reporting and live client walkthrough.
    +60d
    Retest letter closing the loop for CC8.1 — dated inside your observation window.Free retest of remediated findings.

    SOC 2 FAQ

    Frequently asked.

    Not literally — the Trust Services Criteria don't name penetration testing. But auditors overwhelmingly expect it as evidence under CC4.1 (monitoring) and CC7.1 (vulnerability detection). Most modern SOC 2 audit programs list a recent third-party pen test in the request-for-evidence template, so in practice it's a de facto requirement.

    For Type I (point-in-time), run the pen test in the weeks before the audit date so the report is fresh and remediation is complete. For Type II (audit period), run it early in the observation window so any critical findings have time to be remediated and retested inside the same period — that way both the finding and the fix live inside the reviewed evidence. The comparison and sequencing sections above walk through the difference and the criteria coverage in detail.

    Early — ideally in the first two or three months. That leaves time for remediation and a retest to also land inside the window, so the auditor can see the full cycle: finding, fix, verification. A test run in the final weeks leaves open findings and no remediation evidence, which is the most common avoidable Type II exception.

    You remediate and we retest. A critical finding that was detected, fixed, and verified inside the window is evidence your vulnerability-management control works — it is not automatically an exception. What auditors react badly to is an open critical with no documented response. We prioritise the fix order so the highest-risk items close first.

    Yes. Retesting of remediated findings within 60 days is included in every engagement at no extra cost, and produces a signed retest letter you can file as evidence.

    First findings within 72 hours of kickoff, every engagement. Focused 5 to 7 business days. Standard 7 to 10 business days. Extended 2 to 4 weeks. If your fieldwork starts sooner, tell us during scoping. We do not skip validation to hit a date.

    Yes. We'll sign an NDA, take scope input from your auditor before kickoff, and answer their follow-up questions on the report directly. We are a penetration testing firm, not an audit firm — we don't issue SOC 2 opinions, we produce the technical evidence your assessor evaluates.

    Evidence by framework

    Same engagement. Different paperwork.

    Auditors read the report as evidence of separate evaluations and vulnerability detection.

    Mapped to CC4.1 · CC7.1 · CC7.2

    Next step

    Scope a SOC 2 pen test.

    Thirty-minute scoping call. Fixed-scope quote within one business day. Report and evidence bundle ready for your auditor.

    Request a pen test scope call →