CCyber Blog

Simple and practical cybersecurity guides for small and medium-sized businesses that want to reduce cyber risk without building a large internal security team. We cover MFA, backups, phishing, password policies, Microsoft 365 security, employee training, basic risk assessment and minimum incident response planning.

How Not to Get Hacked as a Small Business

A small business usually does not get hacked through a movie-style attack, but through basic gaps: no MFA, weak passwords, phishing, outdated devices, untested backups, excessive permissions and no response plan. Learn a practical plan to reduce risk quickly without building a large security team.

Prepared by: CCyber Editorial Team

Short answer

A small business can significantly reduce the risk of being hacked by implementing a few basic rules: enable MFA for email and administrator accounts, use unique passwords and a password manager, regularly update devices and applications, create and test backups, train employees on phishing, limit permissions, secure email and have a simple incident response plan. The most important goal is to close the easiest attack paths before criminals use them.

Last updated

July 2026

Who this article is for

  • small business owners
  • SME boards
  • service companies
  • online stores
  • accounting firms, law firms, agencies and consulting companies
  • software houses and small technology companies
  • manufacturing companies without a large IT department
  • people responsible for IT in a small company
  • companies using Microsoft 365, Google Workspace, CRM, accounting systems and cloud services
  • companies that want to quickly reduce phishing, ransomware, account takeover and data loss risk

Key takeaways

  1. A small business does not need to start with expensive tools. First, protect email, accounts, devices, data and incident response.
  2. The most common entry points for attackers are phishing, stolen passwords, missing MFA, vulnerable devices, compromised email, insecure remote access and lack of backups.
  3. The most important account in a small business is usually email. A compromised mailbox may allow attackers to reset passwords, impersonate the company and defraud customers.
  4. Backups protect only when they are regular, separated from the main environment and tested.
  5. The best plan is 30 days for quick basics, 60 days to organize access and backups, 90 days to exercise an incident and build a simple security management routine.

How does a small business usually get hacked?

Small businesses are rarely hacked through a very advanced attack prepared for months. Much more often, the problem starts with basic gaps that are easy to exploit.

Typical scenarios:

  • an employee clicks a fake login link
  • an email password leaks from another service
  • an account has no MFA
  • a former employee still has file access
  • remote desktop or VPN is poorly secured
  • an online store or website has outdated plugins
  • a computer is missing updates
  • an attacker takes over a mailbox and sends fake invoices
  • ransomware encrypts files and backups do not work
  • an employee shares an MFA code after a phone call from someone impersonating IT

The conclusion is simple: to avoid being hacked as a small business, first close the basic entry points. More advanced tools can come later.

The main rule: do not protect everything equally

A small business has limited time, budget and people. It does not need to start by protecting everything in the same way. First, protect what can stop the business or cause the biggest losses.

The most important assets are often:

  • corporate email
  • accounting system
  • banking and payments
  • customer data
  • company drive or cloud documents
  • CRM
  • online store
  • production or operations system
  • code repository if the company develops software
  • administrator accounts

The first question for the business owner should be: which systems can we not operate without even for one day?

Step 1: secure corporate email

Email is the center of a small business. Invoices, contracts, customer data, document links, password resets and supplier communication go through email. Compromised email may give an attacker access to many other systems.

What should you do?

  • enable MFA for all email accounts
  • secure owner, board, finance and administrator accounts first
  • disable accounts of former employees
  • check email forwarding and automatic rules
  • define who can reset passwords
  • enable unusual login alerts
  • use company accounts, not private mailboxes for business work
  • enable basic domain protections such as SPF, DKIM and DMARC

Why does this matter?

An attacker who compromises email can read correspondence, impersonate the company, send invoices with changed bank account details, reset passwords to other systems and attack customers.

Evidence to prepare: report of accounts with MFA enabled, active email account list, forwarding and email rule review.

Step 2: enable MFA on the most important accounts

MFA, or multi-factor authentication, means the password alone is not enough to log in. Even if a password leaks, the attacker must pass an additional verification step.

Where is MFA required first?

  • email
  • Microsoft 365 or Google Workspace
  • administrator accounts
  • banking
  • accounting system
  • CRM
  • online store
  • VPN and remote access
  • code repositories
  • systems containing customer data

Which method should you choose?

The best direction is phishing-resistant methods such as security keys or passkeys. A good first step is an authenticator app. SMS is better than no MFA, but it should not be the target method for administrator, finance and owner accounts.

What to do in practice?

  • list all critical accounts
  • enable MFA for the owner and administrators
  • enable MFA for finance and email
  • prepare a backup method
  • define an account recovery procedure
  • check once per quarter who does not have MFA

Evidence to prepare: critical account list with MFA status and exception list.

Step 3: use unique passwords and a password manager

One of the simplest ways to take over an account is using a password leaked from another service. If an employee uses the same password in multiple places, one leak may open access to email, CRM or a company system.

What should you do?

  • use unique passwords for every service
  • deploy a password manager
  • do not send passwords by email or chat
  • do not store passwords in Excel or notes
  • avoid shared accounts where possible
  • change passwords after an employee leaves if they were shared
  • remove accounts the company no longer uses

What about administrator passwords?

Administrator passwords should be especially protected. Administrative access should be granted only to those who really need it. An administrator should not use the same account for everyday work and system management.

Evidence to prepare: password policy, list of shared accounts to remove and confirmation of password manager use.

Step 4: organize employee and supplier access

Small companies often have problems not because nobody has access, but because too many people have too much access. Former employees, suppliers, interns and test accounts sometimes remain active for months.

What should you do?

  • prepare a list of people with system access
  • remove former employee accounts
  • remove supplier access after work is completed
  • limit access only to what is needed
  • check who has administrator permissions
  • define an access granting and removal process
  • review permissions at least once per quarter

Key questions

  • who has banking access?
  • who can issue invoices?
  • who has access to customer data?
  • who can reset passwords?
  • who has an administrator account?
  • which suppliers have remote access?

