Essential Eight AH-ML3.4 Analyse event logs from non-internet-facing servers for cyber threats
What it says
Event logs from non-internet-facing servers are analysed in a timely manner to detect cybersecurity events.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Analyse event logs from servers that cannot be reached from the internet, such as domain controllers and file servers, in a timely manner to detect cyber security events.
At Maturity Level Three, event logs from non-internet-facing servers must be analysed in a timely manner to detect cyber security events, meaning signs that something may be wrong. These are servers that cannot be reached directly from the internet, such as domain controllers, file servers and internal application servers. Under user application hardening, the logs include the PowerShell and command line process creation events that E8-AH-ML2.11 and E8-AH-ML2.12 require to be centrally logged. E8-AH-ML2.14 covers internet-facing servers. The statement sets no time limit, so the organisation decides what timely means.
Free. Save your status, tasks and notes.
Why it matters
Intruders who get inside often move to internal servers such as domain controllers, using PowerShell and command line tools there to take wider control. Timely analysis of these servers' logs gives a chance to notice that activity before it reaches the whole network.
How to implement
List every non-internet-facing server and connect its logs.
Compare the directory, virtualisation and cloud consoles and a network discovery scan with the log sources in your central logging platform. Connect any server that is missing; where a vendor-managed server cannot run your agent, use built-in Windows event forwarding or have the vendor send its logs.
Confirm the PowerShell and command line events arrive.
Check each server sends script block logging (event 4104), module logging (event 4103) and process creation events with command lines (event 4688), plus transcripts, as E8-AH-ML2.11 and E8-AH-ML2.12 require.
Write detection rules for misuse on these servers.
Look for encoded or obfuscated PowerShell, commands that download files, and administration tools run by accounts that do not normally use that server. Test that each rule fires.
Set and meet a time to analysis.
The statement sets no limit, so decide how quickly alerts from these servers are reviewed, sooner for domain controllers and other servers that control access, and measure the delay from the event itself, including log arrival. One process can serve the same requirement under other strategies (for example E8-AC-ML3.4).
Keep it running
Watch for servers that stop sending logs or send them late, and keep detection rules current. Recheck coverage whenever servers are built, migrated or retired, and after any incident on these servers that was found some other way.
Evidence and audit
- Check 1 of 3What an auditor asks for
Ask for
An independent list of non-internet-facing servers, such as from the directory, virtualisation consoles or a discovery scan, and the log sources in the central logging platform.
Look at
Whether every listed server sends PowerShell and command line process creation events, and whether any stopped sending during the period reviewed.
Good evidence
Every non-internet-facing server on the independent list, domain controllers included, is sending these events, and any server that stopped sending during the period was noticed and reconnected.
- Check 2 of 3What an auditor asks for
Ask for
A test on a sample of servers, including a domain controller, such as a harmless encoded PowerShell command run without warning the analysts.
Look at
Whether each test was detected and reviewed by an analyst, and how long that took from when it ran.
Good evidence
Every test was detected and reviewed by an analyst within the organisation's set time, measured from when it ran.
- Check 3 of 3What an auditor asks for
Ask for
Alert and review records for these servers over a recent period, and the incident register.
Look at
How long alerts waited, whether any were closed unread, and whether any incident on these servers was first found another way.
Good evidence
Alerts were reviewed within the set time with none closed unread, and no incident on these servers was first noticed by another route while its events sat unreviewed in the logs.
Mappings
Closest match in ASD Information Security Manual: ISM-1907, Timely analysis of non-internet-server logs, which asks for the same thing.
ISO/IEC 27001: 2 mappings
This control partially meets A.8.15.
E8-AH-ML3.4 requires organisations to analyse event logs from non-internet-facing servers in a timely manner to detect cyber security events. ISO/IEC 27001:2022 Annex A 8.15 is broader, requiring logs to be produced, stored, protected and analysed across activities, exceptions and faults for relevant events. E8-AH-ML3.4 maps to the 'analysed' component of Annex A 8.15 for a specific asset scope (non-internet-facing servers) and with an explicit timeliness/detection objective.
This control partially meets A.8.16.
E8-AH-ML3.4 requires timely analysis of event logs from non-internet-facing servers to detect cyber security events. ISO/IEC 27001:2022 Annex A 8.16 is broader, requiring monitoring of networks, systems and applications for anomalous behaviour and taking action to evaluate potential incidents. E8-AH-ML3.4 overlaps as a concrete log-analysis activity that supports anomalous behaviour detection, but Annex A 8.16 also covers other monitoring methods beyond log review.
ASD Information Security Manual: 9 mappings
This control is equivalent to ISM-1907.
E8-AH-ML3.4 requires event logs from non-internet-facing servers to be analysed in a timely manner to detect cyber security events. ISM-1907 states the same requirement for non-internet-facing server event logs and the same outcome (timely detection of cyber security events). The scope, asset type (non-internet-facing servers) and action (timely analysis) align closely between E8-AH-ML3.4 and ISM-1907.
This control partially meets ISM-1228.
E8-AH-ML3.4 requires timely analysis of event logs specifically from non-internet-facing servers to detect cyber security events. ISM-1228 is broader, requiring cyber security events to be analysed in a timely manner to identify incidents, without limiting to a particular log source or asset class. E8-AH-ML3.4 can be seen as a specific implementation path that contributes evidence and detection input into the broader analysis process described by ISM-1228.
This control partially overlaps ISM-1986.
E8-AH-ML3.4 requires event logs from non-internet-facing servers to be analysed in a timely manner to detect cyber security events. ISM-1986 also requires timely analysis of server logs, but it is scoped to 'critical servers' regardless of whether they are internet-facing or non-internet-facing. They overlap where critical servers are also non-internet-facing, but each control covers scenarios the other does not (non-critical non-internet-facing servers vs internet-facing critical servers).
This control partially overlaps ISM-2125.
ISM-2125 requires independent logging of service provider access and timely analysis to detect anomalous, unexpected or unauthorised activity. E8-AH-ML3.4 relates by requiring timely analysis of event logs from non-internet-facing servers, which may include systems accessed by service providers for administration. ISM-2125 additionally mandates that logging is controlled by the organisation and cannot be altered by the service provider, and it covers service provider access across systems, not only non-internet-facing servers.
This control depends on ISM-0120.
E8-AH-ML3.4 requires timely analysis of event logs from non-internet-facing servers to detect cyber security events. ISM-0120 ensures cyber security personnel have sufficient data sources and tools to monitor systems for key indicators of compromise, which directly enables effective log review and triage. Without the data access and tooling in ISM-0120, meeting the timeliness and detection intent of E8-AH-ML3.4 is likely impractical or incomplete.
This control depends on ISM-0988.
E8-AH-ML3.4 requires organisations to analyse event logs from non-internet-facing servers in a timely manner to detect cyber security events. ISM-0988 requires an accurate and consistent time source for event logging, which improves correlation, sequencing and incident reconstruction during log analysis. ISM-0988 does not require analysis itself, but it strengthens the reliability and usefulness of the analysis performed to satisfy E8-AH-ML3.4.
This control depends on ISM-1979.
E8-AH-ML3.4 requires event logs from non-internet-facing servers to be analysed in a timely manner to detect cyber security events. ISM-1979 requires security-relevant events for server applications on non-internet-facing servers to be centrally logged, which improves completeness and accessibility of log data for analysis. In practice, achieving timely, consistent analysis under E8-AH-ML3.4 is often dependent on the central logging capability mandated by ISM-1979, although E8-AH-ML3.4 can be performed with local logs at reduced effectiveness.
This control depends on ISM-2129.
ISM-2129 requires WMI activity, including permanent event subscriptions, to be centrally logged. E8-AH-ML3.4 requires timely analysis of event logs from non-internet-facing servers to detect cyber security events, and WMI logs materially improve detection of common attacker techniques on Windows servers.
- ISM-2132Central logging of certificate enrolment requests, template and AD CS configuration changesDepends on
This control depends on ISM-2132.
ISM-2132 requires that all certificate enrolment requests (successful and unsuccessful) and changes to certificate templates or AD CS configuration are centrally logged. This supports E8-AH-ML3.4 because AD CS typically runs on non-internet-facing servers and centralising these events ensures they are available for timely threat-focused log analysis.
ASD Essentials for enterprise IT: 2 mappings
This control partially overlaps IT.DET-03.1.
IT.DET-03.1 requires timely triage of alerts and events to decide whether cyber security incident thresholds are met; E8-AH-ML3.4 requires event logs from non-internet-facing servers to be analysed in a timely manner to detect cyber security events, an earlier step that feeds triage.
- IT.DET-04.1Continuously monitor software execution to detect malicious use of legitimate toolsPartially overlaps
This control partially overlaps IT.DET-04.1.
IT.DET-04.1 requires continuous monitoring and analysis of software execution to detect malicious use of legitimate tools; E8-AH-ML3.4 (user application hardening) requires timely analysis of event logs from non-internet-facing servers, a related detection duty.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




