Know what needs to come back first
Identify the files, applications, and system information your organization needs to resume work. Decide who owns each recovery task and what the immediate priorities would be during an interruption.
Back up important information regularly. A synchronized folder is not always a separate recovery copy: deletion or unwanted changes may be synchronized too. Check the actual retention and restoration features of the service you use.
Protect the recovery copy
CISA recommends keeping backups protected from the systems an attacker could compromise, including offline or otherwise isolated copies. Restrict backup administration and protect access credentials. Confirm that backups cover the data and configurations your organization expects them to cover.
Test restoration periodically. A completed backup job does not establish that the right information can be restored within an acceptable time.
Respond deliberately
If ransomware is suspected, follow your incident response plan and contact the designated IT or security team promptly. Recovery should use known-clean systems and appropriate backups; restoring too early can bring a problem back into the environment.
WLC government staff should use their established internal incident channel. Record what you observed and when. Avoid improvising a cleanup, deleting evidence, or reconnecting affected equipment without instructions from the response team.
Further reading
CISA: #StopRansomware Guide
FTC: Cybersecurity for Small Business