Evidence to prepare: access register, administrator list and confirmation of the latest permission review.

Step 5: update computers, phones, websites and applications

Outdated software is one of the easiest attack paths. This includes computers, phones, browsers, accounting systems, online stores, plugins, routers and remote access tools.

What should be updated first?

  • computer operating systems
  • web browsers
  • office software
  • phones used for work
  • routers and network devices
  • VPN and remote access tools
  • website
  • online store
  • website plugins and themes
  • accounting, CRM and business applications

What to do in practice?

  • enable automatic updates
  • remove applications the company does not use
  • do not use systems without vendor support
  • assign responsibility for website and online store updates
  • check once per month for overdue updates
  • urgently update internet-facing systems

Evidence to prepare: device and application list, update status and unsupported system list.

Step 6: create backups and test recovery

Backups are the difference between a problem and a disaster. If the company loses access to data because of ransomware, failure, employee error or deleted files, a backup can save business continuity.

What should be backed up?

  • customer documents
  • contracts
  • invoices
  • accounting data
  • email
  • CRM
  • online store data
  • project files
  • code repositories
  • important system configurations

How should backups be done?

  • automatically, not manually
  • regularly, based on data importance
  • separated from the main environment
  • protected against deletion by attackers
  • with access protected by MFA
  • with regular recovery testing

The most important rule: a backup that has not been tested is only hope. Regularly check whether data can really be restored.

Evidence to prepare: backup register, backup schedule and recovery test report.

Step 7: teach people to recognize phishing

Phishing is one of the most common attack methods against small businesses. Attackers may impersonate a customer, supplier, bank, courier, government office, IT employee or business owner.

What should employees learn?

  • do not click under pressure
  • do not enter a password after clicking from an email
  • never share an MFA code with anyone
  • verify unusual requests through another channel
  • watch for supplier bank account changes
  • be careful with unexpected attachments
  • report suspicious messages
  • report quickly if you clicked or entered data

Key business processes

It is not enough to tell people to “be careful”. The company should have specific rules for risky situations.

  • supplier bank account changes require confirmation through another known channel
  • urgent payments require approval according to the procedure
  • requests for passwords or MFA codes are always suspicious
  • new suppliers should be verified before payment
  • suspicious attachments should be reported, not opened for testing

Evidence to prepare: phishing reporting instruction, trained employee list and suspicious message register.

Step 8: secure employee devices

An employee laptop or phone often contains access to email, documents, CRM and customer data. A lost device or malware infection can quickly become a company incident.

Minimum for computers

  • updated operating system
  • disk encryption
  • screen lock
  • strong PIN or password
  • malware protection
  • no daily work from an administrator account
  • remote lock or data wipe capability where possible

Minimum for phones

  • updated operating system
  • screen lock
  • device encryption
  • remote wipe capability
  • no random app installation
  • separation of business and personal data where possible

Evidence to prepare: device list, update status, encryption status and BYOD rules.

Step 9: restrict remote access

Remote access is convenient, but it often becomes a door for attackers. This applies to VPN, remote desktop, administrator tools, supplier access and applications exposed to the internet.

What should be checked?

  • is remote desktop exposed to the internet?
  • does VPN have MFA?
  • which suppliers have remote access?
  • is supplier access permanent or temporary?
  • are remote sessions logged?
  • is access removed after work is completed?
  • do administrators use separate accounts?

What to do in practice?

  • turn off unnecessary remote services
  • enable MFA for VPN and admin panels
  • limit access to specific people
  • grant supplier access only for the time needed
  • monitor administrator logins
  • review remote access at least once per quarter

Evidence to prepare: remote access register, supplier list and latest review report.

Step 10: prepare a first 60-minute incident plan

A small business does not need a long procedure immediately. It needs a clear instruction on what to do when something goes wrong.

The plan should answer

  • who makes decisions?
  • who contacts the IT provider?
  • who blocks a compromised account?
  • who disconnects an infected computer?
  • who contacts the bank?
  • who contacts customers?
  • who assesses legal obligations?
  • how do we communicate if email is down?
  • where is the emergency contact list?

First actions after a suspected attack

  • do not panic and do not hide the problem
  • disconnect the suspicious device from the internet and company network
  • do not delete evidence
  • block the suspicious account
  • change passwords from a safe device
  • check whether other accounts are affected
  • contact the IT provider or incident response specialist
  • write down what happened and when

Evidence to prepare: one-page response plan, emergency contact list and exercise note.

What should you do if you suspect the company has been hacked?

Compromised email

  • change the password from a safe device
  • sign out all sessions
  • enable or reset MFA
  • check email forwarding rules
  • check whether messages were sent to customers
  • inform customers if they may have received a fake message

Infected computer

  • disconnect the computer from the network
  • do not connect backup drives
  • write down symptoms and detection time
  • contact IT
  • check which systems the computer could access

Fraudulent payment

  • contact the bank immediately
  • preserve correspondence and invoices
  • check whether email was compromised
  • check who approved the payment
  • change the process for confirming supplier bank account changes

Ransomware

  • disconnect infected devices
  • protect backups
  • do not restore data before checking backups are clean
  • preserve the ransomware note
  • determine affected systems
  • contact an incident response specialist

Checklist: how not to get hacked

Accounts

  • does email have MFA?
  • do administrators have MFA?
  • are passwords unique?
  • does the company use a password manager?
  • were former employee accounts removed?
  • are administrator accounts limited?

Data

  • is critical data identified?
  • does data have backups?
  • are backups separated from the main environment?
  • has recovery been tested?
  • is access to customer data limited?

Devices

  • are computers up to date?
  • are phones secured?
  • do laptops have disk encryption?
  • do employees avoid working as administrators?
  • are unused applications removed?

Email and phishing

  • do employees know where to report phishing?
  • does finance confirm supplier bank account changes through another channel?
  • do employees know not to share MFA codes?
  • does the domain use SPF, DKIM and DMARC?
  • are suspicious messages analyzed?

