Small Business Cybersecurity: How to Stop Being the Low-Hanging Fruit
2026-11-16 · 8 min read

Most conversations about small business cybersecurity start with the same question: would anyone really bother attacking a company our size? It's a fair question, and the honest answer is that a few might come looking for you specifically, but far more will simply find you. That difference matters, because defending against being found is not the same as defending against being hunted.
My view is simple. If you run a small business, the attacks you're most likely to face aren't personal. They're opportunistic, and they go to whoever is easiest to get into from the outside. You can't make yourself invisible, but you can stop being the low-hanging fruit.
Most attacks on small businesses are opportunistic, not personal
I want to be careful here, because it's tempting to swing too far the other way. Targeted attacks are real. A business with a valuable client list, a high-profile customer, or a disgruntled former insider can absolutely be singled out, and if that's your situation, you need to plan for it.
For most small businesses, though, the likelier story is less dramatic. Someone is sweeping the internet for anything that answers on a known weak spot, or trying passwords that already leaked somewhere else, and your company happens to turn up. Nobody chose you by name. You were simply on the list of things that were open. CISA says it plainly in its guidance on requiring strong passwords: small and medium-sized businesses are frequent targets for cybercriminals, and weak or stolen passwords are one of the easiest ways they get into business accounts.
I actually find that encouraging. Opportunistic attacks are about economy: the attacker is looking for the cheapest way in, not for you. You don't have to be impenetrable. You have to stop being the easiest option on the list, and that starts with knowing what the list says about you.
What makes a company easy: exposed services and leaked logins
When I picture a small business that's low-hanging fruit, I rarely picture a careless one. I picture a busy one. Two things come up again and again: services that are reachable from the internet when they don't need to be, and logins that have leaked somewhere outside the company's control.
Windows on the roof that nobody checks
Think about how hardware arrives at a small business. A security camera system, a new router, a temperature sensor or monitor in the back room, a retail device at the front counter. Usually a vendor installs it, gets it working, and sets it up so it can be reached remotely, because that's convenient for everyone. The problem is that vendors don't always build or configure things to be secure by default. If you can reach that system from anywhere, so can anyone else.
And installation isn't maintenance. The vendor may do the job well on day one, but that doesn't mean anyone is maintaining the device afterward, or checking that its updates actually succeeded. The same CISA guidance warns that many hardware and software products come out of the box with default usernames and passwords that are widely known and easily exploited. CISA's Secure by Design work makes the bigger point that the security burden has been placed disproportionately on consumers and small organizations, instead of on the companies that make the technology. I agree, but until that changes, the device on your network is still your problem.
Here's how I think about it. Every open port is a window, and each new device adds more of them, often bigger ones, just as the hailstorms are getting more frequent. Except these windows are on the roof, where nobody sees them day to day. Nobody is checking the attic.
Sometimes the first sign that something came through one of those windows doesn't show up inside the business at all. When a network is compromised, it can start sending attack traffic outward, and the business can end up on a third-party threat feed as a source of attacks. The attacker is there, but the business may be unaware, aside from maybe noticing that things seem slower than usual. I described a case like this in my post on what threat intelligence is, and it's still one of the clearest examples I know of a problem that shows up outside your network before it shows up anywhere you're looking.
Leaked logins are the keys to the house
The second thing is leaked credentials, and I want to say this plainly: leaks are inevitable, and having credentials out there doesn't mean your business did anything to cause it. People sign up for services, those services get breached, and the logins end up in places you'll never see. That part is mostly out of your hands.
What turns a leak into a break-in is usually human behavior. When the same password has been reused for several things, including something that matters to the business, one leak from an unrelated site can open a door at work. What better way for an attacker to get in than with the keys to the house? There's no window to break and no alarm to trip. They walk in the front door, and to most of the tools watching, they look like someone who belongs there.
None of this is unique to one industry. Take a small SaaS company as an example. The product may run entirely in the cloud, but the company still has an office router, maybe a camera system, a test server a contractor stood up and forgot about, and a handful of people who have reused a work password somewhere personal. None of that feels like a crisis. It just quietly makes the company easier than the next one. If that sounds like your team, our page on cyber threat intelligence for SaaS companies covers how this applies to a small software company without a dedicated security team.
Why an inside-the-network checklist misses both
Most small business security advice is a checklist that looks inward: antivirus on every laptop, a firewall, a password manager, backups, an IT provider on call. I'm in favor of all of it. Those controls are beneficial, and the basics in CISA's cyber guidance for small businesses are worth following. One point in that guidance describes the vendor-installed device problem exactly: many attacks succeed because the victims were running vulnerable software when a newer, safer version was available.
The trouble is that an inward checklist can only check what it knows about. The camera system the vendor installed isn't on anyone's patch list. The open port on the router isn't something antivirus was ever going to see. And a password that leaked in some other company's breach never touches your network at all, so nothing inside it can tell you it's out there.
I think of the usual tools this way. A password manager isn't enough on its own, because it only protects the passwords people actually put in it. Antivirus is the wrong kind of tool for this question, because it watches the inside of a machine, not what the internet can see. And an IT provider is valuable, but they aren't going to own it the way you or an employee would, especially for equipment someone else installed. None of those are failures. They just answer different questions, and the question an inside checklist can't answer is the one opportunistic attackers start with: what does this company look like from the outside?
Seeing your company the way an attacker does
If attackers are shopping from the outside, the most useful thing you can do is look at the same shelf. That means knowing which of your services and devices are visible on the internet, whether your network shows up anywhere as a source of attacks, and whether credentials tied to your company's email domains have been exposed. This isn't about panic. It's about context, so you can ask better questions of your vendors and your IT provider and decide what to fix first.
That's the job I built ThreatHarvest to do. You register what identifies your organization: your domains, public IPs, brand keywords, and social handles. ThreatHarvest then reviews ports and exposed services tied to your public IPs from publicly available data, so you can see your external attack surface the way an outsider would, without anything scanning or probing your network. It checks those same IPs against threat feeds for signs your network may be compromised. And it watches for exposed credentials tied to your email domains, so a match shows up as a finding you can review.
Where to start this week
If you only do one thing this week, start a free trial and look at your own company from the outside. I recommend that over another checklist for a simple reason: there's only upside to having more information. Either you find nothing surprising and you've confirmed what you believed, or you find a window on the roof you didn't know was there, and you get to close it before someone else finds it.
When you look, start with the two things this post is about. For anything answering on your public IPs, ask whoever installed it whether it needs to be reachable from the internet at all, and who is responsible for its updates. If credentials tied to your email domains turn up exposed, treat it as a reason to retire reused passwords and turn on multifactor authentication, not as a reason for blame. And keep the basics going on the inside, because the outside view works best alongside them, not instead of them. Finally, don't treat any of this as a one-time check. What can be seen from the outside changes every time a vendor installs something new or another site gets breached, so keep watching it over time.
Targeted attacks will always exist, and nobody can promise you won't face one. But for most small businesses, the likelier threat is the attacker who finds you, not the one who chose you. Small business cybersecurity starts with refusing to be the easiest option on the list.