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.
Free. Save your status, tasks and notes.
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
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.
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.
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
- 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.
- 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.
- 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/IEC 27001: 1 mapping
This control partially meets A.8.5.
ISM-1893 requires MFA for a specific authentication scenario: users accessing third-party online customer services handling the organisation's sensitive customer data. ISO/IEC 27001:2022 Annex A 8.5 requires implementation of secure authentication technologies and procedures based on access restrictions and access control policy, which can include MFA across many systems and contexts. ISM-1893 is a prescriptive, scoped instance of the broader authentication control intent in Annex A 8.5.
ASD Essential Eight: 9 mappings
- E8-MF-ML1.5Multi-factor authentication for third-party services with sensitive customer dataEquivalent
This control is equivalent to E8-MF-ML1.5.
ISM-1893 requires multi-factor authentication (MFA) for human users accessing third-party online customer services that process, store or communicate the organisation's sensitive customer data. E8-MF-ML1.5 states the same requirement for users of third-party online customer services handling sensitive customer data. Both are aligned in scope (third-party, online customer services, sensitive customer data) and depth (MFA required for user authentication).
This control is broader than E8-MF-ML1.7.
E8-MF-ML1.7 specifies what constitutes MFA by mandating specific factor combinations. ISM-1893 requires MFA for users authenticating to third-party online customer services that process, store or communicate sensitive customer data, which should be implemented in line with E8-MF-ML1.7's factor requirements. ISM-1893 is narrower because it targets a particular external customer-service context rather than defining MFA construction across the board.
This control partially meets E8-MF-ML2.5.
ISM-1893 requires MFA for human users authenticating to third-party online customer services that handle the organisation's sensitive customer data. E8-MF-ML2.5 is broader because it applies to MFA for authenticating users of systems generally and adds a specific quality requirement that MFA be phishing-resistant. ISM-1893 overlaps on the use of MFA, but does not specify phishing-resistance or apply to all systems.
This control partially overlaps E8-MF-ML1.1.
E8-MF-ML1.1 requires MFA for users of the organisation's online services that handle sensitive data. ISM-1893 overlaps by requiring MFA for third-party online customer services that process, store, or communicate the organisation's sensitive customer data, which is a specific subset of sensitive online services and explicitly focuses on third-party customer platforms. E8-MF-ML1.1 covers both first-party and third-party online services handling sensitive data, while ISM-1893 is limited to third-party customer services and sensitive customer data.
- E8-MF-ML1.2Multi-factor authentication for third-party services handling sensitive dataPartially overlaps
This control partially overlaps E8-MF-ML1.2.
E8-MF-ML1.2 requires MFA for third-party online services handling sensitive organisational data. ISM-1893 stipulates MFA for third-party online customer services handling sensitive customer data, which is a specific subset of sensitive data and service types. ISM-1893 is narrower on service category (customer services) and data type (customer data), while E8-MF-ML1.2 is broader across third-party services handling any organisational sensitive data.
- E8-MF-ML1.4MFA for users of the organisation's online customer services with sensitive dataPartially overlaps
This control partially overlaps E8-MF-ML1.4.
ISM-1893 requires MFA for staff authenticating to third-party online customer services that handle the organisation's sensitive customer data. E8-MF-ML1.4 requires MFA for users authenticating to the organisation's own online customer services handling sensitive customer data. They overlap on protecting access to online customer services with MFA, but differ on service ownership (third-party vs organisation-operated).
- E8-MF-ML1.6Multi-factor authentication for customer access to online services handling sensitive dataPartially overlaps
This control partially overlaps E8-MF-ML1.6.
E8-MF-ML1.6 requires multi-factor authentication (MFA) for customers accessing online customer services that process, store or communicate sensitive customer data. ISM-1893 similarly requires MFA but is scoped to users authenticating to third-party online customer services handling the organisation's sensitive customer data. The overlap is the MFA requirement for access to online customer services handling sensitive customer data, while the key difference is customer-vs-user focus and third-party vs (potentially) organisation-provided services.
This control partially overlaps E8-MF-ML2.2.
ISM-1893 requires MFA for users accessing third-party online customer services that handle sensitive customer data. E8-MF-ML2.2 requires MFA for unprivileged users of systems, which can include users accessing online services but is not limited to third-party customer services or sensitive customer data. They overlap where those third-party customer services are accessed as part of system usage by unprivileged users, but each control has distinct scope constraints.
This control depends on E8-MF-ML2.3.
ISM-1893 requires MFA for users authenticating to third-party online customer services that process, store or communicate the organisation's sensitive customer data. E8-MF-ML2.3 strengthens this by requiring that MFA used for authenticating users of online services be phishing-resistant, which would improve the security of the MFA mandated by ISM-1893. ISM-1893 does not specify phishing resistance, so E8-MF-ML2.3 adds a quality requirement beyond the primary control's baseline.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