Incidents

  • does the company have an emergency contact list?
  • is it clear who decides during a crisis?
  • is the response plan available offline?
  • has the company exercised email compromise or ransomware?
  • is it clear when to inform customers, bank or insurer?

30, 60 and 90-day action plan

First 30 days

  • enable MFA for email, administrators and finance
  • list the most important accounts, applications and data
  • remove former employee accounts
  • deploy a password manager
  • check backups
  • perform the first data recovery test
  • update computers, browsers and router
  • prepare a simple phishing reporting instruction
  • prepare an emergency contact list

Days 31 to 60

  • expand MFA to CRM, accounting, online store and remote access
  • organize permissions to customer data
  • secure phones and laptops used for work
  • check website and plugin updates
  • restrict supplier remote access
  • run short phishing training
  • write a one-page incident response plan
  • define a process for confirming supplier bank account changes

Days 61 to 90

  • review administrator accounts
  • test recovery of a more important system or larger data set
  • check which devices and applications remain outside control
  • exercise an email compromise scenario
  • exercise a ransomware scenario
  • prepare a simple security report for the owner or board
  • define an improvement plan for the next 6 months

What documents and evidence should be prepared?

Basic documents

  • list of key systems
  • administrator account list
  • list of people with access to banking and accounting
  • list of people with access to customer data
  • simple password and MFA policy
  • phishing reporting instruction
  • incident response plan
  • emergency contact list

Technical evidence

  • MFA report
  • backup report
  • recovery test report
  • company device list
  • update status
  • laptop encryption status
  • removed account register
  • access review register

Organizational evidence

  • trained employee list
  • confirmation of security rule communication
  • incident exercise note
  • suspicious message report register
  • policy exception decisions
  • security report for the owner or board

Common small business mistakes

Mistake 1: “we are too small to be attacked”

Attacks are often automated. Criminals do not need to know the company. They only need to find a vulnerable website, weak password, missing MFA or insecure remote access.

Mistake 2: MFA for only some people

If only the owner has MFA, but accounting, administrators or shared email do not, the gap remains.

Mistake 3: backups without testing

Many companies learn that backups do not work only after an attack. Recovery testing should be a regular security activity.

Mistake 4: former employee accounts

Inactive accounts with access to email, files or systems are unnecessary risk. Access should be removed immediately after cooperation ends.

Mistake 5: excessive permissions

Not everyone should see all data or change settings. The more permissions a compromised account has, the greater the damage.

Mistake 6: no payment confirmation procedure

A fake invoice or bank account change is a very practical risk. Verification through another channel can save the company from financial loss.

Mistake 7: response plan only in the owner’s head

During a crisis, people act under pressure. The plan should be written, simple and available even if email or the company drive does not work.

How to measure whether the company is safer?

Account metrics

  • percentage of accounts with MFA
  • number of administrator accounts
  • number of former employee accounts
  • number of shared accounts
  • date of latest access review

Data metrics

  • number of systems covered by backups
  • date of latest recovery test
  • time needed to restore data
  • number of critical data sets without backup

Device metrics

  • number of company devices
  • number of outdated devices
  • number of devices without encryption
  • number of applications without an owner

People and response metrics

  • number of trained employees
  • number of suspicious messages reported
  • response time to a phishing report
  • time to block a compromised account
  • date of latest incident exercise

Business example

A small trading company has 14 employees. It uses cloud email, accounting software, online banking, CRM and an online store. It has no cybersecurity person. IT is handled by an external provider.

The problem starts with an email impersonating a supplier. An accounting employee receives information about a bank account change and an urgent payment request. The message looks credible because the attacker had previously compromised one employee mailbox and knew the conversation context.

After the incident, the company performs a short review. MFA was not enabled on all accounts, a former employee still had drive access, backups were not tested and there was no process for confirming supplier bank account changes.

The company implements the basics in 90 days. It enables MFA, removes old accounts, deploys a password manager, tests backups, updates the online store, trains employees and introduces another-channel confirmation for payment changes.

The result is not that the company becomes impossible to hack. The result is that the easiest attack paths are closed and the team knows how to respond quickly.

How can ccyber.io help?

ccyber.io helps small businesses implement practical protections without excessive bureaucracy and without starting from expensive tools. We focus on what really reduces account takeover, ransomware, phishing, data loss and downtime risk.

We can support your organization with:

  • SME Cybersecurity Starter Pack
  • basic cybersecurity audit
  • MFA implementation
  • Microsoft 365 or Google Workspace review
  • backup review and recovery test
  • employee phishing training
  • incident response plan preparation
  • employee and supplier access review
  • website and online store review
  • 30, 60 and 90-day cybersecurity roadmap

The best first step is a short SME cybersecurity assessment. It helps check whether the company has closed the easiest attack paths, which controls should be implemented first and what evidence should be prepared for customers, the board or insurers.

FAQ

Can a small business really be hacked?

Yes. Small businesses use email, cloud services, banking, accounting systems, customer data and internet-connected devices. That is enough to become a target of phishing, ransomware or automated vulnerability scanning.

What is most important to avoid getting hacked?

The most important basics are MFA, unique passwords, updates, backups, phishing training, permission limits, email security and a simple response plan.

Is good antivirus enough?

No. Device protection is important, but it does not replace MFA, backups, updates, access control and employee training. Attacks often start from an account or email, not only from a malicious file.

Should MFA be enabled for everyone?

Eventually yes, but start with email, administrators, finance, banking, cloud systems and remote access. Then expand MFA to the remaining applications.

How often should backups be created?

It depends on how much data the company can lose without business paralysis. Critical data should be backed up regularly, automatically and tested through recovery.

Do employees need to understand cybersecurity?

They do not need to be experts. They need to know a few practical rules: do not share passwords or MFA codes, beware of urgency, verify unusual requests through another channel and report suspicious messages.

What should be done if someone clicks a suspicious link?

Fast reporting is the most important step. The company should block the suspicious account, change the password from a safe device, check sessions, email rules and whether the attacker performed further actions.

Does cybersecurity help in B2B sales?

Yes. More customers ask about MFA, backups, training, data protection and incident response. A small business with evidence of basic controls looks more trustworthy as a supplier.

Summary

A small business does not need perfect security to significantly reduce risk. It must close the easiest attack paths: weak accounts, missing MFA, outdated devices, untested backups, phishing and uncontrolled access.

The best approach is practical. First secure email, accounts and data. Then organize devices, permissions, remote access and training. Next, prepare a simple response plan so the company knows what to do when something happens.

The goal is not to turn a small business into a large security department. The goal is to make it a harder target, detect problems faster and recover after an incident.

Sources

5 najważniejszych działań cyberbezpieczeństwa dla małej firmy

5 Essential Cybersecurity Actions for a Small Business

Prepared by: CCyber Editorial Team

Short answer

A small business should start cybersecurity with five actions: enable MFA for email, cloud and administrator accounts, create and test backups, update devices and applications, train employees on phishing and prepare a simple incident response plan. These actions do not solve every problem, but they reduce the most common risks: account takeover, ransomware, data loss, payment fraud and long downtime.

Last updated

July 2026

Who this article is for

  • small business owners
  • SME boards
  • service companies
  • online stores
  • accounting firms, law firms, agencies and consulting firms
  • software houses and small technology companies
  • manufacturing companies without a large IT team
  • people responsible for IT in a small company
  • companies preparing for B2B customer requirements
  • organizations that want to reduce cyberattack risk quickly without building a large security team

Key takeaways

  1. A small business should not start by buying many tools. First, protect accounts, data, devices, email and incident response.
  2. The most important account in a small business is usually corporate email. Email compromise may lead to fraud, password resets, document theft and attacks on customers.
  3. Backups matter only if the company has tested that it can actually restore data from them.
  4. Employees do not need to become cybersecurity experts, but they need to know how to recognize a suspicious message and where to report it.
  5. An incident response plan can be one page. What matters is knowing who decides, who to call, what to disconnect and how to communicate with customers.

Why does a small business need cybersecurity?

Small businesses often assume they are too small to be targeted. This is a dangerous assumption. Attackers do not always choose victims manually. They often scan the internet, send mass phishing, exploit weak passwords, vulnerable devices, poorly secured email and missing MFA.

For a small business, even one incident can be very costly. The issue is not only data theft. It may be loss of email access, lost files, an encrypted accounting computer, payment fraud, loss of customer documents or several days of downtime.

Small business cybersecurity should answer simple questions:

  • can someone easily take over our email?
  • do we have a copy of data if a computer or cloud service stops working?
  • are our devices up to date?
  • do employees know how to report phishing?
  • do we know what to do in the first hours after an attack?

The best starting point is practical actions that reduce the most common attack scenarios.

5 essential cybersecurity actions for a small business

Action 1: enable MFA and organize account access

MFA, or multi-factor authentication, requires an additional login confirmation beyond the password. It is one of the most important protections for a small business because many attacks start with password theft.

Enable MFA first for:

  • corporate email
  • Microsoft 365 or Google Workspace
  • administrator accounts
  • accounting system
  • banking and payments
  • CRM system
  • online store
  • code repositories
  • remote access and VPN

The best direction is phishing-resistant methods such as security keys or passkeys. If the company is not ready for these methods yet, an authenticator app is a good first step. SMS is better than no MFA, but it should not be the target method for administrator and finance accounts.

What to do in practice?

  • list all important company accounts
  • enable MFA first for email and administrators
  • remove former employee accounts
  • prohibit shared administrator accounts
  • define who can reset passwords and MFA
  • use a password manager for company passwords
  • review access to key systems once per quarter

Evidence to prepare: critical account list, MFA status, administrator list and latest access review.

Action 2: create backups and test recovery

Backups protect against ransomware, hardware failure, employee mistakes, deleted files and lost devices. For a small business, backups may decide whether the company returns to work in one day or loses data permanently.

The most important data to protect:

  • customer documents
  • contracts
  • invoices and accounting data
  • email
  • customer databases
  • projects and work files
  • online store data
  • source code and technical documentation
  • system configurations

The statement that “backup works” is not enough. The company must check whether it can restore data. Many companies discover the problem only after an attack, when backups turn out to be incomplete, outdated, corrupted or encrypted together with the rest of the environment.

What to do in practice?

  • define which data is critical for business operations
  • run backups automatically, not manually from time to time
  • store backups separately from the main environment
  • protect backup access with MFA
  • make sure an attacker cannot easily delete backups
  • test recovery at least quarterly for critical data
  • record the recovery test result

Evidence to prepare: backup register and latest recovery test report.

Action 3: update and secure devices and applications

Outdated systems, browsers, plugins, routers, VPNs, online stores and cloud applications may become entry points into the company. Updates are not only a convenience issue. They often fix vulnerabilities that attackers can exploit.

A small business should pay particular attention to:

  • employee computers
  • phones used for work
  • operating systems
  • browsers
  • office software
  • routers and network devices
  • VPN
  • online store platform
  • website plugins
  • accounting and CRM applications

Configuration is also important. Devices should use screen lock, disk encryption, malware protection and limited administrator rights.

What to do in practice?

  • enable automatic updates where possible
  • remove old software the company no longer uses
  • block random software installation
  • do not work daily from an administrator account
  • enable disk encryption on laptops
  • enable screen lock and a strong PIN
  • secure phones used for work
  • regularly check website and online store updates

Evidence to prepare: company device list, update status, encryption status and unsupported device list.

Action 4: train employees to recognize and report phishing

Phishing is one of the most common attack methods against small businesses. A message may look like an invoice, customer document, email login link, request from the boss, bank message, courier notification or bank account change request.

Training should not be a long annual presentation. Employees should know a simple rule: pause, check, do not click under pressure and report suspicious messages.

Key warning signs:

  • time pressure
  • urgent payment request
  • bank account change request
  • login link from a message
  • unexpected attachment
  • request for password or MFA code
  • unusual tone from a known person
  • message from a supplier with a new bank account
  • QR code leading to login

What to do in practice?

  • define one simple phishing reporting channel
  • tell employees that fast mistake reporting is good
  • do not punish clicking if the employee reports quickly
  • introduce another-channel confirmation for supplier bank account changes
  • train finance, HR and the board separately
  • teach that MFA codes must never be shared
  • remind employees briefly and regularly

Evidence to prepare: phishing reporting instruction, trained employee list and suspicious message report register.

Action 5: prepare a simple incident response plan

A small business does not need a hundred pages of procedures at the beginning. It needs a simple plan answering: what do we do if an account is compromised, a computer is encrypted, files disappear, a customer reports a suspicious message or someone makes an unauthorized payment?

The plan should be available even if email or the company drive does not work. It is best to keep an offline copy or printed version for decision makers.

The plan should include:

  • who makes decisions
  • who contacts IT or an external provider
  • who contacts customers
  • who contacts the bank
  • who contacts the insurer
  • who assesses legal obligations
  • how to disconnect an infected device
  • how to block a compromised account
  • how to recover data from backups
  • how to communicate if email is down

What to do in practice?

  • prepare an emergency contact list
  • define who can make decisions in a crisis
  • describe the first 60 minutes after an incident
  • prepare an alternative communication channel
  • write down the account lock and password reset procedure
  • write down the device disconnection procedure
  • exercise an email compromise or ransomware scenario

Evidence to prepare: one-page incident response plan, emergency contact list and exercise note.

What should be done first if time is limited?

If a small business can do only a few things this month, the best order is simple:

  1. enable MFA for email and administrators
  2. check whether backups actually work
  3. update computers, browsers, router and website
  4. tell employees where to report phishing
  5. prepare a contact list and first response plan

This is not a complete cybersecurity programme, but it is a strong start. In many small businesses, these five actions significantly reduce the risk of the most common incidents.

Implementation checklist for a small business

Accounts and access

  • does corporate email have MFA?
  • do administrator accounts have MFA?
  • were former employee accounts removed?
  • are passwords unique?
  • does the company use a password manager?
  • does the company know who has access to banking, accounting and CRM?

Backups

  • does the company know which data is critical?
  • are backups automatic?
  • are backups protected against deletion?
  • are backups separated from the main environment?
  • has recovery been tested?
  • is the test result recorded?

Devices and applications

  • are computers up to date?
  • are phones used for work secured?
  • do laptops have disk encryption?
  • do employees avoid daily work from administrator accounts?
  • are the website and plugins up to date?
  • was unused software removed?

Phishing and people

  • do employees know where to report phishing?
  • does finance know how to confirm supplier bank account changes?
  • do employees know that MFA codes must not be shared?
  • does the company have a no-blame reporting rule?
  • was the training practical and short?

Incident response

  • does the company have an emergency contact list?
  • is it clear who decides in a crisis?
  • is there a first 60-minute plan?
  • is it clear how to block a compromised account?
  • is it clear how to disconnect an infected device?
  • is the plan available offline?

30, 60 and 90-day action plan

First 30 days

  • enable MFA for email, administrators and the most important systems
  • list key accounts and applications
  • remove former employee accounts
  • identify where backups are stored
  • perform the first recovery test for a selected file or folder
  • update computers, browsers and router
  • prepare a simple phishing reporting instruction
  • prepare an emergency contact list

Days 31 to 60

  • expand MFA to accounting, CRM, online store and remote access
  • deploy a password manager
  • organize permissions to files and customer data
  • set automatic backups for critical data
  • test recovery of a larger data set
  • secure phones used for work
  • run short phishing training
  • write a one-page incident response plan

Days 61 to 90

  • check which applications and devices are still outside control
  • review administrator access
  • check website and online store updates
  • test recovery of critical data
  • exercise an email compromise or ransomware scenario
  • prepare a simple security report for the owner or board
  • define the next 6-month action plan

What documents and evidence should be prepared?

Basic documents

  • system and application list
  • administrator account list
  • list of people with access to banking, accounting and customer data
  • simple password and MFA policy
  • phishing reporting instruction
  • incident response plan
  • emergency contact list

Technical evidence

  • MFA activation report
  • latest backup recovery test report
  • company device list
  • device update status
  • laptop encryption status
  • former employee account removal register
  • access review register

Organizational evidence

  • list of employees trained on phishing
  • confirmation of security rule communication
  • incident exercise note
  • suspicious message report register
  • exception decisions
  • security report for the owner or board

Common small business mistakes

Mistake 1: thinking the company is too small to be attacked

Attacks are often automated. Criminals do not need to know the company to exploit a weak password, missing MFA, vulnerable website or outdated VPN.

Mistake 2: relying only on an IT provider

An IT provider can help technically, but the business owner must know what is critical, what risk is accepted and whether backups and MFA really work.

Mistake 3: backups without testing

A backup that has not been tested is not reliable protection. The company should regularly check whether it can restore data.

Mistake 4: no MFA for email

Compromised email can give an attacker access to invoices, documents, password resets and customer communication.

Mistake 5: shared passwords and administrator accounts

Shared accounts make control and accountability difficult. It becomes unclear who performed an action and whose access must be removed when someone leaves.

Mistake 6: phishing training once every few years

Employees need short practical reminders. Phishing changes quickly and attacks increasingly look professional.

Mistake 7: no first-hours incident plan

During a crisis, time matters. A company that starts thinking about who to call and what to disconnect only after the incident loses valuable hours.

How to measure progress?

Access metrics

  • percentage of accounts with MFA
  • number of administrator accounts
  • number of former employee accounts
  • number of shared accounts
  • number of systems without an owner

Backup metrics

  • number of systems covered by backups
  • date of the latest recovery test
  • time needed to restore data
  • number of critical data sets without backup

Device metrics

  • number of company devices
  • number of outdated devices
  • number of devices without encryption
  • number of unused applications to remove

People and response metrics

  • number of trained employees
  • number of suspicious messages reported
  • response time to a phishing report
  • time needed to block a compromised account
  • date of the latest incident exercise

Business example

A small service company has 18 employees. It uses cloud email, shared drive, accounting software, CRM and online banking. It has no security department and IT is handled by an external provider.

A short review shows that MFA is enabled only for some employees, a former employee still has drive access, backups are being created but have never been tested and employees do not know where to report phishing.

The company does not start with a large project. Within 30 days, it enables MFA for email and administrator accounts, removes former employee accounts, tests data recovery, updates computers and prepares a phishing reporting instruction.

After 90 days, the company has MFA in critical systems, tested backups, trained employees, an emergency contact list and a simple response plan. It is still not perfectly secure, but it has materially reduced the risk of the most common attacks.

How can ccyber.io help?

ccyber.io helps small businesses implement cybersecurity in a practical way, without excessive bureaucracy and without buying tools that do not solve the most important problems.

We can support your organization with:

  • SME Cybersecurity Starter Pack
  • basic cybersecurity audit
  • MFA implementation
  • Microsoft 365 or Google Workspace review
  • backup review and recovery test
  • employee phishing training
  • incident response plan preparation
  • permission and administrator account review
  • 30, 60 and 90-day cybersecurity roadmap
  • evidence pack for a customer, audit or insurer

The best first step is a short SME cybersecurity assessment. It helps check whether the company has the most important protections enabled, where the biggest gaps are and what should be done first.

FAQ

Does a small business really need cybersecurity?

Yes. Small businesses use email, banking, cloud services, accounting systems, customer data and internet-connected devices. That is enough to become a target of phishing, ransomware or fraud.

Where should a small business start with cybersecurity?

The best starting point is MFA for email and administrators, tested backups, device updates, phishing training and a simple incident response plan.

Do I need an expensive security system?

Not always. At the beginning, the biggest impact comes from the basics. Once MFA, backups, updates, access control and response planning are in place, additional tools can be selected more sensibly.

Is cloud backup enough?

It may help, but it is not always enough. The company must check whether data can be restored, whether backups cannot be deleted together with primary data and whether backup access is protected.

Should MFA be enabled for everyone?

Eventually yes, but start with email, administrators, finance, banking, cloud systems and remote access. MFA can then be expanded to more applications.

How often should employees be trained?

Short and regular training works better than long training once a year. A good minimum is onboarding training, quarterly reminders and additional training for finance, HR and the board.

What should a simple response plan contain?

It should include contacts, roles, first actions after an incident, account blocking, device disconnection, data recovery and communication with customers and the IT provider.

Does cybersecurity help in B2B sales?

Yes. More customers ask about MFA, backups, training, incident response, data protection and audits. A small business with evidence of basic controls looks more trustworthy as a supplier.

Summary

A small business does not need to start cybersecurity with a large audit, complex standards or expensive tools. First, it should implement five actions that reduce the most common risks: MFA, backups, updates, phishing training and a simple incident response plan.

These actions protect email, data, devices, money, customers and business continuity. The key is not to postpone the basics. A compromised account, data loss or ransomware may cost a small business much more than a structured rollout of basic protections.

The best approach is simple: start with actions that give the highest impact, document evidence, test recovery and return to the checklist regularly. Cybersecurity for a small business should be practical, understandable and sustainable.

Sources

Cybersecurity Checklist for SMEs: 12 Steps to Start With

Small and medium-sized businesses do not need to start cybersecurity with complex projects. The right first step is to organize the basics: access, MFA, backups, updates, training, phishing protection, cloud security, suppliers and incident response. Here is a practical 12-step cybersecurity checklist for SMEs.

Author: CCyber Editorial Team

Short answer

SMEs should start cybersecurity with 12 practical steps: inventory systems and data, assign security ownership, enable MFA, use a password manager, test backups, update systems, protect email, review permissions, train employees, secure cloud environments, prepare an incident response plan and check suppliers. This minimum baseline can significantly reduce risk without building a large internal security team.

Last updated

July 2026

Who this article is for

  • small and medium-sized business owners
  • SME boards
  • operations directors
  • CFOs
  • IT managers
  • companies without an internal security team
  • software houses and service companies
  • B2B suppliers
  • companies preparing for customer requirements, NIS2 or cyber insurance

Key takeaways

  1. An SME does not need a complex cybersecurity programme at the beginning. It needs a simple plan, clear ownership and basic controls.
  2. The highest-impact first actions are MFA, backups, updates, training, email protection and access cleanup.
  3. Cybersecurity should be documented because customers, insurers and auditors increasingly expect evidence.
  4. Companies that are not directly covered by NIS2 may still receive security requirements from larger customers.
  5. The best first step is a quick self-assessment and a 30, 60 and 90-day action plan.

Why should SMEs start with a checklist?

Small and medium-sized businesses often delay cybersecurity because it seems expensive, technical and audit-heavy. That is a mistake. Most companies can significantly reduce risk by organizing the basics.

A good checklist helps answer three questions:

  • what do we need to protect?
  • what should we implement first?
  • what evidence can we show to a customer, board, insurer or auditor?

Cybersecurity for SMEs should be practical. The goal is not to build a large compliance system immediately. The goal is to avoid losing access to data, reduce exposure to phishing and know how to respond when something goes wrong.

Cybersecurity checklist for SMEs: 12 steps

Step 1: create an inventory of critical systems, data and accounts

You cannot protect what you cannot see. The first step is a simple inventory of systems, applications, accounts, laptops, servers, cloud services and data.

The inventory should include:

  • business email
  • Microsoft 365 or Google Workspace
  • accounting system
  • CRM
  • website
  • online store
  • production or operational systems
  • code repositories
  • laptops and mobile devices
  • administrator accounts
  • customer, employee and supplier data

Evidence to prepare: a simple register of systems, data and owners.

Step 2: assign responsibility for cybersecurity

In many SMEs, cybersecurity belongs to nobody. IT handles technology, management handles sales and finance, and employees do not know where to report a suspicious email. This creates confusion.

The company should appoint a person responsible for coordinating security. This does not have to be a full-time CISO. In a smaller organization, it can be the owner, a board member, IT manager, office manager or an external vCISO advisor.

This person should coordinate:

  • security actions
  • communication with IT suppliers
  • backup and update follow-up
  • employee training
  • security reports from employees
  • reporting to management

Evidence to prepare: a board decision or short note naming the cybersecurity owner.

Step 3: enable MFA on the most important accounts

MFA, or multi-factor authentication, is one of the most important controls for SMEs. It protects the company when a password is phished, guessed or leaked.

MFA should be mandatory at least for:

  • business email
  • administrator accounts
  • Microsoft 365 or Google Workspace
  • accounting systems
  • CRM
  • online banking
  • code repositories
  • hosting and domain panels
  • VPN

Authentication apps, hardware security keys or phishing-resistant methods are preferred. SMS is better than no MFA, but it should not be the first choice for critical accounts.

Evidence to prepare: a list of systems with MFA enabled and screenshots of settings for critical accounts.

Step 4: organize passwords and deploy a password manager

Passwords stored in notes, spreadsheets or unmanaged browsers are a common SME problem. The company should deploy a password manager and set simple rules.

Good password rules for SMEs:

  • every account has a unique password
  • passwords are long and automatically generated
  • business passwords are not reused privately
  • administrator passwords are not shared without control
  • access is removed when an employee leaves
  • critical accounts use MFA

A password manager reduces chaos and lowers the risk that one leaked password opens access to multiple systems.

Evidence to prepare: password policy and list of systems covered by the password manager.

Step 5: check backups and recovery tests

A backup is not a strategy if nobody has tested recovery. Many companies discover this only after ransomware, an outage or an employee mistake.

A good SME backup should cover:

  • data critical to business operations
  • email and cloud files
  • accounting system
  • CRM
  • website or online store
  • code repositories
  • system configurations

The company should know two values:

  • RPO, meaning how much data the company can afford to lose
  • RTO, meaning how quickly the company must return to operation

The key question is whether the company can restore data in practice, not only in theory.

Evidence to prepare: backup policy, backup schedule and recovery test report.

Step 6: update systems, applications and devices

Outdated systems are one of the simplest entry points for attackers. SMEs should have a basic update process, even without a large IT team.

Updates should cover:

  • operating systems
  • browsers
  • office software
  • accounting systems
  • website CMS and plugins
  • server software
  • routers and firewalls
  • NAS devices
  • mobile apps used for work

For critical security patches, the company should set a shorter implementation deadline than for normal feature updates.

Evidence to prepare: system list, update schedule and confirmation of critical patching.

Step 7: protect email and prepare people for phishing

Business email is one of the most common attack channels for SMEs. Phishing can lead to password theft, fake invoices, payment fraud, malware or account takeover.

The minimum baseline should include:

  • MFA for email
  • anti-phishing filters
  • protection against malicious attachments
  • basic SPF, DKIM and DMARC configuration
  • a process for reporting suspicious emails
  • a rule to confirm bank account changes through another channel

The biggest change is not only technical. Employees must know what to do when a message looks suspicious.

Evidence to prepare: phishing reporting procedure, MFA confirmation and SPF, DKIM and DMARC configuration record.

Step 8: limit permissions and clean up accounts

Employees often have more access than they need. Former employees may still have active accounts. Administrator accounts are sometimes used for everyday work. This increases the impact of an incident.

SMEs should apply the principle of least privilege. This means that users have access only to what they need for their work.

Check:

  • who has administrator access
  • who can access customer data
  • who can access financial systems
  • who can access domains and hosting panels
  • who can access code repositories
  • whether former employee accounts are disabled
  • whether shared accounts are truly needed

Evidence to prepare: access review report and procedure for granting and removing access.

Step 9: train employees in cyber hygiene

Training should not be a boring slide deck once a year. Good SME training should focus on real situations: phishing, fake invoices, passwords, remote work, MFA, phone scams and safe use of AI tools.

Minimum training topics for SMEs:

  • how to recognize phishing
  • how to report a suspicious message
  • how to use MFA
  • how to create and store passwords
  • how to protect customer data
  • how to respond to a suspicious phone call
  • what not to paste into AI tools
  • what to do after clicking a suspicious link

Training should end with a short test or completion confirmation. This is useful for audits, customer requirements and cyber insurance.

Evidence to prepare: attendance list, training materials, test result and training schedule.

Step 10: secure cloud, Microsoft 365 or Google Workspace

Many SMEs now operate mainly in the cloud. Email, files, meetings, documents and user accounts are often more important than a local server. Cloud configuration is therefore critical.

In Microsoft 365 or Google Workspace, check:

  • MFA for all users
  • separate administrator accounts
  • security logging and alerts
  • external file sharing
  • access from personal devices
  • automatic email forwarding rules
  • suspicious logins
  • backup of cloud data

A common mistake is assuming that cloud automatically solves all security problems. The provider protects the infrastructure, but configuration, access rights and user behavior still require management.

Evidence to prepare: Microsoft 365 or Google Workspace configuration review, administrator list and MFA confirmation.

Step 11: prepare a simple incident response plan

An incident response plan does not need to be 80 pages long. For an SME, the most important thing is that employees know who to contact, who makes decisions and what to do in the first hour.

The plan should answer:

  • who receives the report?
  • who decides whether to disconnect a system?
  • who contacts the IT supplier?
  • who informs management?
  • who communicates with customers?
  • when does the incident need to be reported to the relevant party or authority?
  • where is the emergency contact list?
  • how do we check whether backup works?

It is worth running a short tabletop exercise. The scenario can be simple: ransomware, email takeover or a fake invoice.

