ASD ISM 0580 Develop, implement and maintain a security monitoring policy
What it says
A security monitoring policy is developed, implemented and maintained.
Quoted as published. Everything else on this page is written by Control Stack.
In plain English
Write a security monitoring policy for how security-relevant event logs are collected and watched, put it into practice, and keep it up to date.
A security monitoring policy must be developed, implemented and maintained. The policy sets how security-relevant event logs, the records that systems keep of what happens on them, are collected and watched to detect malicious activity. In the ISM this applies to security-relevant logs only, not logs kept for performance. Implemented means logging and monitoring work as the policy says. Maintained means it is reviewed at least annually with a 'current as at' date (ISM-0888). The chief information security officer (CISO) approves it (ISM-0047). The control lists no required contents.
Free. Save your status, tasks and notes.
Why it matters
Without a policy, logging grows system by system: some security events go unrecorded, logs are kept too briefly to investigate, and nobody knows who watches them. A policy that is followed gives every system one approach, so malicious behaviour is likelier to be detected.
How to implement
Say how logs are watched and how long they are kept.
Name who analyses logs and cyber security events and how quickly, in line with the timely analysis ISM-0109 and similar controls require for logs and ISM-1228 for events. Set retention to meet ISM-1988 (searchable for at least 12 months) and the record-keeping minimums ISM-1989 sets.
Split monitoring duties with service providers.
For each cloud or managed service, record which logs the provider collects and monitors, which you collect yourself, and how alerts reach you. Where a contract cannot change, note what the provider will not supply and how you cover it.
Put the policy into effect on every system.
Configure each system's logging, forwarding and alert rules to match the policy, give each monitoring task a named owner, and check a sample of systems against the policy once setup is done.
Keep it running
Update the policy when a new type of system, logging facility or service provider is added, or an incident shows a gap in what was logged or watched, and refresh its 'current as at' date at each review.
Evidence and audit
- Check 1 of 4What an auditor asks for
Ask for
The current security monitoring policy, with its approval record and 'current as at' date.
Look at
Who approved it, when it was last reviewed, and whether it states what is logged and how logs are monitored in terms specific enough to test.
Good evidence
The CISO approved the policy, its 'current as at' date is within the last 12 months, and it states what is logged and how logs are monitored clearly enough to check a system against.
- Check 2 of 4What an auditor asks for
Ask for
A sample of systems drawn from a network discovery scan or cloud account inventory, with each one's logging settings and the centralised event logging facility's list of sources.
Look at
Whether each sampled system logs and forwards the security-relevant events the policy requires.
Good evidence
Every sampled system logs the events the policy requires and appears as an active source in the centralised event logging facility, with none missing.
- Check 3 of 4What an auditor asks for
Ask for
Monitoring records for a recent period, such as alert queues, triage notes and escalations, with the policy's monitoring requirements.
Look at
Whether monitoring happened as the policy describes, by the people it names and within the times it sets.
Good evidence
Records show monitoring carried out as the policy describes throughout the period, and every alert in the period was triaged within the time the policy sets.
- Check 4 of 4What an auditor asks for
Ask for
Change records, the service provider contract register and additions to the system inventory since the policy's last review.
Look at
Whether the policy reflects each change.
Good evidence
The policy matches the logging facility and service providers in use today and covers the systems added since its last review.
Mappings
Closest match in ASD Essential Eight: E8-AC-ML2.7, Event logs from internet-facing servers are analysed to detect cyber security events, which this control covers in full and more.
ISO/IEC 27001: 2 mappings
This control partially overlaps A.5.28.
ISM-0580 requires an organisation to develop, implement and maintain an event logging policy to ensure events are recorded and monitored. Annex A 5.28 establishes procedures for identification, collection, acquisition and preservation of evidence related to information security events, which commonly includes log handling and chain-of-custody considerations. ISM-0580 is broader for logging policy and monitoring, while Annex A 5.28 is narrower and incident/evidence-focused (forensic defensibility).
This control partially overlaps A.8.15.
ISM-0580 requires an organisation to develop, implement and maintain an event logging policy to ensure events are recorded and monitored. Annex A 8.15 requires logs to be produced, stored, protected and analysed, which aligns with the intent of monitoring and managing logging through policy. Annex A 8.15 is more explicit about technical outcomes (protection, storage and analysis), while ISM-0580 is specifically about establishing and maintaining the governing policy.
ASD Essential Eight: 14 mappings
- E8-AC-ML2.7Event logs from internet-facing servers are analysed to detect cyber security eventsBroader than
This control is broader than E8-AC-ML2.7.
ISM-0580 requires an organisation to develop, implement and maintain an event logging policy to ensure events are recorded and monitored. E8-AC-ML2.7 relies on that policy foundation to define expectations for collecting and reviewing logs from internet-facing servers to detect cyber security events. ISM-0580 is policy-governance focused, while E8-AC-ML2.7 is an operational detection activity with a specific scope (internet-facing servers) and timeliness requirement.
This control is broader than E8-AC-ML3.4.
E8-AC-ML3.4 requires timely analysis of event logs from non-internet-facing servers to detect cyber security events. ISM-0580 requires an event logging policy to be developed and maintained, which typically defines what is logged, retention, protection, review frequency and responsibilities that underpin 'timely' analysis. Without policy direction per ISM-0580, E8-AC-ML3.4 may be inconsistently implemented, though E8-AC-ML3.4 is more operational and asset-specific than the policy requirement.
This control is broader than E8-AH-ML2.14.
ISM-0580 requires an organisation to develop, implement and maintain an event logging policy to ensure events are recorded and monitored. E8-AH-ML2.14 mandates timely analysis of event logs from internet-facing servers to detect cyber security events, which is an implementation expectation that should be captured as procedures and performance requirements under the policy required by ISM-0580. ISM-0580 is governance across logging generally, while E8-AH-ML2.14 is a detection activity for a defined system class.
This control is broader than E8-AH-ML3.5.
E8-AH-ML3.5 requires timely analysis of workstation event logs to detect cyber security events. ISM-0580 requires an event logging policy to be developed, defining review frequencies, responsibilities, and escalation thresholds necessary for 'timely analysis'. E8-AH-ML3.5 is dependent on ISM-0580 to set operational rules for workstation log analysis.
This control is broader than E8-MF-ML2.6.
E8-MF-ML2.6 requires central logging of MFA success and failure events. ISM-0580 requires an event logging policy to be developed, implemented and maintained, which typically defines what authentication events must be captured, where they are sent, and how they are retained and reviewed. The policy underpins consistent implementation of E8-MF-ML2.6, but E8-MF-ML2.6 is more specific to MFA event capture than ISM-0580's governance focus.
This control is broader than E8-MF-ML2.8.
ISM-0580 requires an organisation to develop, implement and maintain an event logging policy to ensure events are recorded and monitored. E8-MF-ML2.8 requires timely analysis of logs from internet-facing servers, which is a specific monitoring practice that the ISM-0580 policy would direct and formalise (coverage, timeframes and accountability). ISM-0580 is not limited to internet-facing systems, whereas E8-MF-ML2.8 is scoped to that subset.
This control is broader than E8-RA-ML2.6.
E8-RA-ML2.6 requires one concrete measure, that privileged access events are captured in a central log rather than left on individual hosts. ISM-0580 requires a security monitoring policy to be developed, implemented and maintained, which sets out what the organisation monitors, which events it collects and retains, who reviews them and how those arrangements are kept current. Central logging of privileged access events is one practice such a policy would direct, so E8-RA-ML2.6 covers a single slice of ISM-0580 and says nothing about the policy itself or the rest of the monitoring it governs.
- E8-RA-ML2.9Timely analysis of internet-facing server event logs to detect security eventsBroader than
This control is broader than E8-RA-ML2.9.
ISM-0580 requires an organisation to develop, implement and maintain an event logging policy to ensure events are recorded and monitored. E8-RA-ML2.9 focuses on prompt analysis of event logs for security events, which is a monitoring and response expectation that should be defined (roles, frequency, SLAs) within the policy required by ISM-0580. ISM-0580 is broader governance, while E8-RA-ML2.9 is a specific operational analysis requirement.
This control is supported by E8-AC-ML2.5.
ISM-0580 requires an organisation to develop, implement and maintain an event logging policy to ensure events are recorded and monitored. E8-AC-ML2.5 specifies that application control allow/deny events are centrally logged, which is a concrete logging requirement that should be captured and driven by the policy in ISM-0580. ISM-0580 is broader and policy-oriented, while E8-AC-ML2.5 is a specific event source and centralisation requirement.
This control is supported by E8-AC-ML2.6.
E8-AC-ML2.6 requires organisations to ensure event logs cannot be modified or deleted by unauthorised users. ISM-0580 requires an event logging policy to be developed and maintained, which supports E8-AC-ML2.6 by formalising requirements for log access controls, retention, protection mechanisms and responsibilities. ISM-0580 is governance-focused and does not itself implement technical protections, so it complements rather than matches the Essential Eight requirement.
This control is supported by E8-AH-ML2.11.
ISM-0580 requires an organisation to develop, implement and maintain an event logging policy to ensure events are recorded and monitored. E8-AH-ML2.11 is a specific technical logging requirement (centralising PowerShell module, script block and transcription logs) that would normally be mandated and governed by the broader policy set by ISM-0580. ISM-0580 does not prescribe PowerShell-specific telemetry, whereas E8-AH-ML2.11 does.
This control is supported by E8-AH-ML2.12.
ISM-0580 requires an organisation to develop, implement and maintain an event logging policy to ensure events are recorded and monitored. E8-AH-ML2.12 mandates central logging of command line process creation events, a specific telemetry source that would typically be required and prioritised through the policy established by ISM-0580. ISM-0580 does not specify particular operating system event IDs or telemetry types, while E8-AH-ML2.12 does.
This control is supported by E8-MF-ML2.7.
E8-MF-ML2.7 requires event logs to be protected from unauthorised modification and deletion through appropriate technical and administrative controls. ISM-0580 requires an event logging policy to be developed and maintained, which can mandate and govern protections such as access restrictions, retention, and tamper-evident storage. ISM-0580 is policy/process oriented, while E8-MF-ML2.7 is a specific security outcome focused on log integrity controls.
This control is required by E8-RA-ML2.7.
E8-RA-ML2.7 requires privileged account and group management events to be centrally logged. ISM-0580 requires an event logging policy to be developed, implemented and maintained, which typically defines what privileged account and group management events must be captured and where they are sent. Without the policy control in ISM-0580, implementation of E8-RA-ML2.7 is more likely to be inconsistent or incomplete across systems.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




