1. Home
  2. Solutions
  3. ISO 27001

Solutions · Compliance · ISO 27001

ISO 27001 penetration testing mapped to the Annex A controls your auditor samples

ISO 27001 compliance means showing your ISMS controls work, not just that they exist. ioSENTRIX tests your applications, cloud and networks like an attacker, maps every finding to ISO/IEC 27001:2022 Annex A, and includes a retest of your fixes so the evidence is ready for certification and surveillance audits.

StandardISO/IEC 27001:2022 · Annex A controls 8.8 and 8.29
Who asksYour certification auditor, customers and their vendor-risk teams
What you getProven findings, retest results and an Annex A mapping for your ISMS
Reviewed by Omair Manzoor, Founder & CEO, ioSENTRIX · Updated November 2026Key terms: ISO 27001, Penetration testing, Vulnerability assessment
Trusted by security teams at

01The requirement

Is penetration testing required for ISO 27001?

Not by name. No Annex A control in ISO/IEC 27001:2022 mandates a penetration test. Testing evidence usually sits under control 8.8 (management of technical vulnerabilities) and 8.29 (security testing in development and acceptance), and it gives your clause 6.1.2 risk assessment proof of what is actually exploitable.

Mandatory?No control says "pentest"

Your risk assessment and Statement of Applicability decide which controls apply and how.

Expected?Direct evidence for 8.8 and 8.29

A pentest shows whether vulnerability management and security testing work in practice.

CycleBefore stage 2, then each year

Test ahead of certification, within each surveillance year and after significant change.

What is ISO 27001 penetration testing?

ISO 27001 penetration testing is a penetration test scoped to the systems inside your ISMS scope, documented so that findings, remediation and the retest can be presented as evidence for the Annex A controls your Statement of Applicability includes.

What does ISO 27001 compliance require?

An information security management system: a defined scope, a risk assessment and treatment process, controls selected against Annex A, and evidence that they operate, checked by an accredited certification body. Compare frameworks in SOC 2 vs ISO 27001.

02See it in action

From control to ISMS evidence

How control 8.8 is tested like an attacker would, a proven weakness is patched and retested, and the result goes into your ISMS evidence.

A control, not a scan

We start from the Annex A control in your Statement of Applicability and test whether it holds against a real attacker, so the result answers the auditor's question directly.

Risk your assessment can use

Each finding carries evidence, likelihood and impact, ready to feed your clause 6.1.2 risk assessment and treatment plan.

Treated, then confirmed

A retest of your fixes is included, so your ISMS records each risk as found, treated and confirmed.

Illustrative example. The service, flaw and statuses are a composite for explanation only and do not describe any client. Exploitation uses safe, agreed methods set in the rules of engagement.

Text version of the exhibit
  1. Control: your Statement of Applicability includes Annex A control 8.8, management of technical vulnerabilities. The test also supports clause 6.1.2, 8.20 networks security and 5.35 independent review.
  2. Test: external testing maps your exposed services and their versions.
  3. Finding: an internet-facing file transfer service has a known, publicly exploited flaw, and testers prove it can be exploited on an agreed, safe test path. The finding is rated Critical.
  4. Fix: we describe the patch, exposure reduction and monitoring for your team, linked to 8.29 security testing.
  5. Retest: the exploit no longer works and the patch is confirmed.
  6. Evidence: the folder (scope, finding with proof, treatment, retest and Annex A mapping) is filed in your ISMS as evidence for 8.8.

03Requirement to evidence

How does penetration testing map to ISO 27001 Annex A?

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

Clause or controlWhat it coversWhat ioSENTRIX testsEvidence for your auditor
Clause 6.1.2Information security risk assessmentIdentifying, analyzing and evaluating information security risks.Threat modeling and testing that shows which risks are exploitable.Risk-ranked findings with likelihood and impact
8.8Management of technical vulnerabilitiesGetting information about technical vulnerabilities, evaluating exposure and taking appropriate measures.External and internal penetration testing and manual validation of your scanner's results.Proven vulnerabilities, treatment and retest
8.29Security testing in development and acceptanceSecurity testing processes defined and implemented in the development life cycle.Web app and API testing before release, or PTaaS for frequent releases.Pre-release test results and retests
8.20Networks securityNetworks and network devices secured, managed and controlled to protect information.Network penetration testing, segmentation and exposed-service review.Network findings and exposed services list
8.25Secure development life cycleRules for the secure development of software and systems established and applied.Architecture review, secure code review and application security support.Design and code review findings
5.35Independent review of information securityThe approach to managing information security reviewed independently at planned intervals or after significant changes.An independent, third-party test of the controls in scope.Report with scope, dates, method and testers

