Essential Eight MF-ML1.2 Multi-factor authentication for third-party services handling sensitive data
What it says
Multi-factor authentication is used to authenticate users to third-party online services that process, store or communicate their organisation's sensitive data.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Users must sign in with multi-factor authentication to every third-party online service that processes, stores or communicates the organisation's sensitive data, with no exceptions.
Multi-factor authentication (MFA) must be used whenever users sign in to third-party online services that process, store or communicate their organisation's sensitive data. MFA means signing in with more than one kind of factor, in a combination E8-MF-ML1.7 allows. A third-party online service is one another provider runs over the internet, such as cloud payroll, accounting or file-sharing software. Unlike E8-MF-ML1.3, which covers non-sensitive data, there is no 'where available' exception: using a service with no way to apply MFA falls short.
Free. Save your status, tasks and notes.
Why it matters
Sensitive data held by a provider can be reached from anywhere with a valid username and password. Requiring MFA means a stolen, reused or guessed password is not enough on its own to open it.
How to implement
Find every third-party service that handles sensitive data.
Start from contracts and the identity provider's list of connected applications, then compare with card and expense records and web proxy logs to find services adopted without IT. Record what data each processes, stores or communicates, and how you decided what counts as sensitive.
Enforce MFA for every account on each service.
Where the service supports single sign-on, connect it to the organisation's identity provider, require MFA there and turn off the service's own password sign-in for users. Otherwise make the service's built-in MFA mandatory for all accounts, including administrator, shared and contractor accounts.
Resolve services that offer neither MFA nor single sign-on.
Ask the provider to add either; if they cannot, move the sensitive data to a service that can, or stop using it. Track the gap as a shortfall until it closes, because a recorded exception does not meet this requirement.
Keep it running
Check MFA before a new third-party service receives sensitive data, and recheck when a provider changes its sign-in options or a service starts handling sensitive data. Watch for local accounts created on a service outside single sign-on.
Evidence and audit
- Check 1 of 3What an auditor asks for
Ask for
The register of third-party online services, and card and expense records or web proxy logs for the same period.
Look at
Whether every service in use is on the register, and whether a sample of services marked non-sensitive really handle no sensitive data.
Good evidence
Every third-party service found in the independent sources is on the register, and none marked non-sensitive is found to process, store or communicate sensitive data.
- Check 2 of 3What an auditor asks for
Ask for
The MFA settings and account list for a sample of in-scope services chosen from the independent sources, with a test sign-in to each.
Look at
Whether MFA is enforced for every account rather than left to each user, and whether a local or alternative sign-in page accepts a password alone.
Good evidence
Every account the organisation holds on each sampled service must complete MFA of a kind E8-MF-ML1.7 allows, and no sign-in route accepts a password alone.
- Check 3 of 3What an auditor asks for
Ask for
The services recorded as having no MFA, with each provider's current sign-in documentation.
Look at
Whether any of them still process, store or communicate sensitive data.
Good evidence
No service that processes, stores or communicates sensitive data is in use without MFA; one that is counts as a shortfall even if an exception or accepted risk is recorded.
Mappings
Closest match in ASD Information Security Manual: ISM-1679, Multi-factor authentication for third-party services handling sensitive data, which asks for the same thing.
ISO/IEC 27001: 1 mapping
This control partially meets A.8.5.
E8-MF-ML1.2 requires MFA for authenticating users to third-party services handling sensitive data. ISO/IEC 27001:2022 Annex A 8.5 requires implementing secure authentication procedures commensurate with access restrictions and access control policy, which can include MFA. E8-MF-ML1.2 is a specific prescriptive instance within the broader authentication expectations of Annex A 8.5.
ASD Information Security Manual: 7 mappings
This control is equivalent to ISM-1679.
ISM-1679 requires multi-factor authentication for human users accessing third-party online services that process, store or communicate the organisation's sensitive data. E8-MF-ML1.2 states the same requirement for users authenticating to third-party online services handling the organisation's sensitive data. The scope and intent align closely enough that implementing E8-MF-ML1.2 would largely satisfy ISM-1679 and vice versa.
This control partially meets ISM-1401.
E8-MF-ML1.2 requires multi-factor authentication (MFA) for user access to third-party online services handling the organisation's sensitive data. ISM-1401 defines what constitutes MFA and acceptable factor combinations, applying across contexts. E8-MF-ML1.2 is a specific use case of the broader MFA requirement described in ISM-1401.
- ISM-1504Multi-factor authentication for human users of sensitive data online servicesPartially overlaps
This control partially overlaps ISM-1504.
ISM-1504 requires MFA for human users of the organisation's own online services that handle the organisation's sensitive data. E8-MF-ML1.2 overlaps by applying the same MFA requirement to third-party online services that process, store or communicate the organisation's sensitive data. They align on protecting access to sensitive-data services with MFA, but differ on service ownership (internal vs third-party).
- ISM-1680Multi-factor authentication for human users of third-party services holding non-sensitive dataPartially overlaps
This control partially overlaps ISM-1680.
E8-MF-ML1.2 requires MFA for third-party online services processing, storing or communicating the organisation's sensitive data. ISM-1680 also requires MFA for third-party online services but is scoped to the organisation's non-sensitive data. They align on the control mechanism (MFA for third-party services) but differ materially on the data sensitivity threshold, therefore impacting the risk posture and minimum expectations.
- ISM-1681MFA for customers of online customer services handling sensitive customer dataPartially overlaps
This control partially overlaps ISM-1681.
ISM-1681 mandates MFA for customers accessing the organisation's online customer services that handle sensitive customer data. E8-MF-ML1.2 mandates MFA for users accessing third-party online services that handle the organisation's sensitive data. They overlap on applying MFA to online services handling sensitive information, but differ on both the service ownership (organisation-run vs third-party) and the data focus (customer data vs organisation data).
- ISM-1893Multi-factor authentication for users of third-party online customer servicesPartially overlaps
This control partially overlaps ISM-1893.
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.
This control depends on ISM-1919.
E8-MF-ML1.2 requires MFA for authentication to third-party services handling sensitive data. ISM-1919 supports this by disabling non-MFA authentication protocols for online services, reducing bypass paths. E8-MF-ML1.2 sets the MFA requirement, while ISM-1919 ensures its enforcement.
ASD Essentials for enterprise IT: 1 mapping
- IT.PRO-13.4Enforce phishing-resistant MFA for all user authentication, including from untrusted locationsPartially overlaps
This control partially overlaps IT.PRO-13.4.
IT.PRO-13.4 requires phishing-resistant MFA for users authenticating to systems, including from untrusted, external or high-risk locations; E8-MF-ML1.2 requires MFA for users of third-party online services handling the organisation's sensitive data, a narrower case without phishing resistance.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




