Skip to content
Multi-factor authentication
Essential EightE8-MF-ML1.2

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.

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

  1. 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.

  2. 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.

  3. 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

  1. 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.

  2. 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.

  3. 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 27001

ISO/IEC 27001: 1 mapping

  • A.8.5Secure authenticationPartially meets
ASD ISM

ASD Information Security Manual: 7 mappings

ASD Essentials

ASD Essentials for enterprise IT: 1 mapping

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