Evidence to prepare: incident response procedure, emergency contact list and tabletop exercise note.

Step 12: check suppliers and customer requirements

SMEs rarely operate alone. A company uses accounting services, IT providers, hosting, marketing agencies, cloud services, payment systems and many SaaS tools. Each supplier can increase or reduce risk.

Start with a supplier list and check:

  • which suppliers have access to company data
  • which suppliers have administrator access
  • which suppliers support critical systems
  • whether contracts include security requirements
  • how the supplier reports incidents
  • whether the supplier uses MFA
  • whether the supplier has backup and continuity procedures

At the same time, check customer requirements. More large companies now ask suppliers about MFA, backups, training, incident procedures, security tests and regulatory compliance.

Evidence to prepare: supplier register, short supplier risk assessment and list of security requirements in contracts.

30, 60 and 90-day implementation plan

First 30 days: fast actions with the highest impact

  • create an inventory of systems and accounts
  • enable MFA for email and administrators
  • check backups and run a recovery test
  • disable former employee accounts
  • run short phishing training
  • assign cybersecurity responsibility

Days 31 to 60: organize processes

  • deploy a password manager
  • prepare an incident response procedure
  • check system and device updates
  • perform an access review
  • review Microsoft 365 or Google Workspace configuration
  • create a supplier register

Days 61 to 90: evidence and maturity

  • document an information security policy
  • prepare a basic risk register
  • run an incident response exercise
  • check customer and insurer requirements
  • prepare a cybersecurity evidence pack
  • plan actions for the next 6 months

Minimum cybersecurity evidence pack for SMEs

Even a small company should have a basic evidence pack that can be shown to a customer, insurer, auditor or board.

Documents

  • information security policy
  • password and MFA policy
  • incident response procedure
  • backup policy
  • system and data register
  • supplier register

Technical evidence

  • MFA confirmation
  • backup test report
  • administrator account list
  • access review report
  • system update confirmation
  • basic Microsoft 365 or Google Workspace security report

Organizational evidence

  • training attendance list
  • training materials
  • knowledge test results
  • incident exercise note
  • decision naming the person responsible for security

Common SME mistakes

Mistake 1: believing that “we are too small to be attacked”

Many attacks are automated. Criminals do not always choose a company manually. They look for weak passwords, lack of MFA, vulnerable websites, misconfigured email and outdated systems.

Mistake 2: backup without recovery testing

A backup that has never been tested creates false confidence. Recovery testing should be performed regularly.

Mistake 3: one administrator account used for everything

An administrator account should be used only for administrative tasks. Daily work on such an account increases the impact of infection or account takeover.

Mistake 4: no procedure after clicking a phishing link

Employees should know that fast reporting is more important than hiding the mistake. The company needs a simple incident reporting channel.

Mistake 5: no supplier control

IT providers, hosting, SaaS tools and agencies with system access can be critical to security. No supplier control means no control over part of the risk.

Business example

A service company has 35 employees. It uses Microsoft 365, an accounting system, CRM, a WordPress website, several laptops and an external IT provider. The company has no security team, but serves larger B2B customers.

A short assessment shows that the company does not have MFA enabled for all accounts, Microsoft 365 backup has not been tested, several former employees still have access to selected tools and employees do not know how to report phishing.

Within 30 days, the company can significantly reduce risk: enable MFA, clean up accounts, test backups, train the team and prepare a simple incident response procedure. This does not require a large project. It requires a decision, priorities and consistency.

How can ccyber.io help?

ccyber.io helps SMEs organize cybersecurity quickly without unnecessary complexity or expensive overengineering.

We can support your company with:

  • SME Cybersecurity Starter Pack
  • basic cybersecurity audit
  • Microsoft 365 security review
  • MFA implementation
  • backup review and recovery test
  • phishing training for employees
  • incident response procedure
  • supplier review
  • cybersecurity evidence pack for customers or insurers

The best first step is a short self-assessment. After that, the company knows which actions have the highest impact and what should be done in the first 30 days.

FAQ

Does an SME really need cybersecurity?

Yes. SMEs often have fewer controls than large organizations, while still using email, cloud systems, online banking, accounting software and customer data. That is enough for a cyberattack to disrupt operations.

Where should a small business start?

The best starting point is an inventory of systems, MFA, backups, updates, access review and employee phishing training.

Is MFA necessary?

MFA should be treated as a basic control, especially for email, administrator accounts, cloud systems, online banking, CRM and financial systems.

Is cloud backup enough?

Not always. The company should check what is actually backed up, how long data is retained and whether it can be restored quickly.

Does an SME need ISO/IEC 27001?

Not always. ISO/IEC 27001 can be useful, but many SMEs should first implement basic controls and documentation. Certification can be a later step if customers or the market require it.

Does my company need to prepare for NIS2?

It depends on the company’s sector, size and role in the supply chain. Even if the company is not directly covered by NIS2, it may receive requirements from customers that are regulated.

How often should employees be trained?

At minimum, employees should be trained during onboarding and receive regular refreshers. In practice, a short quarterly programme works well: phishing, passwords, MFA, customer data and incident response.

How much does basic cybersecurity for an SME cost?

The cost depends on the number of employees, systems and current maturity. Many high-impact actions, such as MFA, access cleanup, training and incident response planning, can be started quickly and without a large budget.

Summary

Cybersecurity for SMEs does not need to begin with a complex audit, expensive tool or multi-month project. The best start is 12 practical steps that reduce risk where companies are most commonly exposed.

The most important actions are MFA, backups, updates, access cleanup, email protection, training, incident response planning and supplier control.

A company that implements these basics and can show evidence will be better prepared for incidents, customer requirements, cyber insurance and future regulations.

Sources

We write about regulations such as NIS2, DORA, CRA and ISO 27001, cybersecurity for SMEs and critical infrastructure, as well as cyber hygiene, emerging threats and building security awareness within organisations.

Every article delivers practical knowledge - no jargon, just concrete steps you can act on to effectively protect your data, people and business continuity.