Small business cybersecurity and privacy: the complete playbook for owners
A practical playbook for small business cybersecurity and privacy: protect accounts, devices, email and data, handle personal information properly, plan for incidents and follow a 90-day action plan.

In this guide
- Start with what you have and what could go wrong
- Accounts, passwords and who can access what
- Devices, software and remote work
- Email, phishing and payment fraud
- Data, backups and retention
- Privacy: what you collect and how you handle it
- Suppliers, cloud tools and AI
- When something goes wrong: an incident plan
- A 90-day action plan
- Common mistakes
- Where WorkBOS fits
- Frequently asked questions
Cybersecurity and privacy used to be an IT department problem. In a small business there is no IT department, so the problem lands on the owner, usually on a bad day: a fake invoice that was paid, an employee's account that sent spam, a laptop left in a taxi, or a customer asking what you do with their data. The good news is that most small business incidents come from a short list of causes, and a short list of habits prevents most of them. You do not need to be technical to put those habits in place. You need to decide that it matters, assign an owner and work through a checklist.
This playbook gathers those habits into one practical plan. It covers security (keeping bad actors out and limiting the damage if they get in) and privacy (handling personal information properly), because in a small business the two overlap. It is written for US owners and managers. It is general information, not legal or professional advice, and laws on privacy and breach notification differ by state and industry, so confirm your own obligations with a lawyer or your industry regulator. For a shorter starter list, see our cybersecurity basics guide.
Start with what you have and what could go wrong
Security starts with knowing what you are protecting. Spend an hour on a plain-language inventory before you buy anything. A spreadsheet is enough.
List your assets
- Data: customer and prospect details, contracts, invoices, employee records, bank and payment details, passwords and keys, plans and designs.
- Accounts: email, banking, payroll, accounting, your website and domain name, social media, cloud storage, business software.
- Devices: laptops, phones, tablets, office computers, printers, routers, point-of-sale terminals and anything else connected.
- People: owners, staff, contractors, bookkeepers and anyone else with access.
- Suppliers: every company that holds your data or can change your systems.
Rank what matters most
For each item, ask two questions: how bad would it be if this were lost, stolen or exposed, and how likely is it? Your email account and your bank login usually top the list, because whoever controls your email can reset almost every other password. Customer data and payroll data come next because of the legal and personal harm if they leak.
Use a framework, but do not be scared of it
The US National Institute of Standards and Technology publishes the Cybersecurity Framework, now in version 2.0, which it describes as helping organizations understand and improve how they manage cybersecurity risk. Its quick-start material explains that the framework is voluntary guidance based on existing standards and practices and is intended for organizations of any size or sector. Its three main components are the Core (a set of desired activities and outcomes in common language), the Implementation Tiers (context on how rigorous your program should be) and Profiles (your own alignment of goals and resources against the Core). NIST has also published a white paper aimed at the smallest businesses, those with no employees other than the owner, showing how to use CSF 2.0.
You do not have to adopt the framework to benefit from it. Its main message is useful on its own: security is a cycle of knowing what you have, protecting it, noticing problems, responding and recovering, and it should be decided in terms of the risk to your business rather than as a pile of tools.
Name an owner
Even in a ten-person business, one person must own security. That person is not necessarily technical. Their job is to keep the checklist, schedule the routines, make sure access is removed when people leave and be the first point of contact when something looks wrong. Write their name at the top of your plan.
Accounts, passwords and who can access what
Most break-ins happen through accounts, not through clever technical attacks. Stolen or reused passwords, phishing and accounts left open after someone leaves are the usual routes.
Passwords that hold up
- Use a password manager so that every account has a long, unique password you do not have to remember.
- Prefer long passphrases to short complex ones, and never reuse a password across accounts.
- Do not share logins by email or chat. If several people need the same service, use individual accounts or a manager's shared vault.
- Change a password immediately if you suspect exposure, and check whether the account has unfamiliar sign-ins or forwarding rules.
NIST's digital identity guidelines, which are the US standard for how systems should handle authentication, have been revised in Revision 4, which integrates synced passkeys. Passkeys are a sign-in method that replaces passwords with a cryptographic key stored on your device, and they are worth using where a service offers them because there is no password to steal or phish.
Turn on multi-factor authentication
Multi-factor authentication, often shortened to MFA, asks for a second proof of identity in addition to the password, such as a code from an app, a hardware key or a passkey. Turn it on first for email, banking, payroll, accounting, your domain registrar, cloud storage and any admin account. Prefer an authenticator app or security key over text messages where you have the choice, because text messages can be intercepted or redirected. Our multi-factor authentication rollout plan takes you through it in order.
Give the least access that does the job
This idea is called least privilege. Each person should be able to see and change only what they need. A bookkeeper does not need your customer list. A sales person does not need payroll. An intern does not need admin rights. Use named roles, review them every quarter and remove accounts the day someone leaves. Our guide to roles and permissions shows a simple scheme.
| Role | Typical access | Review how often | |---|---|---| | Owner or admin | Everything, including billing and user management; at most two people | Quarterly | | Manager | Their team's projects, customers and reports | Quarterly | | Staff | Only the tools and records for their job | Twice a year | | Contractor | Specific projects, for a fixed period | At the end of each engagement | | Read-only or viewer | View access to selected material | Twice a year |
Offboard quickly and completely
When somebody leaves, in the same hour: disable their accounts, collect devices, revoke access to shared drives, change any shared passwords they knew, remove them from email forwarding and mailing lists, and transfer the ownership of their files and customer relationships. Keep a one-page offboarding checklist and tick it every time.
Devices, software and remote work
Keep everything updated
Attackers routinely use known flaws for which fixes already exist. Turn on automatic updates for operating systems, browsers, office software, phones, routers and any plugins on your website. Retire devices that no longer receive updates. Keep a list of who has which device so you can check that updates are really happening.
Protect devices that leave the building
- Turn on full-disk encryption on laptops and phones, so a lost device does not mean lost data.
- Set a screen lock with a short timeout, and use a PIN or biometrics.
- Enable remote lock and wipe for company phones and laptops.
- Install reputable security software and keep it switched on.
- Do not use public Wi-Fi for sensitive work without a trusted connection method, and prefer a phone hotspot.
Secure the office network
Change the default administrator password on your router, use a strong Wi-Fi password and encryption, give guests a separate network, and keep payment terminals and any smart devices apart from the network your staff use for work. If you take card payments, follow your payment provider's requirements for protecting cardholder data.
Decide your rules for personal devices
If staff use personal phones or laptops for work, set minimum rules: a screen lock, automatic updates, an approved way to store work files, no sending work files to personal email, and the right to remove company data when the person leaves. Put the rules in your handbook, as described in our employee handbook guide.
Remote and hybrid work
Remote work widens the places your data lives. Keep work files in your approved cloud storage rather than on personal drives, use MFA everywhere, and teach people to lock their screen at home and in cafes. Our guide to managing a remote or hybrid team covers the working side, and the asynchronous communication guide covers how to share information without scattering it across tools.
Email, phishing and payment fraud
Email is both your most important tool and your biggest door for attackers.
Recognise phishing
Phishing is a message that pretends to come from someone you trust to trick you into clicking a link, opening a file, sharing a password or sending money. Warning signs include urgency, unexpected attachments, a sender address that looks almost right, requests to bypass the usual process, and links that go somewhere different from what the text says. Our phishing guide has examples and a response routine.
A habit that stops many attacks: if a message asks you to do something involving money, credentials or sensitive data, confirm it using a different channel, such as a phone number you already have, before you act.
Beware of invoice and payment-change fraud
A common and costly scam is called business email compromise. The attacker either takes over a real mailbox or imitates a supplier or executive, then asks you to pay an invoice, change bank details or buy gift cards. Protect yourself with simple rules:
- Never change a supplier's bank details based on an email alone; call a known number to verify.
- Require two people to approve payments above a set amount and any change to payee details.
- Check the sender address carefully, not just the display name.
- Make staff feel safe to ask "is this real?" without embarrassment.
- Move payment approvals into a system that records who requested and who approved.
Improve your email setup
Ask your email provider or IT adviser to turn on the standard email authentication settings for your domain (known as SPF, DKIM and DMARC), which make it harder for criminals to send mail that appears to come from you. Block automatic forwarding to outside addresses unless it is needed, and review mailbox rules for unfamiliar entries, which attackers use to hide replies.
Train people, repeatedly
Training works best when it is short, regular and specific. Five minutes at a team meeting, a monthly example of a real phishing message and a simple way to report suspicious email do more than an annual lecture. The National Cybersecurity Alliance publishes yearly research on security attitudes and behaviors, and its 2026 report headline asks why people who know what they should do still do not do it. That gap between knowing and doing is exactly what routines and reminders are for, so build habits and checklists rather than relying on good intentions. You can find its material at staysafeonline.org.
Data, backups and retention
Know where your data lives
Make a simple data map: for each kind of data, where is it stored (which system, which device, which country if relevant), who can access it, and how long you keep it. Duplicate copies in email attachments, personal drives and old exports are common weak points. The fewer places data lives, the fewer places you need to protect.
Collect and keep less
The safest data is data you never collected or have already deleted. Ask for only what you need, delete what you no longer need, and avoid storing sensitive items such as full card numbers or government ID numbers unless the law or your work requires it. Balance this with legal retention periods. The IRS says that you should keep records that support income, deductions or credits until the period of limitations for the return expires, which is generally three years but longer in some cases, and employment tax records for at least four years, as set out on its how long should I keep records page. Our record keeping guide explains how to reconcile deleting data with keeping what the law requires.
Back up using the 3-2-1 approach
The widely used rule is to keep three copies of important data, on two different types of storage, with one copy offsite or offline. Offline or immutable copies matter especially for ransomware, which encrypts your files and demands payment, because an attacker who reaches your network can often reach backups that are permanently connected. Test a restore every quarter by actually recovering a file and a whole folder, and time how long it takes. Our backup guide provides a checklist.
Encrypt and control sharing
Encrypt laptops and phones, and use encrypted connections to your services. Share files with named people rather than "anyone with the link", set expiry dates on shares, and review who has access to your shared drives every quarter. Where you send sensitive documents, prefer a secure portal or a signing tool over email attachments.
Privacy: what you collect and how you handle it
Privacy is about people's information: what you collect, why, who sees it, how long you keep it and what rights people have over it. Security protects the data. Privacy decides whether you should have it and what you may do with it.
Know what personal information you hold
Personal information includes names, addresses, phone numbers, email addresses, identification numbers, payment details, employee records, photos, location and online identifiers. List it in your data map and note the reason you hold each type. Special care is needed for sensitive categories such as health, financial and children's information, which several laws treat more strictly.
Know which rules apply to you
The United States has no single national privacy law covering every business. Instead there is a mix of federal laws for particular sectors (such as health, finance and children's data), consumer protection rules against unfair or deceptive practices, and a growing number of state privacy laws with different thresholds and rights. All states also have laws that require notifying affected people after certain kinds of data breach, and the details, such as what counts as a breach and how quickly you must notify, vary by state. If you serve customers in other countries, such as the European Union, additional laws may apply. Because this changes quickly, check the current rules for each state where your customers live and for your industry, and ask a lawyer for a one-time review.
Tell people what you do
Publish a plain-language privacy notice on your website that says what you collect, why, who you share it with, how long you keep it and how people can contact you. Make it match reality, because a statement that promises more than you do can itself create legal exposure. If you send marketing email, follow the rules in our email marketing guide, including honouring unsubscribes promptly.
Handle requests and mistakes well
Decide who answers questions from customers about their data and how you verify who they are before releasing anything. Keep a log of requests and how you resolved them. If you send a document to the wrong person, treat it as an incident, ask the recipient to delete it and record what happened.
Apply the same care to employee data
Employee records carry social security numbers, bank accounts and sometimes health information. Restrict them to the smallest group, store them in a protected location and follow retention rules. The hiring side of this is covered in our guide to hiring your first employees.
Suppliers, cloud tools and AI
You can outsource a task but not the responsibility for the data. Every supplier that holds your data is part of your security.
Choose and review suppliers
Before adopting a tool that will hold customer or employee data, ask:
- Where is the data stored and who can access it?
- Does it support MFA, role-based access and an audit log?
- Can you export your data and delete it at the end of the contract?
- What does the supplier do if it has a security incident, and how fast will it tell you?
- Does it publish security information, independent assessments or a clear privacy policy?
Keep a list of suppliers, what data they hold, who owns the relationship and when you last reviewed them. Remove tools nobody uses; every unused account is a risk.
Use AI tools with clear rules
AI assistants can save time, but they can also receive sensitive data in prompts. Set rules on what may be entered, which tools are approved and whether staff may use free consumer accounts for work. Where AI tools can take actions such as sending messages or changing records, require a human to approve actions that affect customers or money. Our guides to AI and customer data privacy, using AI safely and keeping control of AI agents explain how.
Check your website and online presence
Keep your website platform and plugins updated, use MFA on the site admin and domain registrar, and turn on automatic renewal for your domain so it cannot lapse and be taken over. Remove old staff accounts, keep backups of the site and check forms for spam abuse.
When something goes wrong: an incident plan
Incidents will happen to some small businesses despite good habits. What separates a manageable incident from a disaster is how fast you notice and how clearly you act. Write the plan now, while it is calm.
Detect early
Signs to watch for include unexpected password reset emails, unfamiliar sign-ins, files that will not open or have strange names, an unusually slow computer, customers reporting odd messages from you, and unexplained changes to payment details. Turn on sign-in alerts in your key accounts and review audit logs where they exist.
A first-hour response
- Contain. Disconnect the affected device from the network, change passwords from a clean device and sign out all sessions on affected accounts.
- Tell the right people. Alert your security owner, the owner or director, and your IT adviser or provider.
- Preserve evidence. Do not wipe machines straight away. Take screenshots, keep emails and note times.
- Stop money moving. If payment details or invoices are involved, call your bank immediately and ask whether a payment can be recalled.
- Report the crime. The FBI's Internet Crime Complaint Center at ic3.gov describes itself as the central hub for reporting cyber-enabled crime, and says that if someone is in immediate danger you should call 911 or local police. Its home page also warns that scammers impersonate the IC3 and that the IC3 will never directly contact you for information or money.
- Assess what data was exposed, and take advice about legal duties to notify customers, employees, insurers or regulators, because deadlines can be short.
- Recover from clean backups, change all potentially exposed credentials, and re-enable access step by step.
- Review. Within two weeks, write down what happened, why, and what will change.
Prepare contacts in advance
Keep an offline sheet with the phone numbers for your bank, cyber insurance provider, IT adviser, lawyer, payment processor and key suppliers, plus the names of staff who will make decisions. If your email is down, you must not be searching for those numbers in email.
Consider cyber insurance
Cyber insurance can pay for response costs, legal advice, notification and some losses. Policies differ and insurers often require specific controls such as MFA and tested backups, so compare quotes and read the exclusions. Insurance supports a security program; it does not replace one.
A 90-day action plan
Trying to fix everything at once leads to doing nothing. Use this sequence, which puts the highest-value controls first.
| Period | Actions | Done when | |---|---|---| | Days 1 to 30 | Name a security owner; list assets and suppliers; set up a password manager; turn on MFA for email, banking and admin accounts; turn on automatic updates; start a basic backup | Every owner and admin account has MFA and a unique password, and one backup exists | | Days 31 to 60 | Review roles and remove unused accounts; encrypt laptops and phones; set payment-change verification and a two-person approval rule; run a first phishing awareness session; write a one-page incident plan | Nobody has more access than their job needs and payments cannot change on an email alone | | Days 61 to 90 | Test restoring a backup; publish or update your privacy notice; review supplier list; agree rules for AI tools; run a short incident drill; set quarterly review dates | A restore has worked, the privacy notice matches practice and the plan is in the calendar |
Quarterly checklist
- Review who has access to which systems and remove what is not needed.
- Check that updates and backups ran, and test one restore.
- Review supplier list and any new tools adopted.
- Review audit logs and sign-in alerts for unusual activity.
- Run a five-minute security reminder with the team.
- Update the incident contact sheet.
Keep it proportionate
A sole trader and a thirty-person agency have different needs. Start with the controls that stop the common attacks, add more as your data, headcount and customer expectations grow, and revisit the plan every year. Customers, especially larger ones, increasingly ask suppliers about security, so a written plan also helps you win work.
Common mistakes
- Relying on one password across many accounts. One breach elsewhere then opens your business accounts.
- Skipping MFA on email. Email controls password resets for everything else.
- Untested backups. Many businesses find out during a crisis that the backup was incomplete.
- Everyone is an admin. One mistake or one stolen account gives an attacker everything.
- Changing payment details by email. This is how invoice fraud succeeds.
- No offboarding routine. Former staff keep access for months.
- Collecting data you do not need. Every extra record is extra risk and extra responsibility.
- Promising privacy you do not deliver. A privacy notice must describe real practice.
- Pasting sensitive data into unapproved tools. Set clear AI and software rules.
- Treating security as a one-off project. It is a routine, reviewed on a calendar.
Where WorkBOS fits
WorkBOS is a business operating system that keeps customer records, projects, invoices, documents, HR records and messages in one workspace, which means there are fewer separate places to secure. Relevant features include roles and permissions to limit who sees what, an audit log of changes, drives for central file storage, document signing so that agreements are not passed around by email, AI agents that act only with human approval and a branded client portal so that clients do not need to receive files in attachments. No product makes a business secure by itself: you still need strong passwords, multi-factor authentication, trained people and tested backups. See the features, pricing (including a free plan), docs and the Academy for details. For the wider picture of the routines around security, read our complete guide to running a small business back office.
Frequently asked questions
Q: What is the single most important security step for a small business? A: Turn on multi-factor authentication for email and banking and use a password manager so that every account has a unique password. Email controls resets for almost everything else, so protecting it protects the rest.
Q: Are small businesses really targeted by attackers? A: Yes. Attackers often use automated attacks that do not care how large you are, and small businesses tend to have weaker defences than large companies. NIST runs a dedicated Small Business Cybersecurity Corner of free resources for this reason.
Q: What is the difference between cybersecurity and privacy? A: Security is about protecting systems and data from unauthorized access. Privacy is about what personal information you collect, why, how you use it and what rights people have over it. You need both: good security protects personal data, but privacy also asks whether you should hold the data at all.
Q: Do I have to follow a framework such as the NIST Cybersecurity Framework? A: It is voluntary guidance, not a legal requirement for most small businesses. Many owners use it as a checklist for what to cover, and NIST publishes material designed for small businesses, including those with no employees.
Q: What should I do first if I think an employee account was hacked? A: Sign out all sessions and change the password from a clean device, enable MFA, check for forwarding rules and unusual activity, warn the team about possible phishing messages sent from the account, and report the incident to your security owner. If money or personal data may be involved, contact your bank and take advice about notification duties.
Q: How often should I test my backups? A: At least quarterly. Restore a single file and a full folder, and time the process. A backup you have never restored is an assumption.
Q: Do I need cyber insurance? A: It is worth considering if you hold customer data or depend on online systems. Policies vary and often require controls such as MFA and tested backups. Compare coverage, exclusions and response support with a broker.
Q: How do I handle privacy rules that differ by state? A: List the states where your customers live, check the current rules for each and for your industry, and get a one-time legal review. Keep your data map and privacy notice accurate so that any request can be handled consistently.
Sources are linked in the text above: NIST (Cybersecurity Framework, Small Business Cybersecurity Corner), FBI Internet Crime Complaint Center, National Cybersecurity Alliance, IRS (how long to keep records).
Run it all from one place
Projects, clients, finance, people and AI employees in one system. Start free, no card needed.
Start free →