Skip to content
Procurement and outsourcing
ASD ISMISM-1738

ASD ISM 1738 Verify compliance with security requirements

What it says

The right to verify compliance with security requirements documented in contractual arrangements with service providers is regularly exercised.

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

In plain English

The contractual right to verify service providers' compliance with security requirements must actually be used regularly, at a period the organisation chooses because the control sets none.

The right to verify that service providers comply with the security requirements in their contractual arrangements must be regularly exercised. ISM-1571 puts the right in the contract, and this control requires it to be used, so an audit clause nobody has used does not count. Exercising it means checking evidence against the requirements, not accepting the provider's word. The control sets no period, so the organisation decides how often for each provider, based on the data's sensitivity or classification, how critical the service is and earlier findings.

Why it matters

A provider's protection can weaken long after the contract is signed, through service changes or new subcontractors. Verification shows what the provider really does, in time to demand a fix or leave, rather than finding out after an incident.

How to implement

  1. Set how often to verify each provider.

    The control sets no period, so choose one from the data's sensitivity or classification, how critical the service is and earlier findings. Record each next due date beside the provider's entry in the managed service or outsourced cloud service register (ISM-1736, ISM-1637).

  2. Choose a method for each requirement.

    Work within the clause ISM-1571 requires. Options include requesting evidence such as configuration exports, running tests or inspecting on site. Reports from the assessments providers must undergo (ISM-1570, ISM-1793, ISM-1971, ISM-1972) help but run up to 24 months apart, so verify between them. On a bought service, also check the settings you can see.

  3. Compare the evidence with each contract requirement.

    Work through the security requirements one at a time, recording what you examined, its date and the result. A report whose scope leaves out your service proves nothing about it. Receiving a report is not verification until someone has done this comparison.

  4. Follow up each shortfall.

    Get a dated fix from the provider, then verify again that it worked. If it is not fixed, use the contract's remedies, including any break clause (ISM-1804), and keep the finding open until the requirement is met.

Keep it running

Keep a next verification date against each provider. Verify earlier after an incident at the provider, a significant change to its own service provider arrangements (ISM-1794) or a change to the security requirements, and shorten the period if findings rise.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    The managed service and outsourced cloud service registers, payment records, and each provider's verification period and last verification date.

    Look at

    Whether any service provider in the payment records is missing from the registers, whether each provider has a completed verification within its period, what that verification used, and what each period is based on.

    Good evidence

    Every service provider, whether on a register or only in the payment records, has a completed verification within its period, and each period is based on the data and how critical the service is. A provider past its first due date with no completed verification, or verified only by reading its scheduled assessment report, fails. A managed service or outsourced cloud service missing from its register is a finding against ISM-1736 or ISM-1637.

  2. Check 2 of 3What an auditor asks for

    Ask for

    The working papers from a sampled verification, with the contract's security requirements.

    Look at

    What was examined for each requirement, how current it was, and whether it covers the service in use.

    Good evidence

    Each requirement has a recorded result based on current evidence about the service in use, and the provider's own assurance is not accepted on its own.

  3. Check 3 of 3What an auditor asks for

    Ask for

    A repeat of one check from the last verification, using evidence available today, with the record of any shortfalls that verification found.

    Look at

    Whether the repeat agrees with the recorded result, and what happened to each shortfall.

    Good evidence

    The repeat agrees with the recorded result, or a later change explains the difference, and each shortfall has been fixed and re-verified or is still being pursued under the contract.

Mappings

Closest match in ISO/IEC 27001: A.5.20, Addressing information security within supplier agreements, which this control covers in full and more.

ISO 27001

ISO/IEC 27001: 7 mappings

  • A.8.21Security of network servicesPartially overlaps
  • A.8.30Outsourced developmentPartially overlaps
ISO 42001

ISO/IEC 42001: 1 mapping

  • A.10.2Allocating responsibilitiesPartially overlaps

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