16.6.11. Event log facility 16.6.11.R.01. Rationale The act of logging events is not enough in itself. For each event logged, sufficient detail needs to be recorded in order for the logs to be useful when reviewed. An authoritative external time source, a local Time Source Master Clock or server or Co-ordinated Universal Time (UTC) is essential for the time-stamping of events and later inspection or forensic examination. The NZ Interoperability Framework (e-GIF) recognises the time standard for New Zealand as UTC (MSL), with Network Time Protocol (NTP) v.4 as the delivery method over the Internet. 16.6.11.R.02. Rationale New Zealand standard time is maintained by the Measurement Standards Laboratory of New Zealand (MSL), a part of Industrial Research Limited (IRL). New Zealand standard time is based on UTC, a worldwide open standard used by all modern computer operating systems. UTC (MSL) is kept within 200 nanoseconds of the international atomic time scale maintained by the Bureau International des Poids et Mesures (BIPM) in Paris. 16.6.11.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2017] For each event identified as needing to be logged, agencies MUST ensure that the log facility records at least the following details, where applicable: date and time of the event; relevant system user(s) or processes; event description; success or failure of the event; event source (e.g. application name); and IT equipment location/identification. 16.6.11.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:2018] Agencies SHOULD establish an authoritative time source. 16.6.11.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:2019] Agencies SHOULD synchronise all logging and audit trails with the time source to allow accurate time stamping of events. 16.6.12. Event log protection 16.6.12.R.01. Rationale Effective log protection and storage (possibly involving the use of a dedicated event logging server) will help ensure the integrity and availability of the collected logs when they are audited. 16.6.12.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2022] Event logs MUST be protected from: modification and unauthorised access; and whole or partial loss within the defined retention period. 16.6.12.C.02. ControlSystem Classification(s): Confidential, Secret, Top Secret; Compliance: MUST [CID:2023] Agencies MUST configure systems to save event logs to separate secure servers as soon as possible after each event occurs. 16.6.12.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:2024] Agencies SHOULD ensure that: systems are configured to save event logs to a separate secure log server; and event log data is archived in a manner that maintains its integrity. 16.6.13. Event log archives 16.6.13.R.01. Rationale It is important that agencies determine the appropriate length of time to retain DNS, proxy, event systems and other operational logs. Logs are an important information source in reviews, audits and investigations ideally these should be retained for the life of the system or longer. 16.6.13.R.02. Rationale The Archives, Culture, and Heritage Reform Act 2000, the Public Records Act 2005 and the Official Information Act 1982 may determine or influence the length of time that logs need to be retained and if they should be archived. 16.6.13.C.01. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2028] Event logs MUST be archived and retained for an appropriate period as determined by the agency. 16.6.13.C.02. ControlSystem Classification(s): All Classifications; Compliance: MUST [CID:2029] Disposal or archiving of DNS, proxy, event, systems and other operational logs MUST be in accordance with the provisions of the relevant legislation. 16.6.13.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:2030] Agencies SHOULD seek advice and determine if their logs are subject to legislation. 16.6.13.C.04. ControlSystem Classification(s): All Classifications; Compliance: SHOULD 225 [CID:2031] Version_3.5__January-2022

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents