Multi-factor authentication
Require MFA for online services, organisational systems and customer-facing services, preferring phishing-resistant methods.
24 controls in this part of the Essential Eight mitigation strategies. Each control links to plain-English guidance, audit tips and cross-framework mappings.
24 controls
No controls on this page match.
All 24 controls
- E8-MF-ML1.1Require multi-factor authentication for sensitive online servicesEvery user sign-in to the organisation's own online services that process, store or communicate its sensitive data must use multi-factor authentication.
- E8-MF-ML1.2Multi-factor authentication for third-party services handling sensitive dataUsers 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.
- E8-MF-ML1.3Use MFA where available for third-party online services with non-sensitive dataWhere a third-party online service handling the organisation's non-sensitive data offers multi-factor authentication, turn it on and require it for every user.
- E8-MF-ML1.4MFA for users of the organisation's online customer services with sensitive dataStaff and other users must use multi-factor authentication to sign in to the organisation's own online customer services that process, store or communicate sensitive customer data.
- E8-MF-ML1.5Multi-factor authentication for third-party services with sensitive customer dataStaff and other users must sign in with multi-factor authentication to third-party online customer services, such as a hosted store, that handle the organisation's sensitive customer data.
- E8-MF-ML1.6Multi-factor authentication for customer access to online services handling sensitive dataMake multi-factor authentication mandatory, not optional, for customers signing in to online customer services that process, store or communicate sensitive customer data.
- E8-MF-ML1.7Multi-factor authentication must include something users haveEvery multi-factor authentication method must include something users have, such as a security key or phone, either with a password or PIN, or unlocked by a PIN or biometric.
- E8-MF-ML2.1Multi-factor authentication for privileged users of systemsAt Maturity Level Two, privileged users must use multi-factor authentication to log on to systems, such as workstations, servers and jump servers, not only to online services.
- E8-MF-ML2.2Use multi-factor authentication for unprivileged user accessAt Maturity Level Two, unprivileged users must use multi-factor authentication to log on to systems, such as their workstations, not only to online services.
- E8-MF-ML2.3Phishing-resistant multi-factor authentication for users of online servicesAt Maturity Level Two, multi-factor authentication for users of online services must be phishing-resistant, such as a security key, passkey or smart card, not a code or push approval.
- E8-MF-ML2.4Offer customers a phishing-resistant multi-factor authentication option for online customer servicesMulti-factor authentication for customers of online customer services must include a phishing-resistant method, such as a passkey or security key, that customers can choose to use.
- E8-MF-ML2.5Multi-factor authentication used for system access is phishing-resistantAll multi-factor authentication for users signing in to systems, privileged or not, must be phishing-resistant, such as a smart card, security key or passkey, never a one-time code.
- E8-MF-ML2.6MFA success and failure events are centrally loggedBoth successful and failed multi-factor authentication events must be sent to a central log, from every system and service where multi-factor authentication is used.
- E8-MF-ML2.7Protect event logs from unauthorised changesEvent logs must be protected against modification or deletion by anyone not authorised to do so, including an attacker using a compromised administrator account.
- E8-MF-ML2.8Timely analysis of event logs from internet-facing serversEvent logs from internet-facing servers must be analysed promptly enough to detect cyber security events while there is still time to act on them.
- E8-MF-ML2.9Cyber security events are analysed to identify incidents timelyEvery cyber security event, whether found in logs, raised by a security tool or reported by a person, must be assessed promptly to decide whether it is a cyber security incident.
- E8-MF-ML2.10Report cyber security incidents to the Chief Information Security Officer promptlyEvery cyber security incident must be reported to the chief information security officer or a delegate as soon as possible, including incidents found long after they happened.
- E8-MF-ML2.11Report cyber security incidents to ASD as soon as possibleEvery cyber security incident must be reported to ASD as soon as possible, including incidents found long after they happened, not only the most serious ones.
- E8-MF-ML2.12Cyber security incident response plan enacted after incident identificationOnce a cyber security incident has been identified, the cyber security incident response plan must be put into action, so the response follows its agreed roles and steps.
- E8-MF-ML3.1Multi-factor authentication is used to authenticate users of data repositoriesEvery user of a data repository, such as a database or file share, must be authenticated with multi-factor authentication, not a password alone, whichever route they use.
- E8-MF-ML3.2Phishing-resistant multi-factor authentication for online customer servicesAny MFA used to authenticate customers of online customer services must be phishing-resistant, such as passkeys, with no codes or push approvals left as an alternative.
- E8-MF-ML3.3Phishing-resistant multi-factor authentication for data repositoriesThe MFA that users of data repositories authenticate with must be phishing-resistant, such as passkeys, security keys or smart cards, not codes or push approvals.
- E8-MF-ML3.4Analyse event logs from non-internet-facing servers timely to detect security eventsEvent logs from servers not directly reachable from the internet, such as domain controllers, must be analysed promptly to detect cyber security events like bursts of failed MFA.
- E8-MF-ML3.5Timely analysis of workstation event logs for cyber security eventsEvent logs from every workstation, including laptops away from the office, must be analysed promptly to detect cyber security events like bursts of failed sign-ins.
Back to the full Essential Eight control list, or browse the complete control library.




