Do today / check immediately
- □
List every system: where your site, domain, DNS, email, payments, CRM, bots/apps, and databases live.
- □
Check the domain: is it registered to you or to a contractor? Do you have access to the registrar? Is auto-renew on? This matters even without hackers.
- □
Check access: who knows passwords for the site, hosting, bank, email, ad accounts, CRM? Do former employees still have access?
- □
Turn on 2FA everywhere possible: email, hosting, domain, bank, CRM, Telegram accounts.
- □
Make a backup right now: site files + database. Even if everything seems fine.
- □
Keep client contacts outside the site/CRM: a spreadsheet, phone, email. If the site goes down, you must still be able to reach customers.
This week
- □
Set up 3-2-1 backups: at least 3 copies, on 2 different media, 1 copy off the main hosting. Example: hosting + cloud backup + external drive.
- □
Test restoration: an untested backup is not a backup.
- □
Separate dependencies: domain from one registrar, DNS separately, hosting separately, email separately. Don’t keep everything in one account.
- □
Prepare an “emergency stub” page: simple page with contacts, Telegram/WhatsApp link, request form, and “site temporarily unavailable — orders accepted here.”
- □
Prepare a backup payment route: payment link, manual invoice, payment widget, bank details. Money should not stop if the site goes down.
- □
Change default passwords on cameras, fridges, smart ovens, alarms, and any internet-connected equipment.
- □
Train employees: don’t open “reconciliation act,” “tax audit,” or “test assignment” attachments without verification; don’t keep passwords on sticky notes; report incidents immediately.
Quarterly
- □
Access review: former employees, contractors, old services.
- □
Backup check: restore one test file/site.
- □
Run a drill: “site is down,” “payments fail,” “employee opened phishing.”
- □
Update the emergency envelope: critical services, logins, responsible people, who to call.
2. Sample Policies for a Small Business
Policy 1. Backup Policy
Goal: if the site/server/hosting fails, the business recovers in hours, not weeks.
What to back up: site files, databases, CRM, accounting, documents, client contacts.
Frequency: site and databases daily; important documents on change; full archive weekly.
Where: primary cloud + independent cloud/external drive stored physically separately.
Owner: name/role.
Verification: restore one file/page monthly.
Rule: don’t keep all eggs in one basket — don’t store the only backup with the same hosting provider.
Policy 2. Passwords and Access
Every service gets a separate long password.
Passwords live in a password manager or a physical notebook in a safe. Not in chat, not in a shared file, not on a sticky note.
2FA is mandatory for email, domain, hosting, bank, CRM.
Access is granted only to those who need it.
On termination, revoke access the same day.
An emergency access set is kept by the owner/director in a separate envelope.
Policy 3. Emergency Plan: “Site/Hosting Is Down”
0–30 minutes:
Confirm the problem: site, control panel, email, payments.
Do not delete or reinstall anything in the panel.
Notify clients on Telegram/social media: “Site is temporarily unavailable; orders accepted here.”
Switch on backup order/payment intake.
30 minutes–2 hours:
Check provider status.
Put up an emergency stub on another host/subdomain.
Check whether a recent backup exists.
Assign one person responsible for client communication.
2–24 hours:
Restore the site from backup or rebuild from web archive/saved materials.
If needed, move the domain/site to another host.
Record losses: screenshots, downtime, correspondence.
Policy 4. Payments During an Outage
Always have a backup payment link.
Be able to issue an invoice manually.
Keep the list of active clients/orders accessible outside the site.
Assign someone to contact clients on the day of the outage and explain how to pay.
Record all manual payments so orders are not lost.
Policy 5. Phishing and Employee Incident
Do not open attachments from unknown/suspicious senders.
“Test assignments” that require installing software — only after IT/management approval.
If suspicious: disconnect the device from the network, notify the responsible person, change passwords, enable 2FA.
Rule: an employee must report an incident within 15 minutes. No punishment for reporting — otherwise people will hide it.
Policy 6. Domain, Hosting, and Contractors
The domain is registered to the company/owner, not the contractor.
At least two trusted people have domain access.
All contractors have an SLA: what they do during an outage, response time.
When changing contractors, access is transferred by act.
3. Client Message Template During an Outage
Hello! Due to a technical failure at our hosting provider, our website is temporarily unavailable. We are already working on restoration.
Orders and requests are accepted here: [Telegram/WhatsApp/phone].
Payment: [link/details].
Your orders and data are not lost. Next update — [time].
Thank you for understanding.
