Skip to content
Procurement and outsourcing
ASD ISMISM-1632

ASD ISM 1632 Ensure secure procurement from reliable suppliers

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 English

Buy technology from suppliers known for keeping their systems secure.

This control is about buying technology, like computers and software, from suppliers known for having good security. This is important because if these suppliers aren't secure themselves, your business could end up with vulnerable products that hackers could exploit, leading to data breaches or system failures.

Why it matters

Purchasing from insecure suppliers risks receiving compromised technology, which can lead to data breaches or operational disruptions.

How to implement

  1. Procurement staff should research suppliers before making a purchase.

    They can do this by looking for supplier reviews, checking for security certifications, and asking for references from other customers. This will help ensure the supplier has a good reputation for security.

  2. IT teams should verify that suppliers adhere to security standards.

    This can be done by requesting documentation of their security practices, such as compliance with ISO/IEC 27001, which is an international standard for information security.

  3. Managers should incorporate security criteria into the procurement process.

    They can achieve this by adding specific security requirements into supplier agreements and contracts, ensuring suppliers commit to these standards.

  4. HR should ensure staff involved in procurement are trained on identifying secure suppliers.

    This can involve organising workshops or online training sessions that explain what to look for in a secure supplier.

  5. Board members should regularly review procurement policies to ensure they emphasise secure sourcing.

    This might include setting up annual reviews of procurement practices to align with emerging security threats and industry best practices.

Keep it running

Periodically assess suppliers' security posture, incident history and assurance evidence (e.g., audits) before purchase and renewal to reduce supply-chain compromise risk.

Evidence and audit

  1. Check 1 of 5What an auditor asks for

    Ask for

    Procurement records of recent technology purchases.

    Look at

    The suppliers used and check for evidence that their security track record was assessed.

    Good evidence

    Is having documented proof of supplier evaluations and security certifications.

  2. Check 2 of 5What an auditor asks for

    Look at

    The methods used to evaluate suppliers' security.

    Good evidence

    Will show comprehensive risk assessments and decision documents.

  3. Check 3 of 5What an auditor asks for

    Ask for

    Training records of staff involved in procurement.

    Look at

    The contents of the training sessions related to secure procurement practices.

    Good evidence

    Includes detailed records of training topics and attendance.

  4. Check 4 of 5What an auditor asks for

    Look at

    Clauses that specifically mention adherence to security standards.

    Good evidence

    Will include contractual security obligations with clear terms.

  5. Check 5 of 5What an auditor asks for

    Ask for

    Meeting notes or records from security review meetings with suppliers.

    Look at

    The discussed issues and the actions taken to address them.

    Good evidence

    Includes clear records of meetings and documented resolutions.

Mappings

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

ISO 27001

ISO/IEC 27001: 2 mappings

ISO 42001

ISO/IEC 42001: 1 mapping

ASD Essentials

ASD Essentials for enterprise IT: 1 mapping

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