Compliance

This is the Compliance demo. Every visitor shares this company, and it resets every night.

What you change here, everyone sees until the next reset. Email, payments, and the AI models are switched off.

Start your own trial
  • EU GDPR (2016)
  • ISO 27001:2022
  • NIS2
  • NIS2 Netherlands (Cbw, 2026)

Nothing found that matches the search criteria.

Start your own trial
SV
Sam de Vries
sam.devries@tidewell-it.example

Colocation provider failure plan

BCP-005 - Last updated SupplierLoss
Edit

Plan Document

Response steps

  1. The Platform Manager is told by the colocation provider, or by monitoring, that a suite is out of service and learns whether the provider expects to recover it.
  2. The Incident Coordinator declares the scenario when the provider cannot restore the suite within the recovery time, and the Supplier Manager informs the Management Board.
  3. The platform team moves customer workloads to the suite at the second provider, using the replicated storage, in the order that customers ranked.
  4. The monitoring engineer moves the monitoring probes with the workloads and checks that alerts still arrive.
  5. The Supplier Manager records the failure in the supplier review and decides with the Management Board whether to change providers.
Code
Date
Exercise type
Outcome
Conducted by
Actual RTO
Actual RPO

No tests recorded yet. Record the first exercise.

Are you sure?

This action cannot be reverted.

Leave this page?

Your changes on this form are not saved. If you leave, they are lost.