Skip to content
← Back to articles
Security
Business Strategy

Security, Backups and Recovery: Evidence to Ask For

Define recovery needs, test allowed and denied access, and record a complete restore exercise.

By Rupert GoughPublished Updated
Security, Backups and Recovery: Evidence to Ask For

The practical answer

A resilient system needs appropriate permissions, tested recovery and clear operating responsibility. Agree recovery objectives, then verify records, files and critical journeys in a controlled exercise.

Talk to Lightning Developments about your custom business system, responsibilities and support needs. Discuss your system.

On this page 4 sections

A resilient system needs appropriate access controls, a tested recovery process and clear responsibilities. Hosting-provider assurance is useful evidence about that provider; it does not certify your application configuration or the way your business uses it.

Agree what interruption the business can tolerate #

Recovery time objective (RTO) is the target time to restore an agreed service. Recovery point objective (RPO) describes the amount of recent data the business can tolerate losing, usually expressed as time. Set them for the business task, then check whether the architecture, backups and support can meet them.

Illustrative recovery brief; these are proposed targets, not service promises
QuestionExample decisionWhat must be checked
What is the critical task?Staff need to read current jobs and record urgent updatesWhich database, files, identity service and integration support it?
How long can it be unavailable?Proposed RTO: four hoursCan a restore and verification actually finish within that period?
How much recent work can be lost?Proposed RPO: one hourDoes the complete backup/replication arrangement cover that interval?
How will staff work meanwhile?Use a controlled incident log with one ownerHow are new entries reconciled after service returns?

A daily backup alone would not meet a one-hour RPO. A successful backup job also does not prove a successful restore. Agree objectives and costs together rather than promising instant recovery.

Test access beyond the login screen #

Illustrative permission checks before release
TestExpected outcomeEvidence to keep
Client A requests Client B’s record or fileAccess denied without exposing the recordTest account, request, result and date
Standard user calls an administrative action directlyServer rejects the actionRole, action and observed response
Former staff account attempts to sign in or reuse accessAccess removed according to the offboarding planRevocation steps and checks
Support person requests temporary elevated accessAuthorised, time-limited access with an appropriate recordApprover, purpose, expiry and actions

Authentication establishes identity; authorisation controls actions. For technical review, use the OWASP authorisation guidance. Provider responsibilities and your responsibilities need to be recorded separately; for example, Supabase describes its shared responsibility model.

Run a controlled recovery exercise #

  1. Select a backup and record its timestamp and coverage.
  2. Restore into an isolated environment with appropriate access.
  3. Verify records, files, configuration and critical user journeys.
  4. Measure recovery time and identify any missing recent data.
  5. Record failed checks, owners and remediation dates.

Do not send test emails or trigger live billing while rehearsing. Verify external connections using safe test arrangements. Protect the restored data and remove the temporary environment under the agreed retention process.

Download the recovery exercise record (CSV). Open in a spreadsheet or text editor; the example rows are illustrative.

Agree the ongoing care #

Name who monitors errors, updates dependencies, reviews access, checks backups and responds to an incident. Confirm what the service includes, what needs separate approval and how to contact the responsible person. A hosting subscription is not automatically a complete operational service.

Repeat the exercise when important dependencies or business requirements change. See the security questions guide for the controls to discuss with your developer.

A useful companion: Workflow Mapping Worksheet.