Guide
ISO 27001 and penetration testing
ISO/IEC 27001:2022 never says “penetration test”, but certification auditors ask about them all the time. This is which controls a pentest supports, what the auditor checks, and the evidence to keep.
Updated 11 November 2026 · By the Closeout team
Does ISO 27001 require a penetration test?
No. ISO/IEC 27001:2022 is risk-based: it requires you to manage technical vulnerabilities and to test security, but leaves the method and frequency to your risk assessment. A penetration test is the most common way to show those controls work, and for internet-facing systems an auditor will usually expect one. The transition from the 2013 version ended on 31 October 2025, so certificates now use the 2022 control numbers.
The Annex A controls a pentest supports
| Control | What it asks | Where the pentest fits |
|---|---|---|
| 8.8 Management of technical vulnerabilities | Get information about technical vulnerabilities, evaluate your exposure and take appropriate measures | Finds vulnerabilities scanners miss and shows real exposure |
| 8.29 Security testing in development and acceptance | Define and carry out security testing in the development life cycle | Testing before a release or major change goes live |
| 5.35 Independent review of information security | Review the approach to information security independently, at planned intervals or after significant change | An external test is independent evidence |
Outside Annex A, clause 9.1 asks you to monitor and measure how effective your security is, and clause 10.2 asks you to act on nonconformities. Pentest findings and their remediation feed both.
What the certification auditor checks
- That your risk assessment and statement of applicability explain why you test what you test, and how often.
- That testing actually happened as planned, by someone competent and independent of the system.
- That findings went into your risk treatment: fixed by a date, or formally accepted.
- That fixes were verified, not just closed.
Evidence to keep
- The report, with scope, dates, methodology, who tested and every finding with its severity.
- The remediation record: owner, due date and status of each finding, with dates.
- The retest, which proves each fix works, not just that someone marked it done. See our guide to pentest retesting.
- Accepted risks, in writing, by someone with the authority, with a reason and a review date.
- An attestation letter if the client must show the result to third parties without sharing the full report. You can make one with the attestation letter generator.
Sources
Official texts, checked in November 2026. This is a practical guide, not legal or audit advice.
Frequently asked questions
Is a penetration test mandatory for ISO 27001?
No. ISO/IEC 27001:2022 doesn't mention penetration testing. It requires technical vulnerability management (Annex A 8.8) and security testing (8.29), and a pentest is the usual way to show they work.
How often should an ISO 27001 company run a pentest?
The standard leaves it to your risk assessment. Annually and after significant changes is the common practice auditors accept.
Which ISO 27001 control covers penetration testing?
Mainly 8.8, management of technical vulnerabilities, and 8.29, security testing in development and acceptance. An external test also supports 5.35, independent review.