Cybernion
← Insights

IRAP

IRAP Continuous Monitoring Plan Explained

3 July 2026 · Updated 3 July 2026

The Continuous Monitoring Plan (CMP) describes how a system’s security posture is watched and maintained after an IRAP assessment. It is one of the minimum artefacts in the authorisation package, and it lets an authorising officer keep residual risk within appetite between assessments. It maintains posture; it does not replace the reassessment cloud providers still owe within 24 months.

An IRAP assessment ends, the authorisation begins, and the system keeps running. The Continuous Monitoring Plan is what stops that authorisation going stale, a required part of the authorisation package and a live document, not a filing exercise.

What is a Continuous Monitoring Plan?

A Continuous Monitoring Plan describes how a system’s security posture is monitored and maintained once it is operating under authorisation. It is one of the artefacts ASD’s consumer guidance lists in the authorisation package, alongside the system security plan, the incident response plan, the security assessment report, the control matrix and any plan of action and milestones.

Its job is to give the authorising officer confidence that the controls assessed as effective stay effective. An IRAP assessment is a point in time evaluation. The plan is how the security posture is kept under watch in the long stretch between one assessment and the next, so that residual risk stays within the appetite the officer accepted at authorisation. For the wider picture, see the complete guide to IRAP assessment and maintaining IRAP posture between assessments.

Why does an IRAP authorisation need continuous monitoring?

Because nothing about the system stands still once the assessment is done. Three things move at once.

  • The system changes, through patches, new features, new integrations and staff turnover
  • The ISM updates quarterly, adding, retiring and reworking controls
  • The threat environment shifts, and a control that was adequate can stop being so

Continuous monitoring is how those movements are caught and managed rather than discovered at the next assessment. Without it, the gap between what was assessed and what is running widens quietly, and the authorisation rests on a picture that is increasingly out of date. The ISM itself frames ongoing monitoring of a system’s environment, as set out in a continuous monitoring plan, as essential to maintaining its security posture.

What should a Continuous Monitoring Plan (CMP) cover?

The plan should describe the activities that keep posture stable and who is responsible for them. There is no single template that fits every system, but the substance covers the controls and conditions most likely to drift.

Area What the plan describes
Technical hygiene How patching, configuration baselines and vulnerability management are monitored and how drift is caught
Access and identity How access reviews and privileged activity are checked over time
Logging and detection How monitoring outputs are reviewed and how detection capability is kept effective
ISM currency How each quarterly ISM release is reviewed against the control set for new or changed controls
System change How material changes are identified and assessed against the assessment boundary
Governance Who reviews the plan, how often, and how findings are escalated and accepted

The plan should be live. If monitoring activity has drifted from what the plan describes, either update the plan or reinstate the activity. An authorising officer who reads a monitoring plan that has not been operating as written will have questions.

Does IRAP continuous monitoring replace reassessment?

No. This is the line organisations most often blur. Continuous monitoring maintains the authorisation between assessments, but it does not reset the clock. Under the Protective Security Policy Framework (PSPF), Requirement 0109, cloud service providers must have had an IRAP assessment within the previous 24 months against the latest ISM at the time of assessment. Monitoring keeps the authorisation credible in that window; it is not a substitute for the reassessment itself.

Monitoring and reassessment reinforce each other. The historical evidence a good monitoring regime accumulates, patching records, access reviews, monitoring outputs, ISM delta reviews, is exactly what makes the next assessment shorter and more confident. An organisation reconstructing evidence in the weeks before an assessment has a harder time of it than one that kept records the whole way through.

How do we keep a Continuous Monitoring Plan working?

Tie the plan to two triggers, scheduled periodic review and event based review on any material change, and keep a change log so the next assessment sees what changed and when. The plan is one of the documents that must stay current throughout the authorisation, not a static artefact from the last assessment. The System Security Plan and the IRAP Common Assessment Framework define the other artefacts it stands alongside.

For help building a continuous monitoring plan an authorising officer will accept, Cybernion provides IRAP assessments and readiness.

Frequently asked questions

What is a Continuous Monitoring Plan in IRAP?

A Continuous Monitoring Plan describes how a system’s security posture is watched and maintained after an IRAP assessment. It is one of the artefacts in the authorisation package, and it supports ongoing authorisation by showing an authorising officer how controls are kept effective between assessments.

Why does an IRAP authorisation need continuous monitoring?

Because an IRAP assessment is point in time and the authorisation that follows is not. The system keeps operating, the ISM updates quarterly, and the threat environment moves. Continuous monitoring is how residual risk is kept within appetite between assessments rather than only being checked at the next assessment.

Is the Continuous Monitoring Plan part of the authorisation package?

Yes. ASD’s consumer guidance lists a continuous monitoring plan among the minimum artefacts in an authorisation package, alongside the system security plan, incident response plan, security assessment report, control matrix and any plan of action and milestones.

Does IRAP continuous monitoring replace reassessment?

No. Continuous monitoring maintains posture between assessments, but cloud service providers must still have an IRAP assessment within the previous 24 months against the latest ISM under PSPF Requirement 0109. Monitoring keeps the authorisation credible, it does not reset the reassessment clock.

What should an IRAP Continuous Monitoring Plan actually monitor?

The controls and conditions that keep the system’s posture stable, such as patching, access reviews, logging and monitoring outputs, configuration drift, ISM changes each quarter and material system changes. If monitoring drifts from what the plan describes, either the plan or the activity needs to be brought back into line.


Written by Gaurav Vikash, an ASD endorsed IRAP assessor and senior cyber security leader with 18 years of experience across Australia, the UK and Asia, including CISO and senior security leadership roles. He holds CISSP, CISA, CISM and CRISC and is an ISO 27001 Lead Auditor and ISO 42001 Lead Implementer, and speaks regularly at industry conferences.

Talk to us.

Sources:

  1. IRAP Consumer Guide, Australian Signals Directorate, July 2025
  2. Information Security Manual, cyber.gov.au, June 2026
  3. Cloud assessment and authorisation, including PSPF Requirement 0109, cyber.gov.au, 2026
  4. IRAP Common Assessment Framework, Australian Signals Directorate, April 2025

Last updated: 3 July, 2026

Related serviceIRAP AssessmentSee the service →

Talk to us about your engagement

A scoped proposal within one business day.