Skip to content

Trusted across the UK, USA, EU & India - 24/7 incident response.

VAPT for ISO 27001 certification

ISO 27001:2022 Annex A control A.8.8 requires organisations to obtain timely information about technical vulnerabilities and take appropriate action. For most organisations, the standard of evidence a stage 2 auditor accepts is a manual penetration test report with CVSS scores, exploited proof-of-concept findings and a remediation tracking record. IntelligenceX delivers engagements structured to meet this standard.

Remote delivery
Regulator-aligned report
Free retest included
Signed attestation
Security testing and assessment

What A.8.8 requires

ISO 27001:2022 Annex A control A.8.8 (management of technical vulnerabilities) replaces A.12.6.1 from the 2013 version. The control requires organisations to identify technical vulnerabilities in their systems, evaluate the exposure created by those vulnerabilities, and take appropriate action to address them. The associated guidance in ISO 27002:2022 explicitly references penetration testing as one mechanism for satisfying this control.

There is no mandated frequency in the standard, but the expectation of most stage 2 auditors and certification bodies is annual penetration testing at minimum, with testing after significant infrastructure changes. An automated vulnerability scan alone does not satisfy A.8.8 — the control requires evidence of management, not just identification.

  • Identify technical vulnerabilities across systems in the ISMS scope
  • Evaluate exposure and take action proportionate to the risk
  • Testing frequency: annual at minimum, more after significant changes
  • Evidence required: test report with CVSS scores, remediation tracking, retest confirmation

What the stage 2 auditor looks for

ISO 27001 stage 2 auditors review VAPT evidence during certification and surveillance audits. The document package that satisfies A.8.8 without additional questions consists of the following.

  • Signed VAPT report with scope matching the ISMS boundary
  • CVSS v3.1 scores and finding severity classification
  • Proof-of-concept evidence for critical and high findings (confirms manual testing, not scan only)
  • Remediation tracking log with dates and responsible owner
  • Retest confirmation letter confirming critical and high findings closed
  • Evidence that the test covered production or a representative pre-production environment

Scope: matching the ISMS boundary

The most common A.8.8 gap finding in ISO 27001 audits is a VAPT scope that is narrower than the ISMS scope. If your certification covers your cloud environment, all application tiers and your internal network, the VAPT must cover all three — not just the customer-facing application.

We review your ISMS scope document before agreeing the testing scope, so the two are aligned and there are no surprises at the audit.

  • All applications within the ISMS scope (web, API, mobile)
  • Cloud infrastructure hosting ISMS-scoped systems (AWS, Azure, GCP)
  • Internal network and Active Directory where in ISMS scope
  • Third-party integrations that process ISMS-scoped data

Delivery timeline for certification audits

ISO 27001 stage 2 audits have fixed dates. We work backward from your audit date to deliver a complete evidence package — test, remediation, retest confirmation — with time to spare.

  • Minimum recommended lead time: 10 weeks before stage 2 audit
  • Testing window: 3–8 business days depending on scope
  • Remediation period: 4–6 weeks for critical and high findings
  • Retest and confirmation letter: within 2 weeks of remediation
  • Final attestation letter for auditor submission: at retest completion

Frequently asked questions

An automated vulnerability scan does not satisfy A.8.8 on its own. The control requires identification and management of technical vulnerabilities, and the associated guidance in ISO 27002 references penetration testing. Stage 2 auditors increasingly ask for exploited proof-of-concept evidence — something only a manual test provides — to confirm that vulnerabilities were actively verified rather than just listed by a tool.

The standard does not specify a frequency. The practical expectation, reflected in most auditor guidance and accreditation body guidance, is annual penetration testing. Surveillance audits (years 2 and 3 of a certification cycle) also typically require evidence of VAPT for the period. After significant infrastructure changes, additional testing is a reasonable documented response under A.8.8.

Yes. A single engagement scoped to cover all ISMS-scoped systems, with findings mapped to both CVSS and the relevant framework controls (RBI, SEBI, PCI DSS, SOC 2), satisfies multiple frameworks simultaneously. This is the most cost-efficient approach for organisations with overlapping compliance obligations.

Early disclosure is built into our process — we alert you to critical findings within 24 hours of discovery, well before the full report. This gives your development team maximum remediation time. For stage 2 audits with a tight timeline, we can agree an accelerated retest process. An auditor finding a critical issue in your report is not automatically a failure — evidence of a clear remediation plan and retest confirmation is typically sufficient.

Talk to a security expert today

A penetration test, an audit, or 24/7 monitoring, our team is ready across the UK, USA, EU and India.