Topic

Event log monitoring

Applicable to

all

History

Priority

must

Dec 2023

Event logs from workstations are analysed in a timely manner to detect cyber security events.

The existing control relating to analysing event logs in a timely manner to detect cyber security events was scoped to event logs from workstations.

Mar 2022

Event logs are analysed in a timely manner to detect cyber security events.

Miscellaneous changes were made to rationale and recommendations throughout the publication to clarify content without changing intent. This included a review from the Guidelines for System Hardening chapter through to the Guidelines for Data Transfers chapter.

Dec 2021

Event log auditing processes, and supporting event log auditing procedures, are developed and implemented covering the scope and schedule of audits, what constitutes a violation of security policy, and actions to be taken when violations are detected, including reporting requirements.

Miscellaneous changes were made to rationale and security controls throughout the publication. This included:

• A review from the Using the Information Security Manual chapter through to the Guidelines for Media chapter.

• Security controls suitable for all audiences have been identified with the ‘All’ applicability marking while additional security controls suitable for just government audiences have been identified with the O, P, S and TS applicability markings.

• Security controls suitable for specific classifications have been amended to include their classification(s) in the wording of the security controls to reduce the reliance on applicability markings to confer suitability.

• Tables in security controls have been converted into prose to allow for inclusion in the SSP annex template and the XML list of security controls.

• The use of ‘official’ and ‘highly classified’ terminology has been replaced with specific classifications to remove ambiguity.

• Security controls relating to high assurance ICT equipment have had their applicability narrowed to ‘S, TS’ reflecting that they are intended for the protection of SECRET and TOP SECRET systems and data.

Aug 2019

An event log auditing process, and supporting event log auditing procedures, is developed and implemented covering the scope and schedule of audits, what constitutes a violation of security policy, and actions to be taken when violations are detected, including reporting requirements.

Security control 0109 was modified to include a process for event log auditing.

Jul 2019

Event log auditing procedures are developed and implemented covering the scope and schedule of audits, what constitutes a violation of security policy, and actions to be taken when violations are detected, including reporting requirements.

2015

Agencies must develop, document and implement event log auditing requirements covering:• the scope of audits• the audit schedule• what constitutes a violation of information security policy• action to be taken when violations are detected• reporting requirements• specific responsibilities.

2010

Agencies must develop and document event log audit requirements covering:•••••the scope of auditsthe audit scheduleaction to be taken when violations are detectedreporting requirementsspecific responsibilities.

2008

Agencies must develop and document ICT security audit requirements reflecting the overall audit objectives derived from the ICTSP and SRMP, covering: a. the scope of ICT security audits b. the audit schedule c. action to be taken when violations are detected d. reporting requirements e. specific responsibilities.