Small Business Cybersecurity: What Actually Matters

No scare tactics, and no promise that you will never be hit. A plain-language guide to the handful of things that stop most attacks, from a team named to the CRN Security 100 two years running.

Code background

The Short Version

Start with people

Most attacks start with a login or an email, not a movie-style hack. Fix identity and email first.

Follow a framework

A framework tells you what to do and in what order. A shopping list of security products does not.

Plan for a bad day

Assume something gets through eventually. Tested backups and a written plan decide how that day goes.

Code background

A Guide for Owners, Not IT People

Most breaches start with something ordinary

A reused password. A missed update. A convincing email on a busy day. That is how most businesses get hit, and it is good news, because ordinary problems have ordinary fixes. You do not need to become a security expert. You need a short list of things done consistently.

Follow a framework, not a shopping list

The security industry will happily sell you a product for every fear. A framework is the opposite of that: it is a plain order of operations. In the United States the standard starting point is the NIST Cybersecurity Framework, which sorts the work into six jobs.

  • Govern. Decide who is responsible and what the rules are.
  • Identify. Know what you have: devices, accounts, data and vendors.
  • Protect. Put the basic defenses in place.
  • Detect. Notice when something is wrong.
  • Respond. Know what you will do when it is.
  • Recover. Get back to work, and learn from it.

If your provider cannot tell you which framework they follow and where you stand against it, that is worth a conversation.

The controls that do most of the work

  • Identity. Multi-factor authentication on everything that offers it. A unique password for every account, kept in a password manager. When someone leaves, their access comes off that day.
  • Devices. Every computer and phone that touches business data is updated, encrypted and monitored. Nothing unmanaged gets on the business network.
  • Email. Filtering catches most of the junk. Training handles what gets through, because the last line of defense is a person deciding whether to click. See email security and awareness training.
  • Data. Know where your important data lives, back it up, and test the restore. A backup nobody has tested is a hope, not a plan.
  • Network and cloud. Separate what does not need to talk to each other, and give remote and work-from-home users a secure path in.
  • Vendors. Know which outside companies have access to your systems, and give every vendor account an expiration date.
  • Response and continuity. A written plan for the bad day, and communication channels that are already set up before you need them.

What a plan looks like when it is used

When heavy rain flooded a client’s facility, their continuity plan was already written and the channels already existed. Our team was working the problem within about two minutes, and the core network never went down. Read the case study.

If you answer to a regulator or an auditor

HIPAA, PCI and SOC 2 all ask for the same thing underneath: prove that you do the basics, every day, and can show it. Done right, compliance is a by-product of good security, and the next audit is a review, not a scramble. See Managed Compliance.

What we will not tell you

That you will never be hit. Nobody can honestly promise that. What we will tell you is where you stand, what we are watching, and what happens if something gets through.

How we do it at Ferrum

Our managed commitments come with our security suite and managed tools bundled in, so you are not stitching products together or deciding which protections to skip. We watch around the clock, respond when something looks wrong, and tell you plainly where you stand. Ferrum was named to the CRN Security 100 in both 2025 and 2026.

Code background

Want the Whole Book?

Secured: The Cybersecurity Survival Guide for Protecting Your Business goes through all of this chapter by chapter: the common threats, the framework, each control, incident response and compliance, plus a jargon decoder at the back. It is written for business owners, not IT people.

Ask us for a copy. No sales pitch attached.

Code background