When the Information System reaches the end of its service life in an organisation, policy and procedures SHOULD be in place to ensure secure
decommissioning and transfer or disposal, in order to satisfy corporate, legal and statutory requirements.
13.1.10. Migration plan
13.1.10.R.01. Rationale
Once the decision to decommission a system has been taken, it is important to migrate processes, data, users and licences to replacement
systems or to cease activities in an orderly fashion. It is also important to carefully plan the decommissioning process in order to avoid
disruption to other systems, ensure business continuity, ensure security, protect privacy and meet any archive and other regulatory and
legislative requirements. The basis of a decommissioning plan is a risk assessment.
13.1.10.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:3832]
Agencies SHOULD undertake a risk assessment with consideration given to proportionality in respect of:
scale and impact of the processes;
data;
users;
licences;
usage agreements; and
service to be migrated or decommissioned.
13.1.10.C.02. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:3833]
The risk assessment SHOULD include the following elements:
Evaluation of the applications inventory and identification of any redundancies;
Identification of data owners and key stakeholders;
Identification of types of information (Active or Inactive) processed and stored;
Identification of software and other (including non-transferable) licences;
Identification of access rights to be transferred or cancelled;
Identification of any emanation control equipment or security enhancements;
Consideration of short and long term reporting requirements;
Assessment of equipment and hardware for redeployment or disposal;
Identification of any cloud-based data and services; and
User re-training.
13.1.10.C.03. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:3834]
Agencies SHOULD consider the need for a Privacy Impact Assessment.
13.1.10.C.04. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:3835]
Agencies SHOULD identify relevant service and legal agreements and arrange for their termination.
13.1.11. Decommissioning plan
13.1.11.R.01. Rationale
The decommissioning of a system can be a complex process. A decommissioning plan is an important tool in properly managing the safe
decommissioning of a system and in providing reasonable assurance that due process and agency policy has been followed.
13.1.11.C.01. ControlSystem Classification(s): All Classifications; Compliance: SHOULD
[CID:3838]
The decommissioning plan will be based on the migration plan and SHOULD incorporate the following elements:
An impact analysis;
Issue of notification to service providers, users and customers;
Issue of notification of decommissioning to all relevant interfaces and interconnections;
Timeframe, plan and schedule;
Data integrity and validation checks before archiving;
Transfer or redeployment of equipment and other assets;
Transfer or cancellation of licences;
Removal of redundant equipment and software;
Removal of redundant cables and termination equipment;
Removal of any emanation control equipment or security enhancements;
Return or safe disposal of any emanation control equipment or security enhancements;
Updates to systems configurations (switches, firewalls etc.);
Equipment and media sanitisation including any cloud-based data & services(discussed later in this chapter);
Equipment and media disposal (discussed later in this chapter);
Any legal considerations for supply or service contract terminations;
Asset register updates; and
Retraining for, or redeployment of, support staff.
13.1.12. Archiving
13.1.12.R.01. Rationale
168
Version_3.5__January-2022
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents