Customer data
Keep a verified export of customer, consent and account records offline, so you can rebuild after deletion or encryption and show what you held.
What to keep offline
Customer database exportsConsent and preference recordsOrder and account historySubject access request records
Usually held by: Head of data or data protection lead
Public services
Councils and public bodies keep case and statutory records for years. Keep the retained copy offline, so services can continue when a shared system is down.
What to keep offline
Case recordsStatutory registersDecision recordsContinuity plans
Usually held by: Information governance lead or SIRO
Schools, colleges and trusts
Pupil records, assessment evidence and admissions files need to survive an incident in term time. Keep exports offline, held by a named person.
What to keep offline
Pupil recordsExam and assessment evidenceAdmissions and SEND recordsStaff records
Usually held by: Business manager or data protection lead
Retail
Loyalty, pricing and supplier data keep the business trading. Keep the masters and contracts offline, ready for a rebuild.
What to keep offline
Loyalty and customer exportsProduct and pricing mastersSupplier contractsStore and finance records
Usually held by: Head of data or IT director
Supply chain and logistics
When orders and routing data are encrypted, lorries stop. Keep the data and settings you would restart from offline.
What to keep offline
Order and routing dataCustomer and supplier contractsWarehouse and stock recordsIntegration settings
Usually held by: Operations director
IT and managed service providers
If your tools are compromised, every client is hit at once. Keep each client’s recovery copy outside the platforms attackers target.
What to keep offline
Client backup copiesClient configurationsContracts and SLAsRunbooks
Usually held by: Service owner, with named engineers