7.3.4.
Additional information relating to the management of ICT evidence is contained in:
Reference
ISO/IEC 27037:2012
Title
Publisher
Source
ISO
https://www.iso.org/standard/44381.
Information Technology –
Security Techniques – Guidelines
html
for identification, collection,
acquisition and preservation of
digital evidence.
HB 171:2003
Guidelines for the Management
Standards Australia
https://www.saiglobal.com/PDFTe
of Information Technology
mp/Previews/OSH/as/misc/handbook/
Evidence
HB171.PDF
The New Zealand Security
NCSC
https://www.ncsc.govt.nz/assets/N
Incident Management Guide for
Computer Security Incident
CSC-Documents/New-ZealandSecurity-Incident-Management-
Response Teams (CIRSTs)
Guide-for-Computer-SecurityIncident-Response-Teams-CSIRTs.pdf
Rationale & Controls
7.3.5.
Information security incident management documentation
7.3.5.R.01.
Rationale
Ensuring responsibilities and procedures for information security incidents are documented in relevant Information Security Documentation will
ensure that when an information security incident does occur, agency personnel can respond in an appropriate manner. In addition, ensuring
that system users are aware of reporting procedures will assist in identifying any information security incidents that an ITSM, or system owner
fail to notice.
7.3.5.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1260]
Agencies MUST detail information security incident responsibilities and procedures for each system in the relevant Information Security
Documents.
7.3.6.
Recording information security incidents
7.3.6.R.01.
Rationale
The purpose of recording information security incidents is to highlight the nature and frequency of information security incidents so that
corrective action can be taken. This information can subsequently be used as an input to security risk assessments of systems.
7.3.6.C.01.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1264]
Agencies SHOULD ensure that all information security incidents are recorded in a register.
7.3.6.C.02.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1266]
Agencies SHOULD use their incidents register as a reference for future security risk assessments.
7.3.7.
Handling data spills
7.3.7.R.01.
Rationale
A data spill is defined as the unauthorised or unintentional release, transmission or transfer of data. If there is a possibility that classified
information may be compromised as a result of an information security incident, agencies MUST be able to respond in a timely fashion to limit
damage and contain the incident.
7.3.7.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1271]
Agencies MUST implement procedures and processes to detect data spills.
7.3.7.C.02.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1273]
When a data spill occurs agencies MUST assume that data at the highest classification held on or processed by the system, has been
compromised.
7.3.7.C.03.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1274]
Agency SOPs MUST include procedure for:
all personnel with access to systems;
notification to the ITSM of any data spillage; and
notification to the ITSM of access to any data which they are not authorised to access.
7.3.7.C.04.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1275]
Agencies MUST document procedures for dealing with data spills in their IRP.
7.3.7.C.05.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1276]
Agencies MUST treat any data spill as an information security incident and follow the IRP to deal with it.
7.3.7.C.06.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1277]
When a data spill occurs agencies MUST report the details of the data spill to the information owner.
75
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents