Annex A 8.8
Management of technical vulnerabilities
Information about technical vulnerabilities is obtained, exposure evaluated, and appropriate measures taken.
What an assessor looks for
Show the scanning cadence, how findings are prioritised, and remediation against your own service levels. Overdue critical vulnerabilities need a documented risk acceptance.
Where it usually fails
Scanning runs reliably and remediation service levels are routinely breached without exception records.
Classification
- Theme
- A.8 Technological
- Control type
- Preventive, Detective
- Security properties
- Confidentiality, Integrity, Availability
- Cybersecurity concepts
- Identify, Protect
- ISO 27001:2013 equivalent
- 12.6.1, 18.2.3
Control number and title are identifiers used as references. The classification above is our own analysis, aligned to the shape of the ISO 27002 attribute model rather than reproduced from it, and no text from the standard appears on this page. Last reviewed 2026-08-03.
Building the Statement of Applicability?
Record your applicability decision for this control and the other 92 in the browser-based builder. Nothing is transmitted, and you export the file at the end.
Open the SoA builder