A plan for business continuity and disaster recovery restores wagering operations if the production environment becomes inoperable: it addresses how player and wagering data are stored to minimise loss, documenting the recovery method or the potential loss where replication is asynchronous; states when it is invoked; provides a recovery site physically separate from production; contains recovery guides with the technical steps to re-establish wagering at the recovery site; and covers resuming administrative operations after activation for a range of scenarios.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.