implementing new systems that necessitate changes to existing systems;
identifying new tasks or functionality requiring updates or new systems;
organisational change;
business process or concept of operation change;
standards evolution;
government policy or Cabinet directives;
threat or vulnerability identification and notifications recieved or issued; and
other incidents or continuous improvement activities.
Types of system change
6.3.4.
A proposed change to a system could involve:
an upgrade to, or introduction of IT equipment;
an upgrade to, or introduction of software;
environment or infrastructure change; or
major changes to access controls.
PSR references
6.3.5.
Relevant PSR requirements can be found at:
Reference
Title
Source
PSR Mandatory
GOV3, INFOSEC1, INFOSEC2,
http://www.protectivesecurity.govt.nz
Requirements
INFOSEC3 and INFOSEC4
https://www.protectivesecurity.govt.nz/governance/mandatory-requirements-2/
https://www.protectivesecurity.govt.nz/information-security/mandatory-requirements-2/
PSR content
Management protocol for
protocols
information security
https://www.protectivesecurity.govt.nz/information-security/management-protocol/
PSR requirements
Self assessment & reporting
https://www.protectivesecurity.govt.nz/self-assessment-and-reporting/
sections
Implement your information security
https://www.protectivesecurity.govt.nz/physical-security/understand-the-physical-security-
measures
Maintain your business
lifecycle/implement-2/
https://www.protectivesecurity.govt.nz/governance/business-continuity-
continuity programme
management/maintain-your-business-continuity-programme/
Rationale & Controls
6.3.6.
Change management
6.3.6.R.01.
Rationale
A considered and accountable process requires consultation with all stakeholders before any changes are implemented. In the case of changes
that will affect the security or accreditation status of a system, the Accreditation Authority is a key stakeholder and will need to be consulted
and grant approval for the proposed changes.
6.3.6.R.02.
Rationale
Change management processes are most likely to be bypassed or ignored when an urgent change needs to be made to a system. In these
cases it is essential that the agency’s change management process strongly enforces appropriate actions to be taken before and after an
urgent change is implemented.
6.3.6.C.01.
ControlSystem Classification(s): Top Secret; Compliance: MUST
[CID:1088]
Agencies MUST ensure that for routine and urgent changes:
the change management process, as defined in the relevant information security documentation, is followed;
the proposed change is approved by the relevant authority;
any proposed change that could impact the security or accreditation status of a system is submitted to the Accreditation Authority for
approval; and
all associated information security documentation is updated to reflect the change.
6.3.6.C.02.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1089]
Agencies SHOULD ensure that for routine and urgent changes:
the change management process, as defined in the relevant information security documentation, is followed;
the proposed change is approved by the relevant authority;
any proposed change that could impact the security of a system or accreditation status is submitted to the Accreditation Authority for
approval; and
all associated information security documentation is updated to reflect the change.
6.3.7.
Change management process
6.3.7.R.01.
Rationale
Uncontrolled changes pose risks to information systems as well as the potential to cause operational disruptions. A change management
process is fundamental to ensure a considered and accountable approach with appropriate approvals. Furthermore, the change management
process provides an opportunity for the security impact of the change to be considered and if necessary, reaccreditation processes initiated.
66
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents