Skip to content
Technological controls
ISO 27001A.8.8

ISO 27001 Annex A 8.8 Management of technical vulnerabilities

What it says

Information about technical vulnerabilities of information systems in use shall be obtained, the organization's exposure to such vulnerabilities shall be evaluated and appropriate measures shall be taken.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

Obtain information about technical vulnerabilities of information systems in use, evaluate your organisation's exposure to them and take appropriate measures.

Your organisation must do three things about technical vulnerabilities, meaning weaknesses an attacker could use, in information systems in use:

  • Obtain information about the vulnerabilities that affect those systems.
  • Evaluate exposure, meaning whether each one affects your organisation and how seriously.
  • Take appropriate measures, such as updating the system or applying another control.

The control sets no time limit, so your organisation decides what is appropriate and how quickly to act, based on its risks and context.

Why it matters

Attackers exploit published flaws in software that nobody had tracked or assessed. Knowing which flaws affect your systems, and dealing with the highest risks first, shortens the time they stay open to attack.

How to implement

  1. List your software and systems, with versions and owners.

    Extend the asset inventory (Annex A 5.9) to show vendor, product, version, where it is installed and who is responsible. Add third-party libraries in software you build. For each bought or cloud service, record which parts the provider handles and which are yours, such as configuration and accounts.

  2. Obtain vulnerability information from several sources.

    Subscribe to vendor security advisories and public alert services that match your list. Run a vulnerability scanner suited to your technologies, and commission penetration tests (authorised, planned attacks) where the risk justifies them. Publish a security contact so outsiders can report problems.

  3. Evaluate your exposure to each finding.

    Check whether the affected version is in use, whether it can be reached and whether other controls already shield it, because scanners can over-report. Rate the risk by severity and how critical the system is. Set your own response time for each rating, since the control sets none.

  4. Apply updates, highest risk first.

    Use only legitimate sources. Weigh the risk of installing against the risk of waiting, test where you can and follow change management (Annex A 8.32). Handle urgent cases through your incident procedures (Annex A 5.26). Decide whether automatic updates suit each product. Re-scan to confirm the fix worked.

  5. Use another measure where no update is possible.

    Apply the vendor's workaround, turn off the affected service, tighten network access, filter traffic or increase monitoring. Where a provider controls the fix, ask for its plan, follow its security notices and, where you can change the agreement, add its vulnerability duties (Annex A 5.20). Record who accepted any remaining risk.

Keep it running

An unlisted system gets no alerts, so update the inventory and sources as software changes. Look again when a serious flaw is announced, a new system or service goes live, or a re-scan shows a fix failed.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    The software and systems inventory, compared with a discovery scan and the list of cloud subscriptions.

    Look at

    Anything found by the scan or in the subscriptions that is missing from the inventory or outside scanner and advisory coverage.

    Good evidence

    Every system found in use is listed with its version and owner, and is covered by a scanner or an advisory source.

  2. Check 2 of 5What an auditor asks for

    Ask for

    The records for a serious vulnerability the auditor picks from recent public advisories for products on the inventory.

    Look at

    Whether the organisation learned of it, worked out which systems were affected and rated the risk using its own method.

    Good evidence

    A dated record shows the systems affected, or a reasoned finding of no exposure, along with the risk rating and decision.

  3. Check 3 of 5What an auditor asks for

    Ask for

    A sample of closed findings, with their change records and a fresh scan.

    Look at

    Whether the measure was really applied, whether the highest risks were handled first, and the time taken against the organisation's own response times.

    Good evidence

    The fresh scan no longer shows the sampled vulnerabilities, or the other measure taken is shown working, and each was closed within the time set for its rating.

  4. Check 4 of 5What an auditor asks for

    Ask for

    Open vulnerabilities past their response time, with the measures and decisions for each.

    Look at

    Whether another measure is actually in place, and whether someone accountable accepted the remaining risk.

    Good evidence

    Each overdue item has a working alternative measure or a recorded risk decision by a named person, and none is simply left open.

  5. Check 5 of 5What an auditor asks for

    Ask for

    The responsibility split and security notices for a sample of bought services.

    Look at

    Whether it is written down who handles vulnerabilities in which part, and whether items on your side have been dealt with.

    Good evidence

    The split is written down, provider notices reach a named person, and the items on your side have been assessed and acted on.

Mappings

Closest match in ASD Essential Eight: E8-AC-ML3.3, Microsoft's vulnerable driver blocklist is implemented, which this control covers in full and more.

Essential Eight

ASD Essential Eight: 23 mappings

ASD ISM

ASD Information Security Manual: 56 mappings

ASD Essentials

ASD Essentials for enterprise IT: 6 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.

Get help with this control

ISO 27001 training

Mindset Cyber, a PECB Authorised Titanium Partner, sells official PECB ISO/IEC 27001 courses that map directly to the controls in this library.