Skip to content
Security assurance
ASD ISMISM-0580

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.

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

  1. Set out what is logged and where it goes.

    For each type of system, including cloud services, state which security-relevant events are logged, with the details ISM-0585 lists, and which centralised event logging facility receives them (ISM-1405).

  2. 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.

  3. 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.

  4. Get the policy approved and dated.

    Have the CISO approve it (ISM-0047) and mark it with a 'current as at' date (ISM-0888), so readers know which version is in force.

  5. 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

  1. 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.

  2. 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.

  3. 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.

  4. 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 27001

ISO/IEC 27001: 2 mappings

  • A.5.28Collection of evidencePartially overlaps
  • A.8.15LoggingPartially overlaps
Essential Eight

ASD Essential Eight: 14 mappings

Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.