Standard Time for a New
Measurement Standards Laboratory
Zealand Network
https://www.measurement.govt.nz/a
bout-us/official-new-zealandtime/about-time/
Rationale & Controls
16.6.6.
Maintaining system management logs
16.6.6.R.01.
Rationale
Having comprehensive information on the operations of a system can assist system administration, support information security and assist
incident investigation and management. In some cases forensic investigations will rely on the integrity, continuity and coverage of system
logs.
16.6.6.R.02.
Rationale
It will be impractical and costly to store all system logs indefinitely. An agency retention policy may consider:
Legislative and regulatory requirements;
Ensure adequate retention for operational support and efficiency;
Minimise costs and storage requirements; and
An adequate historical archive is maintained.
Care should be taken to ensure that these considerations are properly balanced.
Some practices dictate retention periods, for example good DNSSEC practice requires log information is stored in log servers for 4 months, then
archived and retained for at least 2 years.
16.6.6.C.01.
System Classification(s): Top Secret; Compliance: MUST
Control
[CID:1997]
Agencies MUST maintain system management logs for the life of a system.
16.6.6.C.02.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1998]
Agencies SHOULD determine a policy for the retention of system management logs.
16.6.7.
Content of system management logs
16.6.7.R.01.
Rationale
Comprehensive system management logs will assist in logging key management activities conducted on systems.
16.6.7.C.01.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:2001]
A system management log SHOULD record the following minimum information:
all system start-up and shutdown;
service, application, component or system failures;
maintenance activities;
backup and archival activities;
system recovery activities; and
special or out of hours activities.
16.6.8.
Logging requirements
16.6.8.R.01.
Rationale
Event logging can help raise the security posture of a system by increasing the accountability for all system user actions.
16.6.8.R.02.
Rationale
Event logging can increase the chances that malicious behaviour will be detected by logging the actions of a malicious party.
16.6.8.R.03.
Rationale
Well configured event logging allows for easier and more effective auditing and forensic examination if an information security incident occurs.
16.6.8.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:2006]
Agencies MUST develop and document logging requirements covering:
the logging facility, including:
log server availability requirements; and
the reliable delivery of log information to the log server;
the list of events associated with a system or software component to be logged; and
event log protection and archival requirements.
16.6.9.
Events to be logged
16.6.9.R.01.
Rationale
The events to be logged are key elements in the monitoring of the security posture of systems and contributing to reviews, audits,
investigations and incident management.
16.6.9.C.01.
223
ControlSystem Classification(s): Confidential, Secret, Top Secret; Compliance: MUST
[CID:2009]
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents