Most security incidents at small companies start with something ordinary: a reused password, an old account nobody removed, a backup that had quietly stopped running. You do not need a security team to check for these. You need an afternoon, an admin login and an honest answer to each question below.
Work through the list with whoever administers your accounts. Where the answer is "no" or "not sure", write it down. That list is your starting point.
1. Know what you have
- You have one list of the cloud services, SaaS tools, domains and devices the business depends on.
- Each item has a named owner inside the company.
- You know which of them hold customer data, payment details or credentials.
- You know which admin accounts exist for each one, and who holds them.
2. Protect your accounts
- Multi-factor authentication is switched on for email, cloud consoles, code hosting, banking and the domain registrar.
- Admin accounts use an authenticator app or a hardware key, not SMS, wherever the service allows it.
- Everyone uses a password manager, and passwords are not reused between services.
- No admin work is done from a shared login.
3. Control who has access
- When someone leaves, their accounts are disabled the same day, following a written checklist.
- Contractors get access for the length of the contract, and it is removed afterwards.
- People have the access their role needs and no more.
- Someone reviews the list of users and admins on your main systems at least every quarter.
4. Protect your email and domain
- SPF, DKIM and DMARC records are published for every domain you send mail from.
- The domain registrar account has multi-factor authentication and an up-to-date recovery contact.
- Domain renewal is automatic, and the payment method is current.
5. Back up, then test a restore
- Your important data is backed up automatically, to somewhere separate from the original.
- You know how much recent work you could lose and how long a restore would take.
- Someone has restored from a backup in the last six months to prove that it works.
- Backups of sensitive data are encrypted, and access to them is limited.
6. Keep devices and software current
- Laptops and phones used for work install updates automatically.
- Laptop disks are encrypted and lock after a short idle period.
- Servers, frameworks and dependencies have an owner who applies security updates.
- Software that no longer receives updates has been replaced or isolated.
7. Prepare for a bad day
- There is a short written note on who to call and what to do first if an account or system is compromised.
- The team knows how to report something suspicious, and that reporting early is welcome.
- You know which customers, partners or authorities you would need to tell after an incident.
- Contact details for your providers are stored somewhere you can reach when your own systems are down.
What to do with your answers
Sort every "no" and "not sure" into three groups: fix this week, fix this quarter, and accept for now. Start with account protection and offboarding. Those two usually reduce the most risk for the least effort.
If the list is longer than your team can handle, or you want an independent view, our Startup Security Baseline covers the same ground in more depth and ends with a prioritised roadmap.