Control numbers and titles follow ISO/IEC 27001:2022 Annex A (aligned with ISO/IEC 27002:2022); descriptions are summaries, not the standard's text. Your certification body decides what evidence is sufficient. ioSENTRIX does not issue ISO certificates.

04Timing

When should you run an ISO 27001 penetration test?

Early enough to treat and retest before the auditor samples your controls, then once in every year of the certification cycle.

  1. Risk assessment

    Scope the ISMS, assess risks and select Annex A controls.

    Statement of Applicability
  2. Test and retest

    Pentest the systems in scope, fix, then retest. A web application test typically takes 1–2 weeks.

    Retest included
  3. Stage 1

    The certification body reviews your ISMS documentation and readiness.

    Readiness
  4. Stage 2

    The auditor samples controls such as 8.8 and 8.29 and their evidence.

    Evidence pack
  5. Surveillance years 1 and 2

    Annual surveillance audits: a new test each year and after significant change.

    Annual test
  6. Recertification

    At the end of the three-year cycle, a full recertification audit.

    Next cycle
Initial certificationTest before stage 2

Findings fixed and retested before the stage 2 audit, so the auditor sees a working vulnerability management process.

Surveillance yearsShow the control keeps operating

A test within each year, plus retests after significant changes, keeps 8.8 and 8.29 evidence current for every surveillance audit.

05Evidence pack

What's in an ISO 27001 penetration test evidence pack?

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

  1. Executive summary

    Scope, method and results in plain language for management review.

  2. Scope and method

    Systems in your ISMS scope, dates, testers and the standards followed.

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

    Each finding with evidence, likelihood, impact and steps to reproduce, ready for your risk register.

  4. Treatment guidance

    Specific remediation for your engineers, prioritized for your risk treatment plan.

  5. Retest results

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

  6. Annex A mapping

    Each result mapped to the clause or control it supports.

    6.1.28.88.208.258.295.35

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 ISO 27001 test

09FAQ

ISO 27001 penetration testing questions

Short answers to what ISMS owners and auditors ask us most.

Ask us something else

Is penetration testing required for ISO 27001?

Not by name. No ISO/IEC 27001:2022 Annex A control mandates a penetration test. Testing evidence usually sits under control 8.8 (management of technical vulnerabilities) and 8.29 (security testing in development and acceptance), and it feeds the information security risk assessment in clause 6.1.2. Whether you test, and how often, follows from your risk assessment and Statement of Applicability.

Which ISO 27001 controls does a penetration test support?

Most directly 8.8 (management of technical vulnerabilities) and 8.29 (security testing in development and acceptance). Depending on scope it also supports 8.20 (networks security), 8.25 (secure development life cycle) and 5.35 (independent review of information security), and gives your clause 6.1.2 risk assessment evidence of real, exploitable risk.

What happened to ISO 27001 control A.12.6.1?

In ISO/IEC 27001:2013, technical vulnerability management was control A.12.6.1. In the 2022 edition it became Annex A control 8.8, management of technical vulnerabilities. System security testing and acceptance testing (A.14.2.8 and A.14.2.9) were merged into 8.29, security testing in development and acceptance.

When should we run a penetration test in the ISO 27001 certification cycle?

Before your stage 2 audit, so findings are fixed and retested by the time the auditor samples 8.8 and 8.29, and again within each surveillance year and after significant changes. A certificate is valid for three years, with surveillance audits in between and a recertification audit at the end.

Does ioSENTRIX issue ISO 27001 certificates?

No. ISO/IEC 27001 certificates are issued by certification bodies after a certification audit. ioSENTRIX provides the testing, evidence and readiness support, and is itself ISO/IEC 27001 certified.

Is a vulnerability scan enough for ISO 27001?

It can be part of your 8.8 process, but it is not the same evidence. A vulnerability scan lists known weaknesses automatically. A penetration test is carried out by people who exploit and chain weaknesses and prove the impact, which shows whether your vulnerability management actually works.

How long does an ISO 27001 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 ahead of your audit.

Ready when you are

Get ISO 27001 evidence your auditor can sample

Tell us where you are in the certification cycle and what is in your ISMS scope. We will help you scope the right test and plan it ahead of your audit.

  • Written scope and timeline before testing starts
  • Retest of fixes included
  • Report mapped to ISO/IEC 27001:2022 Annex A
Scope your ISO 27001 penetration test

Takes about a minute.