ASD ISM 1632 Procure from suppliers with a strong security track record
What it says
Operating systems, applications, IT equipment, OT equipment and services are procured from suppliers that have a strong track record of maintaining the security of their own systems.
Quoted as published. Everything else on this page is written by Control Stack.
What it means
In plain EnglishFor software, IT and OT equipment, and services, choose only suppliers with a strong track record of securing their own systems; good products are not enough.
Operating systems, applications, IT equipment, OT equipment (operational technology, which monitors or controls physical processes) and services must be procured from suppliers that have a strong track record of maintaining the security of their own systems. Own systems means what the supplier runs itself, such as its corporate, development and support environments, rather than the product being bought. A track record is past performance, not a promise. The statement does not define strong or set a period, so the organisation decides both. ISM-1568 covers product security.
Free. Save your status, tasks and notes.
Why it matters
A breach of a supplier's own systems can expose customer data it holds or let tampered products and updates reach customers, however sound the product's design. A strong record lowers the chance of buying into that, though it cannot rule it out.
How to implement
Define what a strong track record means.
The control sets neither a period nor a test, so choose both, based on how much access or data the supplier will have. A clean public record alone proves little, and one incident need not fail a supplier if it was handled well.
Make the result a condition of buying.
Add the check to purchase approval, tenders and renewals, including small purchases, OT equipment and cloud subscriptions, and keep the result with the supplier's record before the order proceeds.
Collect evidence about the supplier's own systems.
Request its incident history and independent assurance reports, and check that their scope reaches its corporate, development and support environments, not only the product or service. Record what other evidence fills any gap. For cloud and managed service providers, also use the latest assessment required by ISM-1570, ISM-1793, ISM-1971 or ISM-1972.
Search public sources as well.
Look for reported breaches, regulator actions and security advisories naming the supplier, since its own account may leave them out. Record what you find and how the supplier responded.
Handle suppliers with no usable record.
A new company, or one that shares nothing, has not shown a strong track record. If you have no alternative or an existing contract cannot change, limit what the supplier can reach and record the unmet control as a risk for the system's authorising officer.
Keep it running
Look again at renewal, and after a reported breach of the supplier, a change of ownership, or an assurance report with new findings or a narrower scope. A record can weaken after purchase, so keep the evidence current.
Evidence and audit
- Check 1 of 3What an auditor asks for
Ask for
Recent purchases and renewals, picked from accounts payable and corporate card records, matched to the track record evidence on file.
Look at
Whether each one, including small purchases, OT equipment and cloud subscriptions, has evidence dated before the purchase.
Good evidence
Every picked purchase, including small purchases, OT equipment and cloud subscriptions, has evidence of the supplier's track record, dated before the purchase and meeting the organisation's written definition of strong.
- Check 2 of 3What an auditor asks for
Ask for
The assurance reports, and any other evidence of the supplier's own security, held for a sample of suppliers.
Look at
Whether the reports reach the supplier's corporate, development and support environments, not only the product or service, how old they are, what they found and what evidence covers any gap.
Good evidence
Each sampled supplier has reports that reach those environments and fall within the period the organisation set. Where reports are missing or leave out an environment, the file names other evidence from that period that covers it. Any significant findings were considered in the decision to buy.
- Check 3 of 3What an auditor asks for
Ask for
A public search for reported breaches and regulator actions involving a sampled supplier, run for this review rather than taken from the supplier file.
Look at
Whether the file records each event found and how the supplier responded.
Good evidence
Every event the search finds is in the file with a judgement of how the supplier handled it, and the decision to buy takes it into account.
Mappings
Closest match in ISO/IEC 27001: A.5.19, Information security in supplier relationships, which this control partially meets.
ISO/IEC 27001: 2 mappings
This control partially meets A.5.19.
ISM-1632 requires organisations to procure operating systems, applications, equipment and services from suppliers with a strong track record of securing their own systems. Annex A 5.19 requires defining and implementing processes to manage information security risks across supplier relationships, which includes due diligence and supplier selection activities that would encompass choosing reputable, secure suppliers. ISM-1632 is a specific supplier-selection expectation, whereas Annex A 5.19 is broader across the full supplier relationship lifecycle (selection, onboarding, ongoing management and offboarding).
- A.5.21Managing information security in the information and communication technology (ICT) supply chainPartially meets
This control partially meets A.5.21.
ISM-1632 requires organisations to procure ICT/OT products and services from suppliers with a proven ability to maintain the security of their own systems. Annex A 5.21 requires processes and procedures to manage information security risks across the ICT supply chain, which includes supplier evaluation, assurance, monitoring, and handling of supply chain threats. ISM-1632 is one concrete supply-chain risk treatment (choosing reliable suppliers), while Annex A 5.21 has broader supply chain scope including upstream components, logistics, and systemic supply chain controls.
ISO/IEC 42001: 1 mapping
This control partially overlaps A.10.3.
Annex A 10.3 requires ensuring supplier-provided AI dependencies align with responsible AI development and use. ISM-1632 overlaps by requiring procurement from suppliers with a strong security track record, reducing the chance that AI components (e.g., hosted models, MLOps tools, data pipelines) introduce vulnerabilities or enable tampering. ISM-1632 is limited to supplier security posture, while Annex A 10.3 also covers non-security responsible AI expectations such as transparency, bias management and use constraints.
ASD Essentials for enterprise IT: 1 mapping
- IT.GOV-11.1Base supplier selection on proportionate cyber supply chain risk assessmentsPartially overlaps
This control partially overlaps IT.GOV-11.1.
IT.GOV-11.1 requires supplier selection based on a proportionate cyber supply chain risk assessment, retaining assurance evidence; ISM-1632 sets a specific selection criterion, procuring from suppliers with a strong track record of maintaining the security of their own systems.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




