System
Classification(s):
All Classifications; Compliance: SHOULD
6.1.7.C.01.
Control
[CID:1040]
Agencies SHOULD undertake and document information security reviews of their systems at least annually.
6.1.8.
Managing Conflicts of Interest
6.1.8.R.01.
Rationale
Reviews may be undertaken by personnel independent of the target of evaluation or by an independent third party to ensure that there is no
(perceived or actual) conflict of interest and that an information security review is undertaken in an objective manner.
6.1.8.C.01.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1043]
Agencies SHOULD have information security reviews conducted by personnel independent to the target of the review or by an independent
third party.
6.1.9.
Focus of information security reviews
6.1.9.R.01.
Rationale
Incidents, significant changes or an aggregation of minor changes may require a security review to determine and support any necessary
changes and to demonstrate good systems governance. An agency may choose to undertake an information security review:
as a result of a specific information security incident;
because a change to a system or its environment that significantly impacts on the agreed and implemented system architecture and
information security policy; or
as part of a regular scheduled review.
6.1.9.R.02.
Rationale
In order to review risk, an information security review should analyse the threat environment and the highest classification of information that
is stored, processed or communicated by that system.
6.1.9.R.03.
Rationale
Depending on the scope and subject of the information security review, agencies may gather information on areas including:
agency priorities, business requirements and/or concept of operations;
threat data;
risk likelihood and consequence estimates;
effectiveness of existing counter-measures;
other possible counter-measures;
changes to standards, policies and guidelines;
recommended good practices; and
significant system incidents and changes.
6.1.9.C.01.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1048]
Agencies SHOULD review the components detailed in the table below. Agencies SHOULD also ensure that any adjustments and changes as a
result of any vulnerability analysis are consistent with the vulnerability disclosure policy.
Component
Review
Information security
The SecPol, Systems Architecture, SRMPs, SSPs, SitePlan, SOPs, the VDP, the IRP, and any third party assurance
documentation
reports.
Dispensations
Prior to the identified expiry date.
Operating environment
When an identified threat emerges or changes, an agency gains or loses a function or the operation of functions
are moved to a new physical environment.
Procedures
After an information security incident or test exercise.
System security
Items that could affect the security of the system on a regular basis.
Threats
Changes in threat environment and risk profile.
NZISM
Changes to baseline or other controls, any new controls and guidance.
6.2. Vulnerability Analysis
Objective
6.2.1.
Exploitable information system weaknesses can be identified by vulnerability analyses and inform assessments and controls selection.
Context
Scope
6.2.2.
This section covers information on conducting vulnerability assessments on systems as part of the suite of good IT governance activities.
Changes as a result of a vulnerability analysis
6.2.3.
64
It is important that normal change management processes are followed where changes are necessary in order to address security risks identified in a
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents