Skip to content
Procurement and outsourcing
ASD ISMISM-1567

ASD ISM 1567 Do not use high-risk suppliers

What it says

Suppliers identified as high risk by a cyber supply chain risk assessment are not used.

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

In plain English

Do not use any supplier that a cyber supply chain risk assessment identifies as high risk, whether it is a new supplier or one already in use.

Suppliers identified as high risk by a cyber supply chain risk assessment must not be used. That assessment, required by ISM-1452, weighs the risks each supplier brings to a system, and its result is the trigger. The wording is absolute: it covers a supplier already in use as well as a new purchase, and the statement gives no exception. High risk is not defined, so the rating method the organisation sets for its assessment decides which suppliers are caught.

Why it matters

A supplier rated high risk brings that risk into the systems it touches, such as covert collection of data held offshore or products left unpatched. Not using it closes that exposure from then on, rather than carrying a risk the assessment has already flagged.

How to implement

  1. Define what rates a supplier as high risk.

    Put the criteria in the assessment method (ISM-1452) before rating anyone, because this rating ends the supplier's use. Say whether a high rating for one system bars the supplier everywhere. Write down who can change a rating and on what evidence, so it is not lowered just to keep a supplier.

  2. Block high-risk suppliers at the point of purchase.

    Keep them off the approved supplier list (ISM-1786), flag them in the purchasing system's supplier records so orders are refused, and review corporate card purchases and cloud sign-ups, which can bypass that system, against the suppliers rated high risk.

  3. Search for indirect use.

    Look through system registers and service contracts for the supplier's products or services arriving through resellers, integrators or managed service providers, because that still counts as using the supplier.

  4. Exit any high-risk supplier already in use.

    List the affected systems, choose a replacement, move the data, remove the supplier's access and accounts, then get written confirmation that it has deleted what it still holds. Use the contract's data portability terms (ISM-1574) where they exist, and its break clause for failing security requirements (ISM-1804) if the rating's cause triggers it.

  5. Manage a supplier you cannot leave straight away.

    Set an exit date, limit the supplier's access until then, and record the unmet control as a risk for the system's authorising officer. The statement offers no exception, so this is a managed gap, not compliance.

Keep it running

Apply this whenever an assessment result changes, because a supplier can become high risk after purchase through a change of ownership, location or security record. Look again when a contract comes up for renewal or a reseller changes its sources.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    All suppliers rated high risk, with current accounts payable records, active contracts and system registers to compare against.

    Look at

    Whether any supplier rated high risk is still being paid, under contract or running in a system, including through a reseller.

    Good evidence

    No supplier rated high risk appears in those records, directly or through a reseller, and each one formerly in use has its exit recorded and its access removed.

  2. Check 2 of 3What an auditor asks for

    Ask for

    The rating criteria and the rating history of every assessed supplier.

    Look at

    Whether high risk is a defined outcome, whether each rating follows the criteria, and what supports any rating that was lowered.

    Good evidence

    The criteria define high risk, sampled ratings follow them, and each rating that was lowered has new evidence and a recorded reason, not only a business need to keep the supplier.

  3. Check 3 of 3What an auditor asks for

    Ask for

    A demonstration of raising a purchase against a test supplier record marked high risk, and the review that covers corporate card payments.

    Look at

    Where the purchase is stopped, and whether any buying route gets around the block.

    Good evidence

    The purchase is stopped before it is placed, by the purchasing system or a recorded approval step, and routes neither can block, such as corporate cards, are covered by a review that would catch a payment to that supplier.

Mappings

Closest match in ISO/IEC 27001: A.5.19, Information security in supplier relationships, which this control partially meets.

ISO 27001

ISO/IEC 27001: 3 mappings

ASD Essentials

ASD Essentials for enterprise IT: 1 mapping

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