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.
What it means
In plain EnglishObtain 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.
Free. Save your status, tasks and notes.
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
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.
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.
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.
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.
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
- 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.
- 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.
- 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.
- 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.
- 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.
ASD Essential Eight: 23 mappings
This control is broader than E8-AC-ML3.3.
E8-AC-ML3.3 requires a specific measure: enabling Microsoft's vulnerable driver blocklist to reduce exposure to driver vulnerabilities. ISO/IEC 27001:2022 Annex A 8.8 requires obtaining information about technical vulnerabilities, evaluating exposure, and applying appropriate measures across information systems generally. E8-AC-ML3.3 is a concrete technical implementation that can be selected as one 'appropriate measure' under Annex A 8.8, but Annex A 8.8 is much broader in scope and method.
This control is broader than E8-AH-ML1.1.
E8-AH-ML1.1 requires Internet Explorer 11 to be disabled or removed to reduce known and future technical vulnerability exposure. This supports Annex A 8.8 by acting as an appropriate measure to treat exposure once an organisation has identified IE11 as a technical vulnerability/unsupported component in use. Annex A 8.8 is a broader vulnerability management requirement (identify, evaluate, treat), while E8-AH-ML1.1 is a specific treatment action for one high-risk software component.
This control is broader than E8-PA-ML1.2.
E8-PA-ML1.2 requires using a vulnerability scanner with an up-to-date vulnerability database for scanning activities. Annex A 8.8 is broader, requiring organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures, of which using an up-to-date scanner is one practical method. Annex A 8.8 extends beyond scanning to include evaluation and treatment activities that E8-PA-ML1.2 does not cover.
This control is broader than E8-PA-ML1.3.
Annex A 8.8 requires organisations to obtain information on technical vulnerabilities, evaluate exposure and take appropriate measures to address them. E8-PA-ML1.3 supports this by requiring daily vulnerability scanning of online services for missing patches, strengthening the vulnerability information feed and enabling timely exposure assessment and remediation prioritisation. The Essential Eight control focuses on detection cadence for online services, while Annex A 8.8 covers the full vulnerability management lifecycle and broader system scope.
This control is broader than E8-PA-ML1.4.
E8-PA-ML1.4 requires organisations to use weekly vulnerability scanning to identify missing patches/updates for common end-user software and security products. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures. E8-PA-ML1.4 supports Annex A 8.8 by operationalising one way to identify vulnerability exposure (missing patches) on a recurring basis, although Annex A 8.8 is broader and not limited to scanning or specific software classes.
This control is broader than E8-PA-ML1.5.
E8-PA-ML1.5 requires organisations to remediate critical online-service vulnerabilities by applying patches or mitigations within 48 hours. Annex A 8.8 requires obtaining information about technical vulnerabilities, evaluating exposure, and taking appropriate measures, which includes but is not limited to patching. E8-PA-ML1.5 is a concrete, time-bound implementation for a high-risk subset of vulnerability treatment covered more broadly by Annex A 8.8.
This control is broader than E8-PA-ML1.6.
E8-PA-ML1.6 requires non-critical vendor patches for online services be applied within two weeks when no working exploits exist. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures, which fits the vulnerability management within E8-PA-ML1.6's prescriptive, time-bound implementation.
This control is broader than E8-PA-ML1.7.
ISO/IEC 27001:2022 Annex A 8.8 requires an organisation to obtain information about technical vulnerabilities in its information systems, evaluate its exposure and take appropriate measures. E8-PA-ML1.7 is a specific measure within that scope, requiring vendor patches or mitigations for office productivity suites, web browsers and their extensions, email clients, PDF software and security products to be applied within two weeks of release.
This control is broader than E8-PA-ML2.2.
E8-PA-ML2.2 requires organisations to remediate vulnerabilities in certain non-critical applications by applying patches/mitigations within one month of release. ISO/IEC 27001:2022 Annex A 8.8 is broader, requiring organisations to obtain information about technical vulnerabilities, assess exposure, and take appropriate measures across information systems in use. E8-PA-ML2.2 is a specific, time-bound treatment measure within the wider vulnerability management expectations of Annex A 8.8.
This control is broader than E8-PA-ML3.1.
E8-PA-ML3.1 requires obtaining and applying vendor mitigations within 48 hours for critical or exploited vulnerabilities in nominated high-risk application categories. Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures across information systems generally. E8-PA-ML3.1 is a prescriptive, time-bound implementation for a specific application set within the broader vulnerability management expectation in Annex A 8.8.
This control is broader than E8-PA-ML3.2.
E8-PA-ML3.2 mandates a two-week patching timeframe for non-critical vulnerabilities in specific high-risk applications. Annex A 8.8 requires organisations to address technical vulnerabilities generally, typically involving patching. E8-PA-ML3.2 is a more prescriptive subset with explicit scope and conditions.
This control is broader than E8-PO-ML1.3.
E8-PO-ML1.3 requires a specific practice: daily vulnerability scanning to identify missing OS patches/updates on internet-facing servers and internet-facing network devices. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures, without prescribing scanning frequency or limiting scope to internet-facing infrastructure. E8-PO-ML1.3 is a concrete implementation approach that fits within the broader vulnerability management expectations of Annex A 8.8.
This control is broader than E8-PO-ML1.4.
E8-PO-ML1.4 requires fortnightly vulnerability scanning to identify missing OS patches on internal systems. ISO/IEC 27001:2022 Annex A 8.8 requires the organisation to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures, which can be implemented using vulnerability scanning and patch identification. Annex A 8.8 is broader and risk-oriented and does not prescribe a fortnightly cadence or limit scope to operating system patch status.
This control is broader than E8-PO-ML1.5.
E8-PO-ML1.5 requires organisations to apply critical patches within 48 hours for operating systems on internet-facing servers and internet-facing network devices when critical or exploited. ISO/IEC 27001:2022 Annex A 8.8 requires obtaining information about technical vulnerabilities, evaluating exposure, and taking appropriate measures, which encompasses patching as one possible treatment. E8-PO-ML1.5 is a prescriptive, time-bound subset of the broader vulnerability management expectation in Annex A 8.8.
- E8-PO-ML1.7One-month operating system patching for workstations, non-internet-facing servers and network devicesBroader than
This control is broader than E8-PO-ML1.7.
ISO/IEC 27001 Annex A 8.8 requires an organisation to obtain information about technical vulnerabilities, evaluate its exposure and take appropriate measures, while E8-PO-ML1.7 is one specific measure within that scope: applying vendor patches or mitigations for operating system vulnerabilities on workstations, non-internet-facing servers and non-internet-facing network devices within one month of release.
This control is broader than E8-PO-ML3.1.
E8-PO-ML3.1 focuses on using a vulnerability scanner at least fortnightly to identify missing driver patches or updates. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures across information systems generally. E8-PO-ML3.1 is one concrete, driver-specific detection activity that fits within the broader vulnerability identification and treatment expectations of Annex A 8.8.
This control is broader than E8-PO-ML3.2.
E8-PO-ML3.2 requires organisations to conduct at least fortnightly vulnerability scanning specifically to identify missing firmware patches or updates. ISO/IEC 27001:2022 Annex A 8.8 is broader, requiring organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures across information systems generally. E8-PO-ML3.2 is a specific, prescriptive method (fortnightly scanning for firmware) that can be used to meet part of Annex A 8.8's broader vulnerability management expectations.
This control is broader than E8-PO-ML3.3.
E8-PO-ML3.3 requires organisations to apply critical operating system patches to non-internet-facing workstations, servers and network devices within 48 hours when vendor criticality or working exploits are present. Annex A 8.8 requires obtaining information about technical vulnerabilities, evaluating exposure, and taking appropriate measures, which encompasses patching as one treatment option. E8-PO-ML3.3 is a prescriptive subset of Annex A 8.8, adding explicit scope (OS on internal assets) and a defined remediation timeframe (48 hours).
This control is broader than E8-PO-ML3.4.
E8-PO-ML3.4 requires a specific operational treatment of technical vulnerabilities: applying non-critical OS patches within one month for defined internal asset classes when no working exploits exist. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures, but it does not prescribe specific patching timeframes or the exact asset scope. E8-PO-ML3.4 is therefore a concrete, time-bound implementation subset of the broader vulnerability management expectations in Annex A 8.8.
This control is broader than E8-PO-ML3.5.
E8-PO-ML3.5 requires a specific vulnerability treatment action: apply critical driver patches (or mitigations) within 48 hours when rated critical or exploited. Annex A 8.8 requires the organisation to obtain information about technical vulnerabilities, evaluate exposure and take appropriate measures, which includes patching as one possible measure. E8-PO-ML3.5 is a prescriptive subset of Annex A 8.8, with tighter scope (drivers) and a defined timeframe.
This control is broader than E8-PO-ML3.6.
E8-PO-ML3.6 requires organisations to apply non-critical driver patches within one month when no working exploits exist. ISO/IEC 27001:2022 Annex A 8.8 requires obtaining information about technical vulnerabilities, evaluating exposure, and taking appropriate measures, which commonly includes patching as a treatment. E8-PO-ML3.6 is a prescriptive subset of Annex A 8.8 focused on a specific asset class (drivers) and a defined remediation window under defined conditions.
- E8-PO-ML3.8Firmware vulnerabilities patched within one month if non-critical and no exploitsBroader than
This control is broader than E8-PO-ML3.8.
E8-PO-ML3.8 requires a specific action: apply vendor mitigations for non-critical firmware vulnerabilities within one month when no working exploits exist. Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures across information systems generally. E8-PO-ML3.8 is a concrete, narrowly scoped implementation (firmware, defined conditions, defined timeframe) that fits within the broader vulnerability management expectations of Annex A 8.8.
This control depends on E8-PA-ML1.1.
E8-PA-ML1.1 requires fortnightly automated asset discovery to identify assets for follow-on vulnerability scanning. Annex A 8.8 requires obtaining information about technical vulnerabilities, evaluating exposure and taking appropriate measures. E8-PA-ML1.1 supports Annex A 8.8 by helping ensure the organisation knows what systems exist so vulnerability information and exposure evaluations are complete, but Annex A 8.8 is broader and does not prescribe asset discovery or a fortnightly cadence.
ASD Information Security Manual: 56 mappings
This control is broader than ISM-0298.
ISM-0298 mandates centralised patch management with integrity and successful application verification. Annex A 8.8 requires organisations to evaluate and address technical vulnerabilities, of which patching is one treatment, making ISM-0298 a specific operational control within its broader scope.
This control is broader than ISM-0300.
Annex A 8.8 requires the organisation to obtain vulnerability information, assess exposure and apply appropriate treatments, including patching and updates. ISM-0300 prescribes a specific patching governance approach for high assurance IT equipment, requiring ASD approval and prescribed methods/timeframes. ISM-0300 is a specialised patch-management treatment that fits within the wider Annex A 8.8 vulnerability management requirement.
This control is broader than ISM-1143.
ISM-1143 requires organisations to develop and maintain patch management processes and procedures to ensure patches are applied in a controlled way. ISO/IEC 27001:2022 Annex A 8.8 supports this by requiring the organisation to obtain information about technical vulnerabilities, assess exposure, and take appropriate measures-patching being a primary measure. Annex A 8.8 is broader vulnerability management, while ISM-1143 is specifically about the procedural and operational mechanics of patching.
This control is broader than ISM-1366.
ISM-1366 requires security updates to be applied to mobile devices as soon as they become available. ISO/IEC 27001:2022 Annex A 8.8 (configuration management for security) is broader in requiring organisations to obtain vulnerability information, assess exposure, and take appropriate measures across information systems generally, which includes patching as one possible treatment. ISM-1366 is a specific prescriptive measure (timely mobile-device updating) that would sit within an Annex A 8.8 vulnerability/configuration management program.
This control is broader than ISM-1483.
ISM-1483 requires internet-facing server applications to be kept on their latest release to address known vulnerabilities. Annex A 8.8 supports this by requiring organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures, which commonly includes upgrading or patching server applications. Annex A 8.8 is broader vulnerability management across systems, while ISM-1483 is a specific prescriptive requirement focused on release currency for internet-facing server applications.
This control is broader than ISM-1501.
ISM-1501 requires operating systems that are no longer supported by vendors to be replaced. Annex A 8.8 is broader by requiring the organisation to obtain technical vulnerability information, evaluate exposure, and take appropriate measures across systems in use. Replacing an unsupported OS (ISM-1501) is one specific treatment option that would typically result from Annex A 8.8's vulnerability management process.
This control is broader than ISM-1606.
ISM-1606 requires timely remediation of vulnerabilities by applying patches, updates or vendor mitigations to software-based isolation mechanisms and the underlying host operating system on shared physical servers. Annex A 8.8 is broader, requiring organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures across information systems in use. ISM-1606 is a specific, operationally focused instance of Annex A 8.8 applied to virtualisation/isolation platforms and their host OS patching/mitigation actions.
This control is broader than ISM-1622.
ISM-1622 requires a specific hardening configuration: PowerShell must use Constrained Language Mode. Annex A 8.8 is broader, requiring organisations to identify technical vulnerabilities, assess exposure, and implement appropriate mitigations across information systems. Configuring Constrained Language Mode is one example of an appropriate measure to reduce exposure to PowerShell-based exploitation, but Annex A 8.8 extends well beyond PowerShell.
This control is broader than ISM-1659.
ISM-1659 requires organisations to implement Microsoft's Vulnerable Driver Blocklist as a specific technical measure to reduce exposure to vulnerable drivers. Annex A 8.8 requires obtaining information about technical vulnerabilities, assessing exposure, and applying appropriate measures, which includes implementing preventative controls like driver blocking. Annex A 8.8 is broader (process and governance for vulnerabilities), while ISM-1659 is a concrete Windows hardening action.
This control is broader than ISM-1690.
ISM-1690 requires a specific patching outcome: apply non-critical patches for online services within two weeks when no working exploits exist. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, assess exposure, and take appropriate measures, without prescribing a specific timeframe or limiting to online services. ISM-1690 is therefore a concrete, time-bound implementation that fits within the broader vulnerability management expectations of Annex A 8.8.
This control is broader than ISM-1691.
ISM-1691 sets a specific, time-bound requirement to apply vendor patches/mitigations for vulnerabilities in common productivity and security software within two weeks. ISO/IEC 27001:2022 Annex A 8.8 is broader, requiring organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures across information systems generally. ISM-1691 is one concrete implementation of Annex A 8.8 focused on a defined software set and a defined remediation timeframe.
This control is broader than ISM-1692.
ISM-1692 requires a specific, time-bound response: applying critical patches for defined application categories within 48 hours when vendor-rated critical or exploited. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures, which includes patching but is not limited to it. ISM-1692 is therefore a prescriptive subset implementation of the broader vulnerability management requirement in Annex A 8.8.
This control is broader than ISM-1693.
ISM-1693 requires a specific remediation action: applying patches/updates/vendor mitigations for certain applications within one month of release. ISO/IEC 27001:2022 Annex A 8.8 is broader, requiring organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures (which can include patching, configuration changes, compensating controls, or decommissioning). ISM-1693 is therefore a prescriptive subset implementation of the broader vulnerability management expectation in Annex A 8.8.
This control is broader than ISM-1694.
ISM-1694 requires a specific patching outcome: non-critical OS vulnerabilities on internet-facing servers and network devices are remediated within two weeks when no working exploits exist. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures, which broadly includes patching and other treatments. ISM-1694 is a prescriptive, time-bound implementation that fits within the broader vulnerability management expectations of Annex A 8.8.
This control is broader than ISM-1695.
ISM-1695 requires organisations to apply OS security patches for non-internet-facing workstations, servers and network devices within one month of release. ISO/IEC 27001:2022 Annex A 8.8 is broader, requiring organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures (which commonly includes patching) across information systems. ISM-1695 is a specific, time-bound patching measure that would sit under an Annex A 8.8 vulnerability management process.
This control is broader than ISM-1696.
ISM-1696 requires a specific technical vulnerability treatment outcome: applying critical OS patches within 48 hours for defined non-internet-facing systems and workstations when rated critical or exploited. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures, which includes patching as one possible treatment. ISM-1696 is a prescriptive, time-bound implementation that fits within the broader vulnerability management expectation of Annex A 8.8.
This control is broader than ISM-1697.
ISM-1697 requires applying vendor-provided mitigations for non-critical driver vulnerabilities within one month where no working exploits exist. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, assess exposure, and take appropriate measures across information systems generally. ISM-1697 is a specific, time-bound patching requirement within the broader vulnerability management expectations of Annex A 8.8.
This control is broader than ISM-1698.
ISM-1698 requires organisations to use a vulnerability scanner at least daily to identify missing patches or updates for vulnerabilities in online services. ISO/IEC 27001:2022 Annex A 8.8 requires obtaining information about technical vulnerabilities, evaluating exposure, and taking appropriate measures, which encompasses broader vulnerability management activities. ISM-1698 is a specific, prescriptive scanning control that fits within Annex A 8.8's wider requirement but does not cover evaluation and treatment in full.
This control is broader than ISM-1701.
ISM-1701 requires a specific operational practice: daily vulnerability scanning to find missing OS patches on internet-facing servers and internet-facing network devices. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures across information systems in use. ISM-1701 is a concrete, scoped implementation approach that fits within the broader vulnerability management expectation of Annex A 8.8.
This control is broader than ISM-1702.
ISM-1702 requires a specific operational practice: running a vulnerability scanner at least fortnightly to identify missing operating system patches on non-internet-facing endpoints, servers, and network devices. Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures, covering the full vulnerability management lifecycle. ISM-1702 is a narrower, prescriptive detection activity that fits within the broader ISO requirement but does not cover evaluation and treatment comprehensively.
This control is broader than ISM-1703.
ISM-1703 requires a specific operational practice: using a vulnerability scanner at least fortnightly to identify missing patches or updates for vulnerabilities in drivers. Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures, without prescribing a specific tool or frequency. ISM-1703 is therefore a more prescriptive and narrower implementation approach that can help satisfy part of Annex A 8.8's broader vulnerability management expectations.
This control is broader than ISM-1704.
ISM-1704 requires removing specific categories of unsupported software to reduce known and unpatched exposure. Annex A 8.8 requires the organisation to obtain vulnerability information, evaluate exposure, and take appropriate measures to address technical vulnerabilities. Removing unsupported software under ISM-1704 is a concrete risk treatment that supports the broader vulnerability management expectations in Annex A 8.8.
This control is broader than ISM-1751.
ISM-1751 requires a specific patching outcome: non-critical vendor OS vulnerabilities (with no working exploits) on certain IT equipment are remediated within one month. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, assess exposure, and take appropriate measures, without prescribing a specific timeframe or limiting to OS-only vulnerabilities. ISM-1751 is therefore a concrete, time-bound subset implementation of the broader vulnerability management expectations in Annex A 8.8.
This control is broader than ISM-1752.
ISM-1752 requires organisations to perform a specific, measurable activity: fortnightly vulnerability scanning to identify missing operating system patches on non-workstation, non-server, and non-network-device equipment. Annex A 8.8 requires obtaining information about technical vulnerabilities, evaluating exposure, and taking appropriate measures, which can be satisfied through multiple approaches including scanning and patch management. ISM-1752 is therefore a prescriptive subset implementation that helps meet the broader vulnerability management expectations in Annex A 8.8.
This control is broader than ISM-1754.
ISM-1754 requires vulnerabilities identified in software to be resolved in a timely manner. Annex A 8.8 addresses a broader vulnerability management lifecycle by requiring organisations to obtain information on technical vulnerabilities, evaluate exposure, and take appropriate measures. ISM-1754 aligns to the remediation portion of Annex A 8.8 but does not, by itself, cover the full acquisition and exposure evaluation activities.
This control is broader than ISM-1755.
ISM-1755 requires organisations to develop, implement and maintain a vulnerability disclosure policy for receiving and handling reported vulnerabilities securely. Annex A 8.8 focuses on obtaining information about technical vulnerabilities, evaluating exposure, and taking appropriate treatment actions, which is strengthened by having a formal disclosure channel feeding vulnerability intelligence into the organisation. Annex A 8.8 is centred on vulnerability identification and remediation processes, whereas ISM-1755 is about governance and safe intake/handling of externally (or internally) reported issues.
This control is broader than ISM-1808.
ISM-1808 requires a specific technical measure: using a vulnerability scanner with an up-to-date vulnerability database for scanning activities. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures. ISM-1808 is one concrete method that can satisfy part of Annex A 8.8, but Annex A 8.8 is broader than scanning tool updates and includes evaluation and remediation activities.
- ISM-1848Replace unsupported software-based isolation mechanisms sharing physical resourcesBroader than
This control is broader than ISM-1848.
ISM-1848 demands replacement of unsupported server isolation or OS components to avoid vulnerabilities. Annex A 8.8 underpins this requirement by mandating measures for known vulnerabilities management, which can include replacement when patches are unavailable.
This control is broader than ISM-1876.
ISM-1876 requires critical patches or vendor mitigations for online services to be applied within 48 hours when vendors rate vulnerabilities as critical or when working exploits exist. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures, without prescribing a specific 48-hour timeframe or limiting scope to online services. ISM-1876 is a specific, time-bound implementation within the broader vulnerability management expectations of Annex A 8.8.
This control is broader than ISM-1877.
ISM-1877 requires a specific remediation outcome: applying critical vendor patches/mitigations to internet-facing operating systems within 48 hours when critical or exploited. ISO/IEC 27001:2022 Annex A 8.8 requires a broader vulnerability management process-obtaining vulnerability information, evaluating exposure, and taking appropriate measures-without prescribing a 48-hour timeframe or limiting scope to internet-facing OS. ISM-1877 is therefore a prescriptive subset implementation of the broader requirement in Annex A 8.8.
This control is broader than ISM-1878.
ISM-1878 requires critical OS patches to be applied within 48 hours for certain categories of IT equipment when vendors rate vulnerabilities as critical or when working exploits exist. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures, which can include patching but is not limited to it. ISM-1878 is a prescriptive, time-bound patching requirement that fits within the broader vulnerability management expectations of Annex A 8.8.
This control is broader than ISM-1879.
ISM-1879 requires a specific, time-bound action: applying patches, updates or mitigations for critical driver vulnerabilities within 48 hours when vendor-critical or exploited. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, assess exposure, and take appropriate measures. ISM-1879 is a concrete, driver-focused and time-specific implementation that fits within the broader vulnerability management expectations of Annex A 8.8.
This control is broader than ISM-1900.
ISM-1900 requires a specific operational practice: using a vulnerability scanner at least fortnightly to identify missing firmware patches or updates. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, evaluate exposure, and take appropriate measures, covering the full vulnerability management lifecycle. ISM-1900 is a concrete, firmware-focused detection activity that fits within the broader expectations of Annex A 8.8.
This control is broader than ISM-1901.
ISM-1901 requires a specific vulnerability treatment action: applying non-critical patches within two weeks for a defined set of high-risk application types when no exploits exist. ISO/IEC 27001:2022 Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, assess exposure, and take appropriate measures. ISM-1901 is a prescriptive, time-bound subset of the broader vulnerability management expectations in Annex A 8.8.
This control is broader than ISM-1903.
Annex A 8.8 requires obtaining vulnerability information, evaluating exposure and applying mitigations such as patching to reduce risk. ISM-1903 mandates rapid patching of critical firmware vulnerabilities within 48 hours when critical or exploited, which is a direct example of 'appropriate measures' under Annex A 8.8. ISM-1903 is narrower, focusing only on firmware and defined criticality/exploit conditions, while Annex A 8.8 applies to technical vulnerabilities across systems generally.
This control is broader than ISM-1904.
Annex A 8.8 requires the organisation to obtain information on technical vulnerabilities, assess exposure, and take appropriate measures to address them. ISM-1904 is a specific measure within that lifecycle, mandating patching of non-critical firmware vulnerabilities within one month under defined exploitability conditions. ISM-1904 is therefore a subset of Annex A 8.8's broader vulnerability identification, assessment and treatment requirement.
This control is broader than ISM-1905.
ISM-1905 requires removal of vendor-unsupported online services to reduce risk from vulnerabilities that can no longer be remediated. Annex A 8.8 requires organisations to obtain information about technical vulnerabilities, assess exposure, and take appropriate measures across information systems in use. Removing unsupported online services (ISM-1905) is one specific treatment option within the broader vulnerability management expectations of Annex A 8.8.
This control is broader than ISM-1909.
ISM-1909 requires root cause analysis when resolving vulnerabilities and, where possible, remediation of entire vulnerability classes. This deepens the appropriate measures that Annex A 8.8 requires once vulnerabilities are identified and the organisation's exposure is evaluated. Annex A 8.8 covers the whole vulnerability management process (information gathering, evaluation and treatment), whereas ISM-1909 addresses how remediation is performed.
This control is broader than ISM-2118.
ISM-2118 requires organisations to conduct vulnerability assessments and penetration tests prior to deployment/significant changes and at least every six months. Annex A 8.8 requires ongoing management of technical vulnerabilities, including obtaining vulnerability information, evaluating exposure, and taking appropriate measures. ISM-2118 is a specific testing-focused implementation within the broader ISO requirement, which also covers identification, evaluation, and remediation governance beyond testing cadence.
This control partially meets ISM-1635.
ISM-1635 requires system owners to implement controls to protect systems and their environments. Annex A 8.8 focuses on vulnerability exposure management, which is one category of controls a system owner would implement under ISM-1635. ISM-1635 is broader as it extends to all relevant environmental safeguards, not restricted to technical vulnerabilities.
This control partially meets ISM-1914.
Annex A 8.8 requires obtaining vulnerability information, evaluating exposure and implementing measures including secure configuration of platforms. ISM-1914 requires approved configurations for operating systems to be developed, implemented and maintained, directly reducing exposure from insecure OS settings and configuration drift. Annex A 8.8 is broader because it encompasses vulnerability identification and assessment activities and is not limited to OS configuration baselining.
This control partially meets ISM-1915.
Annex A 8.8 requires organisations to manage security configuration by identifying technical vulnerabilities, evaluating exposure and implementing appropriate measures. ISM-1915 specifically requires approved configurations for user applications to be developed, implemented and maintained, which is one concrete measure that reduces exposure arising from insecure application configuration. Annex A 8.8 is broader because it also covers vulnerability intelligence and exposure evaluation, not just maintaining approved user application configurations.
This control partially meets ISM-1916.
Annex A 8.8 requires managing security configuration as part of reducing exposure to technical vulnerabilities. ISM-1916 requires approved configurations for server applications to be developed, implemented and maintained, which is a specific secure-configuration control to prevent insecure defaults and drift. Annex A 8.8 is broader because it also covers vulnerability intelligence and exposure evaluation across systems, not only server application configuration baselines.
This control partially meets ISM-2054.
ISM-2054 requires that, where an SBOM exists for imported third-party software components, it is used during development to ensure those components have no known vulnerabilities. This aligns with Annex A 8.8 because both require obtaining vulnerability information and acting on exposure, with ISM-2054 being a specific method focused on SBOM-driven third-party component checking in the SDLC. Annex A 8.8 is broader, covering technical vulnerability management across information systems generally, not only third-party components or SBOM usage.
This control partially overlaps ISM-0912.
Annex A 8.8 requires organisations to manage security configuration in response to technical vulnerabilities by assessing exposure and applying appropriate measures. ISM-0912 requires a change and configuration management plan with authorised baselines and defined processes for requesting, approving, tracking and notifying configuration changes, which directly supports controlled security configuration and reduces vulnerability introduced by unmanaged change. They overlap on maintaining secure baselines and governing configuration changes, but Annex A 8.8 also emphasises vulnerability information and exposure evaluation whereas ISM-0912 emphasises governance and workflow for configuration change.
This control partially overlaps ISM-1163.
ISM-1163 requires continuous monitoring including regular vulnerability assessments. Annex A 8.8 overlaps by demanding evaluation of technical vulnerabilities and appropriate countermeasures, though it lacks specific scanning schedules or penetration testing requirements.
- ISM-1526System owners continuously monitor security and manage threats, risks and controlsPartially overlaps
This control partially overlaps ISM-1526.
ISM-1526 requires system owners to continuously monitor security and manage cyber threats, security risks and security controls over time. Annex A 8.8 requires obtaining information about technical vulnerabilities, evaluating exposure, and taking appropriate measures, which is a core component of ongoing risk/control management. They overlap strongly in vulnerability-driven monitoring and remediation, but ISM-1526 is broader as it also covers non-vulnerability threats and overall continuous security posture management beyond technical vulnerabilities.
This control partially overlaps ISM-1616.
ISM-1616 requires organisations to implement a vulnerability disclosure program so external and internal researchers can report product/service vulnerabilities and the organisation can triage and remediate them. This overlaps with Annex A 8.8, which requires obtaining information about technical vulnerabilities, assessing exposure, and taking appropriate measures. Both drive vulnerability intake and remediation decisions, but ISM-1616 is specifically about a coordinated disclosure process and engagement channel, whereas Annex A 8.8 is broader vulnerability management across systems in use (not necessarily disclosure-driven).
This control partially overlaps ISM-1717.
Annex A 8.8 requires organisations to obtain information about technical vulnerabilities and take measures to reduce exposure. ISM-1717 establishes a vulnerability disclosure facilitation mechanism (security.txt) to help receive vulnerability reports for internet-facing domains, which contributes to obtaining vulnerability information used in Annex A 8.8 processes. The overlap is in vulnerability information intake, but Annex A 8.8 also requires exposure evaluation and remediation, while ISM-1717 does not address assessment or treatment actions.
This control partially overlaps ISM-1756.
Annex A 8.8 requires obtaining information on technical vulnerabilities, evaluating exposure, and taking appropriate measures to address them. ISM-1756 relates by establishing vulnerability disclosure processes and procedures that improve how an organisation receives and triages vulnerability information and initiates remediation. ISM-1756 is process-focused on inbound vulnerability reporting, while Annex A 8.8 is broader and includes exposure assessment and implementation of technical treatments.
- ISM-1809Compensating controls for unsupported systems pending removal or replacementPartially overlaps
This control partially overlaps ISM-1809.
ISM-1809 requires compensating controls to be implemented when unsupported applications, operating systems or devices cannot be removed or replaced immediately. Annex A 8.8 (technical vulnerability management) overlaps because unsupported products create known and unresolvable vulnerabilities, and the standard requires evaluating exposure and taking appropriate measures (which may include compensating controls). Annex A 8.8 is broader across all vulnerability sources, while ISM-1809 is specifically triggered by end-of-support conditions and emphasises interim controls until replacement/removal.
This control partially overlaps ISM-1908.
ISM-1908 requires vulnerabilities identified in an organisation's software to be publicly disclosed in a responsible and timely manner, including Common Weakness Enumeration and Common Platform Enumeration information. Both controls sit within technical vulnerability management: ISM-1908 makes structured vulnerability information available to those using the software, while Annex A 8.8 requires the organisation to obtain such information, evaluate its exposure and take appropriate measures. Annex A 8.8 focuses on vulnerabilities in systems the organisation uses, whereas ISM-1908 covers the disclosure obligations of an organisation that produces software, so each covers aspects the other does not.
This control partially overlaps ISM-1913.
ISM-1913 requires approved configurations for IT equipment to be developed, implemented and maintained. Annex A 8.8 focuses on obtaining vulnerability information, evaluating exposure and taking appropriate measures, which often results in configuration hardening or changes to approved baselines. The overlap is in configuration updates driven by vulnerabilities, but Annex A 8.8 is broader vulnerability management, while ISM-1913 is baseline configuration governance.
This control partially overlaps ISM-2131.
ISM-2131 requires certificate templates to be reviewed at least quarterly to find and fix misconfigurations that could allow privilege escalation or unauthorised enrolment. This overlaps with ISO/IEC 27001:2022 Annex A 8.8 because certificate template misconfigurations are a common class of technical vulnerability that organisations should evaluate for exposure and treat. Annex A 8.8 is broader and vulnerability-driven (feeds, assessment, treatment) and is not specifically about certificate template governance or a mandated three‑monthly review cadence.
This control depends on ISM-1643.
ISM-1643 requires maintaining registers of software versions and patch histories across applications, drivers, operating systems and firmware. This supports ISO/IEC 27001:2022 Annex A 8.8 by improving the organisation's ability to obtain vulnerability information, evaluate exposure, and decide appropriate remediation based on accurate version/patch state. Annex A 8.8 is broader vulnerability management, while ISM-1643 is a specific recordkeeping practice that strengthens exposure evaluation and assurance.
This control depends on ISM-2119.
ISM-2119 requires organisations to use suitable AI models to augment vulnerability assessments and penetration tests. This supports Annex A 8.8 by improving the organisation's ability to identify and triage technical vulnerabilities and better evaluate exposure through more effective discovery and analysis. Annex A 8.8 also covers end-to-end vulnerability management actions (e.g., evaluation and treatment) beyond the testing augmentation focus of ISM-2119.
ASD Essentials for enterprise IT: 6 mappings
- IT.PRO-06.1Continuously scan and assess assets for known software and configuration weaknessesBroader than
This control is broader than IT.PRO-06.1.
IT.PRO-06.1 requires known software and configuration weaknesses in assets to be identified through continuous and repeatable assessment activities, including vulnerability scanning. This directly delivers the gathering of technical vulnerability information and evaluation of the organisation's exposure required by Annex A 8.8. Annex A 8.8 is broader, as it also requires appropriate measures to be taken to address the vulnerabilities identified.
- IT.PRO-06.2Apply security patches within risk-based timeframes, or automatically where impact is lowBroader than
This control is broader than IT.PRO-06.2.
IT.PRO-06.2 requires security patches or updates to be applied within defined risk-based timeframes, or automatically where operational impact is low. Patching is the principal treatment under Annex A 8.8, which requires appropriate measures to be taken once the organisation's exposure to technical vulnerabilities has been evaluated. Annex A 8.8 is broader, also covering how vulnerability information is obtained and exposure is assessed, and it allows treatments other than patching.
- IT.PRO-06.3Remediate or mitigate above-threshold vulnerabilities within defined timeframes and verify effectivenessBroader than
This control is broader than IT.PRO-06.3.
IT.PRO-06.3 requires vulnerabilities exceeding defined risk thresholds to be remediated or mitigated within defined timeframes, prioritised by exploitation, exposure, criticality, impact and compensating controls, with treatment effectiveness verified. This is a specific, risk-based implementation of the exposure evaluation and appropriate measures required by Annex A 8.8. Annex A 8.8 also covers obtaining information about technical vulnerabilities, while IT.PRO-06.3 adds explicit treatment timeframes and verification of effectiveness.
- IT.GOV-14.1Identify, assess and treat legacy system risks until removal or replacementPartially overlaps
This control partially overlaps IT.GOV-14.1.
IT.GOV-14.1 requires a process to identify, assess and treat the cyber security risks of legacy systems and unsupported technologies through compensating controls, enhanced monitoring and assurance until they are removed or replaced. This overlaps with ISO/IEC 27001 Annex A 8.8, which requires exposure to technical vulnerabilities to be evaluated and appropriate measures taken, because unsupported technologies typically carry vulnerabilities that can no longer be patched and must be treated by other means. Annex A 8.8 applies to vulnerabilities in all systems in use, while IT.GOV-14.1 is limited to legacy and unsupported technology but also addresses its wider risks and eventual replacement.
- IT.IDE-04.1Identify relevant weaknesses and threat behaviours for risk assessments, reviewing them continuouslyPartially overlaps
This control partially overlaps IT.IDE-04.1.
IT.IDE-04.1 requires relevant weaknesses, malicious actor techniques and cyber threat behaviours to be identified when undertaking risk assessments and reviewed on a continuous basis. Its identification of weaknesses overlaps with ISO/IEC 27001 Annex A 8.8, which requires information about technical vulnerabilities to be obtained and the organisation's exposure to them evaluated. Annex A 8.8 also requires appropriate measures to be taken against identified vulnerabilities, while IT.IDE-04.1 additionally considers threat actor behaviour as a risk assessment input.
- IT.PRO-16.2Monitor vendor advisories and threat intelligence to act on supply chain exposurePartially overlaps
This control partially overlaps IT.PRO-16.2.
IT.PRO-16.2 requires vendor advisories and threat intelligence to be used to maintain awareness of supplier, product and component exposure to compromise, with action taken within timeframes proportionate to the risk. This overlaps with ISO/IEC 27001 Annex A 8.8, which requires information about technical vulnerabilities to be obtained, exposure evaluated and appropriate measures taken. IT.PRO-16.2 also covers compromise of suppliers beyond technical vulnerabilities, while Annex A 8.8 covers vulnerabilities in all systems in use regardless of their source.
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.




