
The theme of this year’s Cybersecurity Awareness Month, “Don’t Make It Easy for Them,” is a good reminder that security isn’t about perfection. Criminals tend to go after the easiest targets first. If your accounts and devices take a little more effort to break into than the next person’s, many attackers will simply move on.
The good news is that a handful of everyday habits cover a lot of ground. None of them require technical skill.
A small business does not need to be a household name to attract a cyberattack. Criminals often look for practical opportunities: a password that has appeared in a breach, an account without multi-factor authentication, an old device that no longer receives security fixes, or files that cannot be recovered after they are deleted or encrypted.
The goal is not to eliminate every possible risk. It is to make common attacks harder to carry out, limit what an intruder can reach, and give the business a way to recover if something still goes wrong. Four repeatable habits can help: use multi-factor authentication, give every account a unique password, keep software supported and updated, and maintain backups that can actually be restored.
What We'll Cover
1. Turn on multi-factor authentication
Multi-factor authentication (MFA) asks you to prove your identity in more than one way. For example, signing in may require a password plus an approval in an authenticator app or a physical security key. If someone steals your password, that extra step can stop them from signing in with the password alone.
Start with accounts that could unlock other parts of your business: your primary email account, financial accounts, password manager, website and hosting logins, and services that store customer or business information. Email deserves particular attention because it is often used to reset passwords for other accounts. Protecting it can help prevent one compromised login from spreading into several.
Use the strongest practical sign-in option the service supports. Passkeys and security keys can provide strong protection against phishing when implemented correctly. An authenticator app is generally preferable to text-message codes when available, though any MFA is usually better than relying on a password alone. The options vary by service, so choose what you can use consistently.
MFA is not a guarantee. Attackers may try to trick someone into approving an unexpected prompt, steal an active login session, or exploit a different weakness. Never approve a sign-in request you did not initiate. If prompts keep appearing unexpectedly, treat that as a warning and review the account’s security.
Store recovery codes somewhere safe and separate from the account they protect. Review the account’s recovery email address and phone number, too. Otherwise, losing a phone or security key can turn a security improvement into a lockout.
2. Use a unique password for every account
Password reuse lets one breach turn into several. When a password leaks from one service, criminals may test the same email address and password on other popular services, including email, cloud storage, financial accounts, and workplace tools. They do not need to guess every password if people reuse credentials.
A password manager can generate and store long, random passwords, so you do not have to remember each one. Protect the manager itself with a strong, unique master passphrase and MFA if available. Make sure you understand how to recover access if you lose your device, and keep recovery information somewhere secure. Avoid storing the only copy of recovery details inside the account that those details are meant to recover.
Be cautious with unexpected messages that ask you to reveal a password, follow a sign-in link, or approve an authentication request. When a message claims there is a problem with an account, go to the service through a known bookmark or by typing its address yourself rather than trusting the link in the message.
If you suspect a password has been exposed, change it on the affected service and anywhere else it was reused. Start with email and other accounts that can be used to reset passwords elsewhere. If you cannot tell whether a password was reused, treat the accounts that matter most as the priority and work outward from there.
3. Keep software supported and updated
Updates do more than add features or change an interface. They often fix security weaknesses that could let an attacker access a device, run unwanted code, or interfere with a service. Once a weakness is known, leaving affected software un-patched can give attackers an opportunity to exploit it.
For everyday devices, turn on automatic updates for the operating system, browser, phone, and routinely used apps where practical. Restart devices when updates require it; a downloaded update may not take effect until the device restarts. Do not ignore repeated update notices indefinitely simply because the computer still appears to work.
Business-critical systems need clear ownership rather than guesswork. A website, plugin, point-of-sale system, production computer, or specialized application may need compatibility checks, a maintenance window, a backup, or testing before an update is applied. That is a reason to have a process, not to postpone updates forever. Decide who is responsible, how urgent updates are handled, and how the business will respond if an update causes a problem.
Also check whether devices and applications are still supported. An old router, operating system, plugin, or business application may continue to run while no longer receiving security fixes. When that happens, plan a supported replacement or alternative. Updating cannot protect software that no longer receives updates.
4. Back up what you cannot afford to lose
Backups help a business recover from accidental deletion, hardware failure, ransomware, and other disruptions. They are not a complete prevention strategy: they do not necessarily stop an attacker from viewing or stealing information. Their purpose is to preserve a usable copy of important data so the business has options when the original is lost or damaged.
Keep backups separate from the systems they protect. If every backup is accessible through the same account or connected system, someone who compromises that account may be able to change or delete the copies as well. Keep at least one copy offline or otherwise protected from modification or deletion by someone who compromises your main environment.
Choose a backup schedule that reflects how often the information changes and how much work you could afford to lose. A business that updates orders, customer records, or production files throughout the day may need a different schedule from one that updates a small website occasionally. Check that the backup includes the data and configuration you would actually need, not just the files that were easiest to select.
Test a restore periodically. Start with a small set of important files, then confirm that you can recover the data and open it. For a website or business system, make sure the restored data and application work as expected. A successful backup notification only tells you that a process ran; it does not prove that recovery will work when you need it.
Why these habits work better together
Each habit addresses a different part of the problem. MFA can make it harder to use a stolen password, but it will not fix an un-patched computer. Unique passwords limit the damage from a credential leak, but they cannot prevent every kind of attack. Updates close known software weaknesses, but they do not stop someone from tricking an employee into giving away access. Backups help with recovery, but they do not necessarily prevent an attacker from accessing or copying information.
That is why it helps to think in layers. MFA, unique passwords, and updates primarily reduce opportunities for an incident. Backups help reduce the consequences when prevention fails. None replaces the others, and no single measure makes a business completely safe. Together, however, they make it harder for a problem to start, spread, or become permanent.
Make the habits part of how the business operates
You do not need a dedicated IT department to begin, but someone should own the work. For a small business, that might mean identifying who manages email and financial accounts, who handles computer and website updates, and who checks backups. If a service provider manages one of these systems, confirm what they are responsible for and what still falls to the business. There are many ways you can start protecting yourself, and your website, today.
For example, a small contractor or manufacturer could begin by enabling MFA on its main email, financial, and hosting accounts; replacing reused passwords with unique ones in a password manager; checking which devices and software need updates; and confirming that business files and website data have a separate backup. The business can then test restoring a few important files and record who to contact if an account or device is compromised.
A short list of specific tasks, with an owner and a due date, is more useful than a general intention to improve security. Revisit the list when staff, systems, or service providers change. Security is ongoing maintenance, not a one-time cleanup.
What to prioritize if you cannot do everything
If your time is limited, begin with the accounts that control other accounts and the information you cannot easily replace:
- Turn on MFA for your primary email and other high-impact accounts.
- Replace reused passwords with unique ones, starting with email and financial accounts.
- Make sure important files and website data have a separate, protected backup, and test restoring them.
- Enable routine updates and assign someone responsibility for business-critical systems and unsupported software.
You can spread the work over several days. On the first day, enable MFA on your primary email. Next, start replacing reused passwords. Then review updates and identify who owns them. Finally, check your backups and test restoring a small set of important files. This is a suggested sequence, not a guarantee that every system can be secured in a week; specialized or business-critical systems may require more planning.
Start with one action this week
Choose one practical step and finish it: enable MFA on your primary email, set up a password manager, install pending routine updates, identify unsupported software, or test a backup restore. Once it is done, choose the next item and make it part of your regular routine.
If you are not sure where to start, we can help review your accounts, devices, backups, and update practices. Just send us a message and we’ll get in touch.
