7.2.20.C.01.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1220]
Agencies SHOULD report information security incidents categorised asLow to the NCSC.
7.2.21.
How to report information security incidents to National Cyber Security Centre (NCSC)
7.2.21.R.01.
Rationale
Reporting of information security incidents to the NCSC through the appropriate channels ensures that appropriate and timely assistance can
be provided to the agency. In addition, it allows the NCSC to maintain an accurate threat environment picture for government systems.
7.2.21.R.02.
Rationale
To simplify the reporting of information security incidents to the NCSC, a Cyber Security Incident – Report Form is provided on the NCSC website
under Reporting an Incident at https://www.ncsc.govt.nz/
7.2.21.C.01.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1223]
Agencies SHOULD formally report information security incidents using the NCSC on-line reporting form.
7.2.22.
Outsourcing and information security incidents
7.2.22.R.01.
Rationale
In the case of outsourcing of information technology services and functions, the agency remains responsible for the reporting of all information
security incidents. This includes any outsourced cloud services used by the agency. As such, the agency MUST ensure that the service
provider informs them of all information security incidents to enable them to assess the incident and provide formal reporting.
7.2.22.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1226]
Agencies that outsource their information technology services and functions MUST ensure that the service provider advises and consults with
the agency when an information security incident occurs.
7.2.23.
Cryptographic keying material
7.2.23.R.01.
Rationale
Reporting any information security incident involving the loss or misuse of cryptographic keying material is particularly important. Systems
users in this situation are those that rely on the use of cryptographic keying material for the confidentiality and integrity of their secure
communications.
7.2.23.R.02.
Rationale
It is important to note that a loss or compromise of keying material is aCritical or Serious information security incident and strict procedures
must be followed to minimise the impact of the incident.
7.2.23.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1233]
Agencies MUST notify all system users of any suspected or confirmed loss or compromise of keying material.
7.2.24.
Replacement of Cryptographic Key (HACE) keying material
7.2.24.R.01.
Rationale
If an encryption key is compromised, there is no need to attack the algorithm itself and it is a trivial matter to decrypt any encrypted data. This
is why strong key management is vital in order to protect the encryption keying materials. If a compromise of keying materials is known or
even suspected, the cryptographic key must be replaced as a matter of urgency and measures taken to reduce the impact of the key
compromise. See also Section 17.9 – Key Management.
7.2.24.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:6592]
Agencies MUST replace compromised cryptographic keys as a matter of urgency and record the replacement in the incident reporting.
7.2.25.
High Assurance Cryptographic Equipment (HACE) keying material
7.2.25.R.01.
Rationale
For information security incidents involving the suspected loss or compromise of HACE keying material, GCSB will investigate the possibility of
compromise, and where possible, initiate action to reduce the impact of the compromise.
7.2.25.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1237]
Agencies MUST urgently notify GCSB of any suspected loss or compromise of keying material associated with HACE.
7.3. Managing Information Security Incidents
Objective
7.3.1.
To identify and implement processes for incident identification, management and analysis of information security incidents, including selection of
appropriate remedies which will assist in preventing or reducing the impact of future information security incidents.
Context
Scope
7.3.2.
This section covers information relating primarily to managing information security incidents. The management of physical and personnel security
incidents is considered to be out of scope unless it directly impacts on the protection of systems (e.g. the breaching of physical protection for a server
room).
7.3.3.
It is important to note that, in most cases, information systems are likely to be affected.
References
74
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents