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.
Free. Save your status, tasks and notes.
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
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.
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.
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.
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
- 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.
- 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.
- 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.
- 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/IEC 27001: 4 mappings
This control is broader than A.8.8.
ISM-1526 requires system owners to continuously monitor security and manage cyber threats, security risks and security controls over time. Annex A 8.8 requires obtaining information about technical vulnerabilities, evaluating exposure, and taking appropriate measures, which is a core component of ongoing risk/control management. They overlap strongly in vulnerability-driven monitoring and remediation, but ISM-1526 is broader as it also covers non-vulnerability threats and overall continuous security posture management beyond technical vulnerabilities.
This control is broader than A.8.16.
ISM-1526 requires system owners to continuously monitor the security of each system and to manage the associated cyber threats, security risks and security controls. Annex A 8.16 requires networks, systems and applications to be monitored for anomalous behaviour, with appropriate action taken to evaluate potential information security incidents. The monitoring in Annex A 8.16 is one part of the wider ownership and management duty ISM-1526 sets.
This control supports A.5.7.
ISM-1526 requires system owners to monitor each system and its associated cyber threats, security risks and controls on an ongoing basis. ISO/IEC 27001:2022 Annex A 5.7 supports this by requiring the collection and analysis of threat information to produce threat intelligence that can feed system threat/risk monitoring. The ISM control is broader and governance-focused, while Annex A 5.7 is specifically about producing threat intelligence as an input.
This control supports A.8.15.
ISM-1526 requires system owners to continuously monitor system security and manage cyber threats, risks and controls for each system. ISO/IEC 27001:2022 Annex A 8.15 supports this by requiring logs to be produced, protected and analysed, enabling the monitoring evidence and detection capability owners rely on. Annex A 8.15 is focused on logging controls, whereas ISM-1526 also includes defining boundaries/objectives and overarching risk ownership.
ASD Essential Eight: 6 mappings
This control is broader than E8-PA-ML1.4.
ISM-1526 requires system owners to continuously monitor system security and actively manage cyber threats, security risks and controls throughout operations. E8-PA-ML1.4 fits within this by mandating at least weekly vulnerability scanning to find missing patches in key software, which is an ongoing monitoring activity that informs risk/control management. ISM-1526 is broader because it covers continuous monitoring and management across the full threat/risk/control set, not just patch-related vulnerability scanning.
- 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-1526 requires system owners to monitor the security of each system continuously and to manage the associated cyber threats, security risks and security controls. E8-RA-ML2.9 covers one part of that work, timely analysis of event logs from internet-facing servers to detect cyber security events, so the narrower log analysis duty sits inside the continuous monitoring ISM-1526 requires.
This control supports E8-AC-ML2.8.
ISM-1526 requires system owners to continuously monitor system security and manage cyber threats and risks for each system. E8-AC-ML2.8 supports this requirement by ensuring cyber security events are analysed in a timely manner to identify incidents, which is a core input to continuous monitoring and risk treatment decisions. E8-AC-ML2.8 focuses on operational incident detection/triage, whereas ISM-1526 also covers boundary/objective setting and overall control governance.
This control supports E8-AH-ML2.15.
ISM-1526 requires ongoing monitoring of systems and associated cyber threats, security risks and controls by system owners. ASD Essential Eight E8-AH-ML2.15 supports this by requiring timely analysis of cyber security events to identify incidents, which is a key operational activity within continuous monitoring. ISM-1526 is broader in scope, while E8-AH-ML2.15 focuses specifically on event analysis for incident identification.
This control supports E8-MF-ML2.9.
ISM-1526 requires system owners to continuously monitor each system's security and manage associated threats, risks and controls within defined system boundaries and objectives. E8-MF-ML2.9 supports this by requiring timely analysis of cyber security events so the monitoring activity results in incident identification and action. ISM-1526 is broader and governance-focused (ownership, boundaries, objectives and risk management), while E8-MF-ML2.9 is a specific operational monitoring/analysis outcome.
This control supports E8-RA-ML2.10.
ISM-1526 requires system owners to monitor systems and associated cyber threats and risks on an ongoing basis. ASD Essential Eight E8-RA-ML2.10 supports this by requiring timely analysis of cyber security events to identify incidents, which is a concrete monitoring-and-detection activity. ISM-1526 extends beyond event analysis to include broader security risk and control monitoring responsibilities.
ASD Essentials for enterprise IT: 7 mappings
This control is broader than IT.GOV-14.1.
IT.GOV-14.1 requires legacy and unsupported technology risks to be treated with compensating controls, enhanced monitoring and assurance; ISM-1526 is broader, with system owners continuously monitoring each system's security and managing its threats, risks and controls.
- IT.DET-05.1Periodically review detection coverage for gaps as assets, services and architecture changePartially overlaps
This control partially overlaps IT.DET-05.1.
IT.DET-05.1 requires periodic reviews of detection coverage to find gaps from new assets, services or architectural changes; ISM-1526 requires system owners to continuously monitor each system's security and manage its threats, risks and controls, a broader duty those reviews support.
- IT.GOV-03.1Assess and treat cyber security risks using an approved methodology and planPartially overlaps
This control partially overlaps IT.GOV-03.1.
IT.GOV-03.1 requires an approved risk management methodology and plan to be established and maintained and used to assess and treat cyber security risks. ISM-1526 requires system owners to continuously monitor the security of each system and manage the associated cyber threats, security risks and security controls. Both address cyber security risk, yet only IT.GOV-03.1 asks for the methodology and plan, and only ISM-1526 assigns continuous monitoring to system owners.
- IT.IDE-04.1Identify relevant weaknesses and threat behaviours for risk assessments, reviewing them continuouslyPartially overlaps
This control partially overlaps IT.IDE-04.1.
IT.IDE-04.1 requires risk assessments to consider relevant weaknesses, malicious actor techniques and threat behaviours, reviewed continuously; ISM-1526 overlaps on ongoing review, with system owners continuously monitoring each system's security and managing its cyber threats and risks.
- IT.PRO-04.3Detect and respond to configuration drift using scheduled assessments and monitoringPartially overlaps
This control partially overlaps IT.PRO-04.3.
IT.PRO-04.3 requires detecting and responding to configuration drift via scheduled assessments and, where supported, automated monitoring; ISM-1526 sets the broader duty that system owners continuously monitor each system's security and manage its threats, risks and controls.
- IT.RES-04.1Perform post-incident reviews to identify security gaps behind each incident stagePartially overlaps
This control partially overlaps IT.RES-04.1.
IT.RES-04.1 requires post-incident reviews to identify the security gaps that enabled each stage of an incident; ISM-1526 requires system owners to continuously monitor each system's security and manage its threats, risks and controls, which the gaps found can inform.
- IT.RES-04.2Evaluate monitoring coverage and response procedures after cyber security incidentsPartially overlaps
This control partially overlaps IT.RES-04.2.
IT.RES-04.2 requires monitoring coverage and incident response procedures to be evaluated after incidents; ISM-1526 requires system owners to continuously monitor each system's security and manage its threats, risks and controls, the monitoring whose coverage that evaluation checks.
Mappings show how controls relate across frameworks. They do not imply full equivalence or certification.




