Ending a capability completely i.e. no migration, redevelopment or new version of a capability occurs; Combining parts of existing capabilities services into a new, different system; As part of wider redesign, where a capability is no longer provided and is decommissioned or merged with other capabilities or systems. 13.1.4. ICT requirements evolve as business needs change and technology advances. In some cases this will lead to the retirement and decommissioning of obsolete systems or systems surplus to requirements. 13.1.5. Security requires a structured approach to decommissioning in order to cease information system operations in a planned, orderly and secure manner. It is also important that the approach for decommissioning systems is consistent and coordinated. Sanitisation is important to eliminate any remnant data that could be retrieved by unauthorised parties. These procedures include the following: A migration plan; A decommissioning plan; Archiving; Safe disposal of equipment and media; Robust procedures to manage any residual data and associated risk; and Audit and final signoff. 13.1.6. As a final step, a review of the decommissioning should be undertaken to ensure no important elements, data or equipment have been overlooked. References 13.1.7. Reference Title Publisher Risk Management And UK Centre for the Protection of Accreditation Of Information National Infrastructure (CPNI) Source http://www.cpni.gov.uk/Documen ts/Publications/2005/2005003- Systems Also Released As HMG Risk_management.pdf Infosec Standard No. 2, August 2005 SP 800-88 NIST Special Publication 800-88 Guidelines for Media National Institute of Standards and Technology (NIST), U.S. Department http://nvlpubs.nist.gov/nistpubs/S pecialPublications/NIST.SP.800- Sanitization, Rev.1, December, of Commerce 88r1.pdf Better Practice Checklist – Australian Government Information http://agict.gov.au/policy-guides- Decommissioning Government Websites, March 2011 Management Office (AGIMO) procurement/better-practicechecklists-guidance/bpc- 2014 decommissioning PSR references 13.1.8. Relevant PSR requirements can be found at: Reference Title Source PSR Mandatory GOV3, INFOSEC1, INFOSEC2, INFOSEC3, http://www.protectivesecurity.govt.nz Requirements INFOSEC4, PHYSEC1 and PHYSEC2 https://www.protectivesecurity.govt.nz/governance/mandatory-requirements-2/ https://www.protectivesecurity.govt.nz/information-security/mandatoryrequirements-2/ https://www.protectivesecurity.govt.nz/physical-security/physical-securitymandatory-requirements-2/ PSR content Management protocol for information security https://www.protectivesecurity.govt.nz/information-security/management-protocol/ protocols Management protocol for physical security https://www.protectivesecurity.govt.nz/physical-security/management-protocol/ PSR requirements Handling requirements for protectively https://www.protectivesecurity.govt.nz/information-security/classification-system- sections marked information and equipment and-handling-requirements/handling-requirements/ Supply chain security https://www.protectivesecurity.govt.nz/governance/supply-chain-security/ Managing specific Secure your ICT facilities https://www.protectivesecurity.govt.nz/physical-security/specific-scenarios/physical- scenarios Physical Security for ICT systems security-for-ict/secure-your-ict-facilities/ https://www.protectivesecurity.govt.nz/physical-security/specific-scenarios/physicalsecurity-for-ict/ Rationale & Controls 13.1.9. Agency Policy 13.1.9.R.01. Rationale Information systems are often supported by service and supply contracts and may also be subject to obligations to provide a service, capability or information. Decommissioning of a system will require the termination of these contracts and service obligations. Other aspects of system decommission may be subject to security, regulatory or legislative requirements. An Agency policy will provide a comprehensive approach to system decommissioning from the inception of a system, thus facilitating the termination of supply contracts and service obligations while managing any risks to the Agency. 13.1.9.C.01. 167 ControlSystem Classification(s): All Classifications; Compliance: SHOULD [CID:3829] Version_3.5__January-2022

Select target paragraph3

Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents