Continuous monitoring plan
A continuous monitoring plan can assist an organisation in proactively identifying, prioritising and responding to
security vulnerabilities. Measures to monitor and manage security vulnerabilities in systems can also provide an
organisation with a wealth of valuable information about their exposure to cyber threats, as well as assisting them to
determine security risks associated with the operation of their systems. Undertaking continuous monitoring activities is
important as cyber threats and the effectiveness of security controls will change over time.
Three types of continuous monitoring activities are vulnerability assessments, vulnerability scans and penetration tests.
A vulnerability assessment typically consists of a review of a system’s architecture or an in-depth hands-on assessment
while a vulnerability scan involves using software tools to conduct automated checks for known security vulnerabilities.
In each case, the goal is to identify as many security vulnerabilities as possible. A penetration test however is designed
to exercise real-world scenarios in an attempt to achieve a specific goal, such as compromising critical system
components or data. Regardless of the continuous monitoring activities chosen, they should be conducted by suitably
skilled personnel independent of the system being assessed. Such personnel can be internal to an organisation or from
a third party. This ensures that there is no conflict of interest, perceived or otherwise, and that the activities are
undertaken in an objective manner.
Security Control: ISM-1163; Revision: 7; Updated: Dec-21; Applicability: All; Essential Eight: N/A
Systems have a continuous monitoring plan that includes:
conducting vulnerability scans for systems at least monthly
conducting vulnerability assessments or penetration tests for systems at least annually
analysing identified security vulnerabilities to determine their potential impact
using a risk-based approach to prioritise the implementation of mitigations based on effectiveness and cost.
Security assessment report
At the conclusion of a security assessment for a system, a security assessment report should be produced by the
assessor. This will assist the system owner in performing any initial remediation actions as well as guiding the
development of the system’s plan of action and milestones.
Security Control: ISM-1563; Revision: 0; Updated: May-20; Applicability: All; Essential Eight: N/A
At the conclusion of a security assessment for a system, a security assessment report is produced by the assessor and
covers:
the scope of the security assessment
the system’s strengths and weaknesses
security risks associated with the operation of the system
the effectiveness of the implementation of security controls
any recommended remediation actions.
Plan of action and milestones
At the conclusion of a security assessment for a system, and after the production of a security assessment report by the
assessor, a plan of action and milestones should be produced by the system owner. This will assist with tracking any of
the system’s identified weaknesses and recommended remediation actions identified during the security assessment.
Security Control: ISM-1564; Revision: 0; Updated: May-20; Applicability: All; Essential Eight: N/A
At the conclusion of a security assessment for a system, a plan of action and milestones is produced by the system
owner.
24
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents