Home Vooki Pro Features Pricing About Contact
Compliance / ISO/IEC 27001

ISO/IEC 27001 vulnerability management: Annex A.8.8, explained

ISO/IEC 27001:2022 names technical vulnerability management as its own Annex A control — A.8.8. Here's where it sits in the standard's structure, what it actually asks for, and how Vooki Pro's scans and reports give you evidence for it, without claiming to certify anything on their own.

"Start 7-Day Trial" submits a request — Vooki Pro's team reviews it and sends the trial license and installation instructions; it is not an instant self-serve activation.

The requirement

What A.8.8 actually covers

A.8.8 — Management of technical vulnerabilities

Sits in the Technological theme of the 2022 revision's 93 Annex A controls (reorganized from the 2013 edition's 114 controls into four themes: Organizational, People, Physical, Technological). The control's aim is identifying exposure to known technical weaknesses and responding to them — commonly described as covering discovery, assessment, prioritization, remediation, and verification.

No prescribed method or cadence

Like most Annex A controls, A.8.8 states an objective, not an implementation. Your Statement of Applicability and risk treatment plan — the documents your certification auditor actually reviews — define how often you scan and what tooling you use to satisfy it, within your organization's own ISMS.

The ISO/IEC 27001:2022 standard text itself is a paid, licensed document (iso.org) and was not directly reproduced here — this summary is paraphrased from secondary ISO 27001 implementation guides, cross-checked across multiple sources, not quoted verbatim from the standard. Confirm exact wording against the licensed standard for an actual audit.

Where Vooki Pro fits

How Vooki Pro supports A.8.8

What it covers

Scheduled scans provide the ongoing "identification" half of the control for your web applications and REST APIs; the CVSS score and severity on each finding support prioritization; automated retest and the fixed/false-positive triage states provide the remediation-and-verification evidence an auditor would look for in your vulnerability management records.

What it doesn't cover

A.8.8 is one of 93 Annex A controls spanning everything from access control to supplier relationships to physical security. ISO 27001 certification requires a full ISMS audit by an accredited certification body — a DAST tool's output is evidence for one control, not a substitute for the management system or the certification process.

The ISO 27001 compliance report

Exporting a scan as an ISO/IEC 27001-mapped report (HTML or PDF, via the Export menu or the CLI's compliance_framework: iso27001 config) gives your ISMS documentation a dated, reproducible artifact for the technical-vulnerability-management control.

FAQ

Common questions

Which ISO 27001 control covers vulnerability scanning?
Annex A.8.8, "Management of technical vulnerabilities," in the 2022 revision's Technological theme — one of 93 Annex A controls. The 2013 version covered similar ground under A.12.6.1. The control is about identifying and responding to known weaknesses; it does not prescribe a specific tool or scan frequency.
Does Vooki Pro generate an ISO 27001 compliance report?
Yes — scan findings can be exported as a report mapped to ISO/IEC 27001, in HTML or PDF, as evidence for your ISMS's technical vulnerability management control.
Does using Vooki Pro make us ISO 27001 certified?
No. ISO 27001 certification is granted by an accredited certification body after an audit of your entire Information Security Management System (ISMS) — A.8.8 is one of 93 Annex A controls, and vulnerability scanning evidence supports that one control, not certification as a whole.

Sources

ISO/IEC 27001:2022 (official standard page, iso.org)
Secondary ISO 27001 implementation guides cross-checked for A.8.8's control number and theme (not individually linked — the standard text itself is paywalled, so none of them substitute as a primary source).
Vooki Pro: live features.html, docs/reports.html, docs/cli.html, docs/findings.html (verified 2026-10-23).

Unverified, explicitly not claimed: the exact clause wording of Annex A.8.8 (paraphrased from secondary sources, standard itself is paywalled); specific remediation-timeframe language sometimes attributed to A.8.8 by third-party sites — not confirmed against the standard and left out of this page.

Document vulnerability management for your ISMS

No credit card required — submit a request and the team will send your trial license and installation instructions.

This site uses cookies to enhance user experience. See Privacy Policy