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

Ransomware recovery plan

BCP-002 - Last updated Cyberattack
Edit

Plan Document

Response steps

  1. Whoever sees encrypted files or a ransom note disconnects the device from the network and calls the service desk at once.
  2. The Incident Coordinator opens an incident, isolates the affected network segments, and disables the accounts involved.
  3. The Information Security Officer decides with the Management Board whether customers or the Dutch Data Protection Authority must be told, and starts the clock on the notification deadline.
  4. The systems engineers rebuild affected servers from clean images and restore data from the offsite copy at Harbourlight Offsite Backup, after checking the last good restore point.
  5. Passwords and keys that the attacker could have seen are replaced before any system returns to production.
  6. The team writes a short report with the cause and the changes that follow from it.
Code
Name
RTO (target)
RPO (target)
ACT-001
Managed hosting platform
2h
15m
ACT-002
Service desk and ticketing
4h
1h
ACT-004
Customer backup service
8h
24h
ACT-005
Customer identity and Microsoft 365 administration
4h
1h

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.