Identify systems and dependencies before retirement
Confirm the asset owner, covered services, linked identities, integrations, backups and supplier support arrangements. Verify that the successor service has been accepted and that any required migration can be reversed or recovered safely.
A supposedly obsolete machine may still provide a scheduled job, licence service or emergency recovery function. Discover such dependencies before disconnecting it.
Plan controlled migration and cutover
Set criteria for data integrity, availability, secure configuration and access control in the replacement environment. Determine who approves cutover and how to respond if critical functions fail.
For high-impact services, test business processes and restoration arrangements. A migration is not secure simply because the old hardware has stopped running.
Revoke access and network exposure
Remove accounts, API credentials, remote support connections, monitoring permissions and firewall rules that are no longer required. Update asset inventories and supplier access records to reflect the new architecture.
Look for shared secrets or service credentials embedded in scripts and configurations. Where secrets were copied into the replacement system, plan rotation to avoid leaving usable credentials on retired equipment.
Dispose of data appropriately
Identify information that must be retained, migrated or securely erased, according to applicable law, contractual obligations and organisational policy. Select sanitisation or destruction methods suited to the storage medium and sensitivity.
Deletion claims should be supported by suitable evidence. Where backups or legally mandated archives retain copies, document the limitation rather than claiming all data has disappeared.
Address third parties and physical assets
Coordinate equipment collection, recycling, disposal certificates and supplier offboarding as needed. Protect storage devices during transport and confirm that outsourced disposal arrangements have appropriate safeguards.
Do not overlook virtual machines, cloud resources, snapshots and abandoned development environments, which may remain accessible after an on-premises asset is removed.
Verify closure and keep proportionate evidence
Confirm service migration, removal of access, inventory updates and the chosen data handling. Retain approvals and disposal records in a form useful for future accountability and relevant supervisory requests.
NIS2 does not impose one universal destruction method on every organisation. Check national implementation, relevant sector requirements and any overlapping data protection rules before defining mandatory procedures.
Questions arising
Does NIS2 require a specific data destruction technology?
Article 21 does not prescribe a single destruction technology for every covered entity. Methods should reflect risk and other applicable legal obligations.
Why is secure retirement relevant to cybersecurity?
Retired systems can leave exploitable accounts, unsupported software and sensitive information behind unless dependencies and access are closed deliberately.