ASD ISM 0109 Timely analysis of workstation event logs
What it says
Event logs from workstations are analysed in a timely manner to detect cyber security events.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Analyse event logs from every workstation soon enough to act on what they show, detecting cyber security events such as malware running or a stolen account in use.
Event logs from workstations must be analysed in a timely manner to detect cyber security events (signs of a possible security policy breach or failed safeguard). A workstation is a single-user computer, including a laptop running a desktop operating system. Only security-relevant logs count, not performance logs. Analysis can combine automated rules and analyst review, but storing logs is not analysing them. The control sets no time, so the organisation decides what timely means, based on how quickly a compromise could spread from a workstation.
Free. Save your status, tasks and notes.
Why it matters
Workstations are often where an intrusion starts, through a malicious attachment, a download or a stolen password. Prompt analysis of their logs can reveal that first foothold, such as an unexpected program or logon, before an attacker reaches servers and data.
How to implement
Confirm every workstation sends its security-relevant logs centrally.
Compare the endpoint management inventory with the sources in the centralised event logging facility (ISM-1405), covering laptops often off the network and every operating system in use. ISM-0582, ISM-1976 and ISM-1977 require central logging of operating system security-relevant events.
Write detection rules for signs of workstation compromise.
Cover security product alerts, new services and scheduled tasks, unusual script and command line activity (centrally logged under ISM-1623 and ISM-1889), blocked application control events (centrally logged under ISM-1660), bursts of failed logons, logons at odd times or from unexpected places, and cleared event logs.
Set a target time and analyse every alert against it.
Base the target on how fast a compromise could spread, decide how alerts at night and on weekends are handled, record each outcome, and pass events on for the incident analysis ISM-1228 requires. Where a provider does the analysis, write the target into its service terms.
Test detection with harmless simulated activity.
On a sample of workstations, use a burst of failed logons or a test scheduled task, not just an antivirus test file, then measure how long detection and analysis took and fix any gap.
Keep it running
Alert when a workstation stops sending logs, and add new operating systems and builds to the detection rules before they are deployed. Revisit the rules after an incident, a penetration test or a new attack technique reported by threat intelligence.
Evidence and audit
- Check 1 of 3What an auditor asks for
Ask for
The endpoint management inventory, network access records such as DHCP or VPN logs, and the list of log sources in the centralised event logging facility.
Look at
Whether every workstation, including laptops and each operating system in use, sends security-relevant logs that detection rules or analysts read.
Good evidence
Every workstation in either record is a log source with recent events and is covered by detection rules, with no group, such as remote laptops or one operating system, left out.
- Check 2 of 3What an auditor asks for
Ask for
Harmless test events on workstations the auditor picks, raised without warning to the monitoring team and including one outside business hours, such as a burst of failed logons or a test scheduled task, not just an antivirus test file.
Look at
Whether each event was detected and analysed, by whom, and how long it took.
Good evidence
Each test event was detected and analysed, with the time from event to analysis recorded and within the organisation's target, including one raised outside business hours.
- Check 3 of 3What an auditor asks for
Ask for
Read access to a recent period's workstation logs, so the auditor can search for clear signs of compromise such as cleared event logs, and incident register entries involving workstations with their occurrence and discovery dates (ISM-1803).
Look at
Whether each sign the search finds was alerted and analysed at the time, and how each incident was first found.
Good evidence
Every sign the search finds has an alert analysed at the time, and no workstation incident was first reported by a user or an outside party while its signs sat unexamined in the logs.
Mappings
Closest match in ASD Essential Eight: E8-AC-ML3.5, Workstation event logs are promptly analysed for security events, which asks for the same thing.
ISO/IEC 27001: 1 mapping
This control partially meets A.8.15.
ISM-0109 requires event logs from workstations to be analysed in a timely manner to detect cyber security events. This implements the analysis element of Annex A 8.15 for one class of system. Annex A 8.15 is broader, requiring logs of activities, exceptions, faults and other events to be produced, stored, protected and analysed across all systems.
ASD Essential Eight: 5 mappings
This control is equivalent to E8-AC-ML3.5.
ISM-0109 requires event logs from workstations to be analysed in a timely manner to detect cyber security events. E8-AC-ML3.5 contains the same requirement word for word as part of Essential Eight Maturity Level Three. Implementing one satisfies the other, although E8-AC-ML3.5 sits within the application control strategy, so the analysis would be expected to cover allowed and blocked execution events.
This control is equivalent to E8-AH-ML3.5.
ISM-0109 requires event logs from workstations to be analysed in a timely manner to detect cyber security events. E8-AH-ML3.5 contains the same requirement word for word as part of Essential Eight Maturity Level Three. Implementing one satisfies the other, although E8-AH-ML3.5 sits within the user application hardening strategy, so the analysis would be expected to cover application-related events.
This control is equivalent to E8-MF-ML3.5.
ISM-0109 requires event logs from workstations to be analysed in a timely manner to detect cyber security events. E8-MF-ML3.5 contains the same requirement word for word as part of Essential Eight Maturity Level Three. Implementing one satisfies the other, although E8-MF-ML3.5 sits within the multi-factor authentication strategy, so the analysis would be expected to cover authentication-related events.
This control is equivalent to E8-RA-ML3.9.
ISM-0109 requires event logs from workstations to be analysed in a timely manner to detect cyber security events. E8-RA-ML3.9 contains the same requirement word for word as part of Essential Eight Maturity Level Three. Implementing one satisfies the other, although E8-RA-ML3.9 sits within the restrict administrative privileges strategy, so the analysis would be expected to cover privileged activity.
This control supports E8-AH-ML2.15.
ISM-0109 requires event logs from workstations to be analysed in a timely manner to detect cyber security events. Detecting events from workstation logs feeds directly into E8-AH-ML2.15, which requires cyber security events to be analysed in a timely manner to identify cyber security incidents. ISM-0109 is limited to workstation log analysis for event detection, while E8-AH-ML2.15 covers the subsequent triage of events into incidents.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




