Skip to content
System access
ASD ISMISM-1893

ASD ISM 1893 Multi-factor authentication for users of third-party online customer services

What it says

Multi-factor authentication is used to authenticate human users to third-party online customer services that process, store or communicate their organisation's sensitive customer data.

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

In plain English

Require multi-factor authentication for the organisation's people who sign in to third-party online customer services, such as a hosted store, that handle its sensitive customer data.

Multi-factor authentication must be used to authenticate human users, such as staff and contractors, to third-party online customer services that process, store or communicate their organisation's sensitive customer data. These are customer-facing services another organisation runs for it, such as a hosted online store, booking system or customer support platform. Sensitive customer data is customer data that would cause damage if compromised. Multi-factor authentication combines two or more different kinds of factor. The organisation's own customer services are covered by ISM-1892, and customers' sign-in by ISM-1681.

Why it matters

A hosted customer platform puts many customers' records behind the staff logins the organisation issues. A staff password stolen by phishing could expose or alter every record that account can reach. Requiring a second factor means the password alone is not enough.

How to implement

  1. List third-party customer platforms that handle sensitive customer data.

    Compare the outsourced cloud service register (ISM-1637) and finance records with the platforms customer-facing teams actually use, such as store, booking, payment and support platforms. Record who in the organisation has an account on each.

  2. Require multi-factor authentication for every staff account on each platform.

    Use single sign-on through your identity provider with a policy requiring a second factor, and disable local logins, or require the platform's own second factor on any it will not let you disable. Otherwise, set the platform's own multi-factor option to required for all accounts, including contractors' accounts.

  3. Deal with platforms that cannot require it.

    The control has no exception, so raise it with the provider and build it into the contract at renewal (ISM-0072 puts security requirements in contracts). Until it is fixed, move the sensitive customer data to a platform that supports it, or stop the platform handling that data.

Keep it running

Check the multi-factor setting whenever a platform is adopted, its sign-in options change or contractors are given accounts. Recheck if a platform starts handling sensitive customer data it did not handle before.

Evidence and audit

  1. Check 1 of 3What an auditor asks for

    Ask for

    The list of third-party online customer services handling sensitive customer data, with the outsourced cloud service register and finance records.

    Look at

    Whether any customer-facing platform that is paid for or registered is missing from the list.

    Good evidence

    Every customer-facing platform in the register and finance records is on the list with its data sensitivity, and none handling sensitive customer data is missing.

  2. Check 2 of 3What an auditor asks for

    Ask for

    The user list and authentication settings exported from each sampled platform, compared with the users assigned to it in the identity provider.

    Look at

    Whether any account exists only in the platform, outside single sign-on, and whether every account for the organisation's people must use multi-factor authentication.

    Good evidence

    Every account for the organisation's people on each sampled platform, including any that exist only in the platform, must use multi-factor authentication, and none can sign in with a password alone.

  3. Check 3 of 3What an auditor asks for

    Ask for

    A demonstration of signing in to a sampled platform with a test staff account's correct password only, through the web page and any mobile app.

    Look at

    Whether the platform or identity provider demands a second factor on each route.

    Good evidence

    Every route refuses access until a second factor is given.

Mappings

Closest match in ASD Essential Eight: E8-MF-ML1.5, Multi-factor authentication for third-party services with sensitive customer data, which asks for the same thing.

ISO 27001

ISO/IEC 27001: 1 mapping

  • A.8.5Secure authenticationPartially meets
Essential Eight

ASD Essential Eight: 9 mappings

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