A.8 Technological controls

A.8.8 Management of technical vulnerabilities

Not mandatory by default – decided in your SoA

What it means in plain language

Find technical vulnerabilities in your systems, evaluate the exposure and fix them in time.

Is it mandatory? Not automatically. You must consider this control in your Statement of Applicability (6.1.3 d). Include it if your risk assessment, laws, contracts or business needs require it; if you exclude it, write down a justification an auditor will accept.

Why this control matters

Teams should turn the Vulnerability Management Procedure and Vulnerability Register into a working decision trail. Emphasize how discovery, prioritization, remediation, and verification connect across infrastructure, applications, and externally exposed assets. A frequent weakness is a register that lists findings without ownership, due dates, compensating measures, or closure evidence, which leaves risk treatment incomplete and hard to explain during review.

Common auditor findings to check for

Potential gaps to test in your own environment, not a claim about observed audit frequency.

  • Monthly scans run, but the register does not show asset ownership, exposure rating, or whether findings affect internet-facing systems versus internal-only assets.
  • Critical patches are applied inconsistently; some remediation dates slip without documented risk acceptance, temporary safeguards, or management review of overdue items.
  • External testing is performed, but retest evidence is missing, so resolved items cannot be distinguished from recurring issues or partially fixed vulnerabilities.

How you can implement it

Tools and review intervals are examples; choose them according to risk, obligations and your operating environment.

  • Define a triage workflow owned by the vulnerability manager, with input from asset owners, infrastructure support, and application teams. Each finding should record asset name, exploitability, business impact, remediation target, and a decision on whether temporary mitigation is needed before patching. Use a single register to prevent findings from being lost across tools.
  • Set an illustrative cadence that matches risk: authenticated scans on a defined schedule, emergency scans after critical advisories, and periodic validation of remediation. Keep timing risk-based rather than rigid, and document why a finding was deferred, isolated, or accepted. This helps reviewers see controlled deviation rather than unmanaged backlog.
  • Track technical and compensating treatments together. If patching is delayed, note firewall rules, service shutdowns, configuration changes, or access restrictions that reduce exposure. Assign accountable owners for each action and require closure evidence such as patch versions, scan screenshots, or signed retest notes.
  • Maintain evidence that shows the lifecycle of a vulnerability: scan output, triage notes, register entries, remediation tickets, change records, and retest results. The register should reveal open, in progress, accepted, and closed states, with dates and approvers. This makes status transparent across management review and internal audit.

What an auditor will ask to see

  • Vulnerability Register entries with owner, risk rating, due date, and closure status.
  • Scan report and authenticated retest results for a critical server or application.
  • Patch or change ticket showing implementation and business approval for a deferred fix.
  • External test summary with documented remediation actions and verification notes.

Baseline documents in the kit

These free kit documents help you document or evidence A.8.8. Each one is tailored to your organization when you build your kit.

Connect this work to your ISMS

Review the dependencies with A.8.7 — Protection against malware and A.8.9 — Configuration management. Keep the ownership and evidence consistent across these activities.

NIS2 and ISO/IEC 27001: reuse controls and check legal gaps for the wider implementation context.

Use the SIG and CAIQ questionnaire accelerator to find supporting documents. A mapping is a starting point: verify your actual operating evidence before answering a buyer.

For help adapting this to your environment, explore ISO/IEC 27001 consulting, starting with a free one-hour consultation.

Get these documents tailored to your organization

109 ready-to-edit documents, including all 19 mandatory ones, tailored from a short scoping questionnaire and linked to your risk register and SoA.

Start free

Plain-language interpretation by an ISO/IEC 27001 lead implementer, not the official text of ISO/IEC 27001:2022.