Website security · Raksha guide

SOC 2 Penetration Test: Planning Evidence With Your Auditor

SOC 2 is an examination of controls, not a universal checklist that names a mandatory annual penetration test for every organisation. Penetration testing can support security-control evidence, but the appropriate scope, timing and tester qualifications should be agreed with your service auditor.

By Raksha · Reviewed 16 November 2026

Does SOC 2 require a penetration test?

The Trust Services Criteria address identifying vulnerabilities and monitoring security anomalies, including CC7.1 and CC7.2. Testing may help demonstrate those controls, alongside configuration review, monitoring and remediation. Do not assume every auditor accepts the same automated report—or that the absence of one particular test automatically causes a qualification.

Ask your auditor which controls need testing evidence, what systems are in scope and what independence or competence they expect from the tester. A SOC 2 examination is performed by a qualified CPA service auditor; a scanner cannot issue a SOC 2 report.

Agree timing and coverage before commissioning work

An annual test plus reassessment after significant changes is a common planning approach, not a universal SOC 2 rule. For Type II, discuss whether the evidence and follow-up demonstrate operation during the observation period. Define how ongoing vulnerability reviews and incident monitoring complement point-in-time tests.

  • In-scope applications, APIs, infrastructure and account roles.
  • Testing window, production safeguards and prohibited actions.
  • Expected methodology, deliverables and tester qualifications.
  • Remediation owners, deadlines and retest evidence.

What useful testing evidence contains

An auditor-ready record should make coverage and exceptions visible
RecordWhy it matters
Scope and authorisationShows which targets, roles and methods were approved.
Method and coverageExplains tests that ran, exclusions, failures and technical limits.
Findings and evidenceSupports reproducible impact, affected resources, severity and confidence.
Remediation recordConnects each issue to an owner, action and risk decision.
Retest and residual riskShows whether the same behaviour remains after the fix.
Dates and provenanceLinks records to the relevant period and preserves integrity.

If your auditor needs CVSS, a signed assessor statement or a particular test format, agree it first. Do not relabel Raksha’s own severity or score as a CVSS assessment.

SOC 2, PCI DSS and ISO 27001 are not interchangeable

SOC 2 evaluates controls against selected Trust Services Criteria. ISO/IEC 27001 evaluates an information security management system and its risk treatment. Neither can be reduced to possession of one pentest report.

PCI DSS v4.0.1 has explicit penetration-testing requirements in Requirement 11.4, including internal and external testing at least every 12 months and after significant changes within applicable scope. Vulnerability scanning has separate requirements. Confirm applicability and qualifications with your assessor; Raksha is not presented as an Approved Scanning Vendor service.

What Raksha provides—and what it does not

Raksha supports evidence-graded findings, scoped guided or autonomous runs where entitled, compliance mappings, retention and exportable auditor packs. Coverage and access depend on the workspace’s current entitlements and supported runtime checks.

Packs organise evidence against controls. They are not a certification, an audit opinion or a guarantee that automated testing meets your auditor’s requirements. Human-led workflow testing may still be needed.

Compare a scan, an automated run and a human-led assessment

Can an internal team test?

Discuss competence, independence and evidence expectations with your auditor. Do not assume an internal scan or external vendor is automatically sufficient.

Sources and further reading

Consult current official documentation before changing a production system. Examples are illustrative, not live findings or universal configurations.

Start with a site you are authorised to test

A free passive check needs no card. Sign-in, email confirmation, ownership rules and usage limits apply. It is not an unrestricted penetration test.