Penetration testing for SOC 2 and ISO 27001

What the frameworks say, what auditors commonly expect, and when to schedule the test.

A tidy desk with a keyboard, phone and stationery, seen from above

SOC 2

The AICPA Trust Services Criteria do not name penetration testing as a mandatory control. Penetration testing appears as one example of how an organisation can evaluate its controls. In practice many auditors expect independent testing as evidence, so most companies include one. Ask your auditor what evidence they expect for your report.

ISO/IEC 27001:2022

ISO 27001 does not require a penetration test by name either. Annex A controls such as 8.8 (management of technical vulnerabilities) and 8.29 (security testing in development and acceptance) ask you to find and handle weaknesses. A penetration test is a common way to show those controls work. ESCOSS itself is certified to ISO/IEC 27001:2022.

When to test

Test early enough to fix and retest high findings before your audit window closes. For a first SOC 2 Type II period, that usually means testing near the start of the period, not the end.

One test, several frameworks

A single well-scoped test can support SOC 2, ISO 27001 and customer questionnaires at the same time. Tell us every framework in the proposal request so the scope covers all of them.

Sources

General guidance, not legal, audit or compliance advice. Confirm requirements with your auditor or assessor.

Need this done?

Tell us what needs testing and when. We reply within 1 business day.

Request a proposal
Ready to test?

Tell us what needs testing and by when.

You receive a written proposal with scope, method, timeline and a fixed price. We reply within 1 business day.