Recovery order follows dependencies
You cannot restore the application before the thing it authenticates against, however much more visible the application is.
Commercial pressure pushes towards bringing back whatever customers notice first. Dependencies dictate a different order, and ignoring them produces a sequence of failed restores. Knowing the order in advance is part of the plan; discovering it during the incident costs days.
More on Backups and recovery
- Offline copies break attacker reachabilityReach ends at the last plug
- Immutable backups trade flexibility for protectionSet in concrete
- RPO and RTO answer different questionsTwo different clocks
- Restoring data can restore malware tooThe newest jar is the spoiled one
- Backup credentials deserve separate protectionNot on the same switch
- Backup retention determines how far back you can restore to escape corruption or compromiseAs far back as the rope goes