Restrict admin privileges
Separate privileged accounts, validate requests for privileged access, and keep privileged accounts off the web and email.
29 controls in this part of the Essential Eight. Each control links to plain-English guidance, audit tips and cross-framework mappings.
29 controls
No controls on this page match.
All 29 controls
- E8-RA-ML1.1Validating privileged access requests upon initial requestValidate every request for privileged access to a system, application or data repository at the time it is first made, before granting the access.
- E8-RA-ML1.2Dedicated privileged user accounts for privileged dutiesGive each privileged user a separate privileged account used only for duties that need privileged access, with everyday work such as email done on another account.
- E8-RA-ML1.3Prevent privileged user accounts from accessing internet, email and web servicesBlock privileged user accounts from the internet, email and web services by technical means, unless an account is explicitly authorised to access online services.
- E8-RA-ML1.4Limit privileged user accounts to essential online service accessLimit each privileged account explicitly authorised for online services strictly to what the people or services using it need for their duties, and block everything else.
- E8-RA-ML1.5Privileged users use separate privileged and unprivileged environmentsPrivileged users must do privileged work in an operating environment separate from the one they use for everyday work; two accounts on one desktop are not enough.
- E8-RA-ML1.6Unprivileged user accounts restricted from logging on to privileged environmentsUnprivileged user accounts, including privileged users' own everyday accounts, must be technically unable to log on to any privileged operating environment.
- E8-RA-ML1.7Prevent privileged user accounts from logging on to unprivileged environmentsPrivileged user accounts, apart from local administrator accounts, must be technically unable to log on to unprivileged operating environments such as standard workstations.
- E8-RA-ML2.1Disable privileged access after 12 months without revalidationEach grant of privileged access to a system, application or data repository must be disabled if it is not revalidated within 12 months.
- E8-RA-ML2.2Privileged access is disabled after 45 days of inactivityPrivileged access to a system or application that has not been used for 45 days must be disabled, with no exception for rarely used accounts.
- E8-RA-ML2.3Privileged environments are not virtualised within unprivileged environmentsA privileged operating environment must not run as a virtual machine inside an unprivileged one, as an administration virtual machine on an everyday desktop would.
- E8-RA-ML2.4Conduct administrative activities through jump serversAdministrative activities must go through jump servers, the dedicated servers administrators connect to first, never straight from their own device to the system they manage.
- E8-RA-ML2.5Long, unique, managed break glass, local admin and service account credentialsBreak glass, local administrator and service accounts each need a long, unique, unpredictable credential that is managed, not shared between devices or built from a pattern.
- E8-RA-ML2.6Privileged access events are centrally loggedEvents showing privileged access being used, such as privileged sign-ins, failed attempts and use of administrative rights, must be collected into a central log.
- E8-RA-ML2.7Centrally log privileged user account and security group management eventsRecords of privileged user accounts being created, changed or deleted, and of security groups and their membership changing, must go to a central log.
- E8-RA-ML2.8Event logs are protected from unauthorised changes and lossesProtect event logs, including central records of privileged access and account changes, so that nobody without authorisation can edit or delete them.
- E8-RA-ML2.9Timely analysis of internet-facing server event logs to detect security eventsAnalyse event logs from every internet-facing server promptly enough to detect cyber security events; other servers and workstations follow at Maturity Level Three.
- E8-RA-ML2.10Timely analysis of cyber security events to identify incidentsExamine each cyber security event soon after it is detected and decide whether it amounts to a cyber security incident, so incidents are not left unrecognised.
- E8-RA-ML2.11Report cyber incidents to the CISO promptlyTell the chief information security officer, or a delegate they have named, about every cyber security incident as soon as possible after it happens or comes to light.
- E8-RA-ML2.12Report cyber security incidents to ASD promptlyTell ASD about every cyber security incident as soon as possible after it happens or comes to light, sending what is known rather than waiting for the investigation.
- E8-RA-ML2.13Enact cyber incident response plan after an incident is identifiedOnce a cyber security incident is identified, put the cyber security incident response plan into action and follow it, rather than handling the incident informally.
- E8-RA-ML3.1Limit privileged access to what is necessary for dutiesGive each user and service account only the privileged rights its duties need on systems, applications and data repositories, and nothing broader.
- E8-RA-ML3.2Use secure admin workstations for administrative tasksAdministrative activities must be performed from Secure Admin Workstations: privileged environments hardened and stripped back to only what administration needs.
- E8-RA-ML3.3Just-in-time administration is used for administering systems and applicationsAdminister systems and applications through just-in-time administration: admin rights are granted only when a task needs them and are gone once its time is up.
- E8-RA-ML3.4Memory integrity functionality is enabledMemory integrity, the Windows feature that checks drivers and other kernel code in an isolated environment before it can run, must be turned on and running.
- E8-RA-ML3.5Local Security Authority protection functionality is enabledTurn on LSA protection so LSASS, the Windows process holding sign-in credentials, runs as a protected process that other programs, even ones run by administrators, cannot read or alter.
- E8-RA-ML3.6Enable Credential Guard for secure credential storageTurn on Credential Guard so Windows keeps NTLM password hashes, Kerberos ticket-granting tickets and saved domain credentials in an isolated environment that malware with admin rights cannot read.
- E8-RA-ML3.7Enable Remote Credential Guard functionalityTurn on Remote Credential Guard so Remote Desktop sessions keep the user's credentials on the connecting device instead of sending them to the remote host.
- E8-RA-ML3.8Timely analysis of event logs from non-internet-facing serversEvent logs from servers the internet cannot reach directly, such as domain controllers, must be analysed in a timely manner to spot cyber security events.
- E8-RA-ML3.9Timely analysis of workstation event logs for security eventsEvent logs from workstations must be analysed in a timely manner to spot cyber security events, such as a privileged account signing in where it should not.
Back to the full ASD Essential Eight control list, or browse the complete control library.




