Skip to content
Cyber security roles
ASD ISMISM-1526

ASD ISM 1526 System owners continuously monitor security and manage threats, risks and controls

What it says

System owners continuously monitor the security of each system, and manage associated cyber threats, security risks and security controls.

Quoted as published. Everything else on this page is written by Control Stack.

In plain English

System owners must continuously monitor the security of each system, and manage the cyber threats, security risks and security controls associated with it.

System owners must continuously monitor the security of each system, and manage the cyber threats, security risks and security controls associated with it. Continuously means monitoring is ongoing for as long as the system operates, rather than occasional checks or work done only around an assessment or authorisation. Managing means acting on what the monitoring shows: reassessing risks when threats change, and fixing or adjusting controls that fall short. ISM-1163 separately requires each system to have a continuous monitoring plan covering vulnerabilities.

Why it matters

An authorisation reflects a system's threats, risks and controls at one point in time. Without continuous monitoring, a new threat or failed control can go unseen while the system keeps operating on a security picture that is out of date.

How to implement

  1. Set out what to watch for each system.

    Start from its threat and risk assessment (ISM-1203), system security plan (ISM-0041) and continuous monitoring plan (ISM-1163). For each threat and risk, and each group of controls, name the signal that would show a change, such as a threat advisory, scan result, event log alert or configuration check.

  2. Connect each system to those signals.

    Use vulnerability scanning, the centralised event logging facility (ISM-1405), configuration checks and threat advisories. A security team can run these, but results must reach the system owner. For a bought service, use the provider's dashboards, logs, notices and assurance reports, and record what you cannot see as a risk.

  3. Keep a current risk record for each system.

    List each threat, risk and control issue with its rating, treatment, responsible person and due date. Update it when a signal arrives, rather than waiting for the next assessment.

  4. Act on what the monitoring shows.

    Fix controls that have failed and treat risks that have grown. Where the selected controls no longer fit, change them in consultation with the authorising officer (ISM-1634). Carry assessment findings into the plan of action and milestones (ISM-1564).

Keep it running

Recheck what feeds each system's monitoring whenever a component, integration, hosting arrangement or system owner changes. The results also feed the report to the authorising officer due at least annually (ISM-1587).

Evidence and audit

  1. Check 1 of 4What an auditor asks for

    Ask for

    The register of systems (ISM-1966), an asset discovery scan and the monitoring records for each system.

    Look at

    Whether every system on the register or found by the scan has a named system owner and monitoring results from the current period.

    Good evidence

    Every system on the register or found by the scan has a named system owner and current monitoring results, and none sits outside monitoring.

  2. Check 2 of 4What an auditor asks for

    Ask for

    One sampled system's monitoring outputs for the whole period since its last assessment or authorisation.

    Look at

    Whether scan results, log alerts and reviews run without gaps, or bunch just before assessment or authorisation dates.

    Good evidence

    Monitoring outputs run through the whole period without an unexplained gap, including the stretch furthest from any assessment or authorisation.

  3. Check 3 of 4What an auditor asks for

    Ask for

    A recent threat advisory or disclosed vulnerability affecting a sampled system's technology, chosen by the auditor from an outside source, with that system's risk record.

    Look at

    Whether the threat was assessed for that system, and the dates of the assessment and any resulting decision.

    Good evidence

    The risk record shows a dated assessment of that threat for this system with a resulting decision, and any control change decided on has been made.

  4. Check 4 of 4What an auditor asks for

    Ask for

    A control found weak or failed in a sampled system's latest security control assessment, vulnerability scan or incident, with the record of what followed.

    Look at

    Whether the finding reached the system owner, and whether it was fixed or a risk decision recorded by the date set.

    Good evidence

    The system owner knew of the finding, and the control was fixed, or a decision on the remaining risk recorded, by the date set in the risk record or plan of action and milestones.

Mappings

Closest match in ISO/IEC 27001: A.8.8, Management of technical vulnerabilities, which this control covers in full and more.

ISO 27001

ISO/IEC 27001: 4 mappings

  • A.8.16Monitoring activitiesBroader than
  • A.5.7Threat intelligenceSupports
  • A.8.15LoggingSupports
Essential Eight

ASD Essential Eight: 6 mappings

ASD Essentials

ASD Essentials for enterprise IT: 7 mappings

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