6.3.7.C.01.
ControlSystem Classification(s): Top Secret; Compliance: MUST
[CID:1093]
An agency’s change management process MUST define appropriate actions to be followed before and after urgent changes are implemented.
6.3.7.C.02.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1094]
An agency’s change management process SHOULD define appropriate actions to be followed before and after urgent changes are
implemented.
6.3.7.C.03.
ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:1095]
Agencies SHOULD follow this change management process outline:
produce a written change request;
submit the change request to all stakeholders for approval;
document the changes to be implemented;
test the approved changes;
notification to user of the change schedule and likely effect or outage;
implement the approved changes after successful testing;
update the relevant information security documentation including the SRMP, SSP and SOPs
notify and educate system users of the changes that have been implemented as close as possible to the time the change is applied; and
continually educate system users in regards to changes.
6.3.8.
Changes impacting the security of a system
6.3.8.R.01.
Rationale
The accreditation of a system accepts residual security risk relating to the operation of that system. Changes may impact the overall security
risk for the system. It is essential that the Accreditation Authority is consulted and accepts the changes and any changes to risk.
6.3.8.C.01.
ControlSystem Classification(s): All Classifications; Compliance: MUST
[CID:1098]
When a configuration change impacts the security of a system and is subsequently assessed as having changed the overall security risk for the
system, the agency MUST reaccredit the system.
6.4. Business Continuity and Disaster Recovery
Objective
6.4.1.
To ensure business continuity and disaster recovery processes are established to assist in meeting the agency’s business requirements, minimise any
disruption to the availability of information and systems, and assist recoverability.
Context
Scope
6.4.2.
This section covers information on business continuity and disaster recovery relating specifically to systems.
References
6.4.3.
Additional information relating to business continuity is contained in:
Reference
ISO 22301:2019
Title
Security and resilience —
Publisher
Source
ISO
https://www.iso.org/standard/75106.
Business continuity
html
management systems —
Requirements
ISO/IEC 27001:2013
Information Technology –
ISO
Security Techniques Information Security
https://www.iso.org/standard/54534.
html
Management Systems Requirements
ISO/IEC 27002:2022
Information security,
ISO
cybersecurity and privacy
protection — Information
https://www.iso.org/standard/75652.
html
security controls
ISO/IEC 27005:2018
Information Technology –
ISO
Security Techniques -
https://www.iso.org/standard/75281.
html
Information Security Risk
Management
ISO/IEC 27031:2011
Information technology —
Security techniques —
Guidelines for information and
ISO
https://www.iso.org/standard/44374.
html
communication technology
readiness for business
continuity
67
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents