Scarlet Risk logoSCARLET RISK
Cyber Essentials

Scarlet Risk · Learn · Cyber Essentials

Cybersecurity Basics Every Small Business Needs

2 min read

Most small businesses don't get breached because of a sophisticated, targeted attack. They get breached because of a handful of basic gaps that go unaddressed for years — no multi-factor authentication, unpatched software, an employee who clicks the wrong link.

You don't need an enterprise security budget to close most of that gap. Here's where to actually start.

1. Multi-factor authentication (MFA), everywhere it's offered

If a password is the only thing standing between an attacker and your email, your bank, or your customer data, one leaked password is all it takes. MFA — a second step like a code from your phone — turns a stolen password into a dead end. Turn it on for email, banking, cloud storage, and any admin accounts first. It's free on almost every platform and it's the single highest-leverage thing on this list.

2. Keep software patched

Most breaches don't exploit a secret, unknown vulnerability — they exploit a known one that already had a fix available. Turn on automatic updates for operating systems, browsers, and any business software you rely on. If a vendor stops supporting a piece of software you use, that's a signal to plan a replacement, not to keep running it indefinitely.

3. Back up your data — and actually test the backup

Ransomware doesn't just threaten your data, it threatens your ability to operate. A backup that runs automatically, stores a copy somewhere separate from your main systems, and gets tested periodically (not just assumed to be working) is what turns a ransomware incident from a business-ending event into an inconvenience.

4. Limit who can access what

Not everyone on your team needs admin access to everything. The fewer people who can touch sensitive systems and data, the smaller your exposure if one account gets compromised. This is sometimes called "least privilege" — give people access to what their job requires, not more.

5. Train people to spot phishing

Most breaches start with a person, not a piece of malware. A single short training on what a phishing email looks like, run once or twice a year, meaningfully reduces the odds someone on your team clicks the wrong thing. It doesn't need to be elaborate — recognizing urgency, unexpected attachments, and requests to change payment details is most of the battle.

6. Have a basic incident response plan — before you need one

You don't need a 40-page document. You need to know: who gets called first, how you'll communicate if email is compromised, and who has the authority to make decisions under pressure. Write it down while you're calm. You won't have time to think clearly once something's actually happening.

Where this fits into a bigger picture

These six items won't make you SOC 2 compliant or HIPAA compliant on their own — those frameworks require more formal documentation, evidence, and in most cases a third-party audit. But they're the foundation almost every framework builds on top of. Getting these right first makes everything that comes after — a formal compliance program, a security questionnaire from a customer, a cyber insurance application — considerably less painful.

A practical review of your email environment

Choose your business email as a starting workflow. Identify its administrator, account inventory, MFA requirements, recovery options, forwarding rules, and connected applications. Ask which settings were actually checked and when. Record the evidence and any account or provider that was outside the review.

Next, walk through a suspicious-message scenario. Who receives a report, who can investigate it, and how does the team communicate if email is compromised? Confirm that the contact details and administrative permissions are available. This is an illustrative review, not a test that your organization has passed.

Make completion measurable

Replace broad tasks such as improve backups with a specific outcome: restore the information needed for a selected workflow and document what worked, what failed, and who owns the follow-up. Test procedures in a safe environment and involve the responsible provider before changing production systems.

For access cleanup, record which accounts and permissions were reviewed and obtain evidence of changes in the actual service. An employee’s checklist confirmation is not the same as an independently verified configuration. Keep both useful records, labeled clearly, so a later reviewer understands what each establishes.

Common mistakes to avoid

MFA does not make every compromised password harmless; sessions, recovery methods, and malicious integrations can create other paths. Backups do not eliminate the consequences of stolen information. Training attendance does not prove that every suspicious message will be recognized.

Use the foundations together, and revisit them when systems or staff change. For more detail, review the related MFA, attack surface, and incident-response glossary entries. Formal compliance work still requires the relevant scope and evidence; security basics are useful without being a certification claim.

Put this into practice with Scarlet Risk.

AI-powered risk intelligence that shows you exactly where you're exposed — and what to do about it.

Get started with Scarlet Risk