Many serious cyber incidents at small businesses do not involve sophisticated attacks. They exploit gaps in the basics: unpatched systems, weak or stolen credentials, backups that do not restore and access that is too broad. Getting the fundamentals right, and keeping them right, is the core of security work for most smaller organisations.

This guide sets out a practical starting baseline for a small or mid-size business. It is not a full framework implementation. Which controls you prioritise should follow your context, risks, data and obligations, and the controls need governance, risk assessment and ongoing monitoring around them to stay effective.

Why the basics matter

Attackers usually take the easiest route. For SMEs that often means a control that was never implemented rather than one that was defeated: phishing succeeds because MFA was missing, ransomware spreads through unpatched systems, data leaks through over-broad access, and recovery fails because backups were never tested.

Stolen credentials and exploited vulnerabilities are both important initial access vectors in industry breach reports such as the Verizon Data Breach Investigations Report, and their relative ranking varies between years and datasets. Rather than rely on a ranking, prioritise by the systems you expose to the internet, your own incident history, the threats relevant to your sector and your specific risks.

The baseline controls

Multi-factor authentication

MFA means a stolen password alone is not enough to access an account. Enable it on email, remote access, cloud services and any system reachable from the internet, and make it mandatory for accounts with access to sensitive data or administrative functions. Authenticator apps and phishing-resistant methods such as passkeys are stronger than SMS codes. Track coverage and document any exclusions. Our MFA guide covers rollout in more detail.

Patch management

Set patch deadlines by risk: severity, whether the vulnerability is known to be exploited (for example, listed in the CISA Known Exploited Vulnerabilities catalogue), exposure to the internet and the system's importance to the business. Test updates where a failed update would hurt, record exceptions, and apply compensating controls when a patch cannot be applied in time. As an illustrative policy only, a business might aim for 48 hours for exploited flaws in internet-facing systems, 7 days for workstations and a monthly cycle for other third-party software. If you hold Cyber Essentials, its own deadline for high and critical updates also applies. A documented process, even a simple one, closes the gap between a patch being available and being applied.

Endpoint protection

Every device that accesses business systems needs modern endpoint protection, including laptops used at home. Endpoint detection and response (EDR) tools add device telemetry, behavioural detection, investigation and response on top of signature-based antivirus. They do not guarantee that unknown threats will be caught: effectiveness depends on full coverage, sound configuration and someone with the capacity to review alerts and act on them. Microsoft Defender for Business, for example, is included in Microsoft 365 Business Premium. Unmanaged personal devices accessing company email or files are a significant and often overlooked exposure.

Access control and least privilege

Users should only have access to the systems and data their role requires. Administrator accounts should not be used for day-to-day work. Privileged access should be reviewed regularly and revoked when no longer needed. Stale accounts from former employees, contractors or testing are a common entry point. A quarterly review of who has access to what is a small cost compared with the incident it can prevent.

Backup and tested recovery

Backups are only useful if they can be restored quickly enough to matter. Follow the 3-2-1 rule: three copies of data, on two different media types, with one stored offsite or in a separate cloud account not connected to the primary environment. Set the test frequency by system criticality, the rate of change and your continuity objectives; critical services may need frequent partial restores plus a full recovery exercise on a different cycle. Record the measured recovery time, whether the data was complete and intact, and whether the recovery time objective (RTO) and recovery point objective (RPO) set by the business were met. The measured time shows whether the RTO is achievable; it is not the RTO itself. Ransomware often targets backups, so immutable or offline copies should be part of the design for any organisation handling sensitive data.

Network segmentation

Flat networks allow an attacker who gains access to one system to move freely to others. Basic segmentation, separating guest Wi-Fi from the corporate network, isolating operational technology from IT systems and restricting server-to-server communication, limits the blast radius of a compromise. This does not require complex infrastructure. VLAN configuration on a managed switch is sufficient for many SME environments.

Email security

Email is a primary delivery mechanism for phishing, malware and business email compromise. At a minimum, configure SPF, DKIM and DMARC records to prevent domain spoofing. Use a mail gateway or filtering service that inspects attachments and links before delivery. Train staff to recognise phishing, but do not rely on training alone. Technical controls catch what awareness misses.

Incident response plan

An incident response plan does not need to be long. It needs to answer three questions: who decides when an incident is serious enough to escalate, who gets called when it is, and what do we do in the first four hours. Organisations without a plan make worse decisions under pressure and take longer to contain incidents. Write it down and test it with a short tabletop exercise before you need it. For ransomware specifically, see our ransomware response guide.

If personal data is involved, the plan should also cover UK GDPR. A reportable personal data breach must be notified to the ICO without undue delay and, where feasible, within 72 hours of becoming aware of it, unless it is unlikely to result in a risk to individuals' rights and freedoms. Affected individuals must be told without undue delay when the breach is likely to result in a high risk to them. Not every security event is a reportable breach, but the assessment has to be quick and recorded.

Frameworks that map to this baseline

If your organisation operates in a regulated sector or is considering cyber insurance, several frameworks are worth understanding in relation to this baseline.

Cyber Essentials (UK) covers five technical controls: firewalls, secure configuration, user access control, malware protection and security update management. It provides useful third-party validation of the basics, and many public sector contracts and some insurers ask for it. More detail follows below.

NIST Cybersecurity Framework 2.0 is free and voluntary. It organises security into six functions: Govern, Identify, Protect, Detect, Respond and Recover. NIST's Small Business Quick-Start Guide (SP 1300) is a practical entry point. The checklist below shows which CSF functions each baseline area contributes to.

ISO 27001 goes significantly further, requiring a full information security management system. You can implement it with or without external certification; certification is a choice, often driven by client or tender requirements. The baseline controls described here cover only part of what ISO 27001 expects. See our ISO 27001 guide for SMEs for a more detailed walkthrough.

NIS2 applies to medium and large organisations in specified sectors across the EU and imposes incident reporting and minimum security measures. It matters to UK businesses with EU operations or EU clients in those sectors. This baseline is a foundation for NIS2 measures, not a substitute for them. Our NIS2 guide covers the full scope of obligations.

Starting checklist: minimum evidence

Use this as a starting checklist, not as full NIST CSF 2.0 or UK GDPR compliance. The CSF column shows where each area contributes; no single area satisfies a whole CSF function.

Control areaCSF 2.0 (examples)Minimum evidence
Governance and riskGV.RR, GV.RM, ID.RANamed owner, risk register, agreed priorities
Asset inventoryID.AMDevices, SaaS and systems listed, each with an owner
Endpoint protectionPR.PS, DE.CMCoverage by device, records of alerts handled
Identity and accessPR.AAMFA coverage, privileged accounts, approved exclusions
Backup and recoveryPR.DS, RC.RPRestore tests, results against RTO and RPO
Vulnerability managementID.RA, PR.PSFindings, deadlines, remediation, documented exceptions
Incident responseRS.MA, RS.CO, ID.IMContacts, procedures, exercise results
Suppliers and data protectionGV.SC, PR.DSCritical suppliers, access granted, data handling terms

Cyber Essentials as a starting point

The UK government-backed Cyber Essentials scheme is an accessible entry point if you want to establish a credible security posture. The basic certification is a self-assessment, verified by a certification body, covering firewalls, secure configuration, user access control, malware protection and security update management. Fees are set by IASME and vary with organisation size, so check the current price list before budgeting.

Cyber Essentials Plus adds a hands-on technical assessment of your systems by an assessor. IASME Cyber Assurance goes further, adding governance and risk management requirements.

If your IT hygiene is already in reasonable shape, the basic certification can often be completed within a few weeks. Cyber Essentials is also required for many UK central government contracts that involve handling personal information or providing certain ICT services.

Cyber Essentials does have clear limits. It does not cover social engineering, phishing simulation, incident response planning or business continuity. A certificate will not stop an attacker who targets your people rather than your systems. Treat it as the floor and the starting gun for further work.

The cost of skipping the basics

The most common reason SMEs delay security investment is cost. Government survey data helps put the risk in context.

The UK government's Cyber Security Breaches Survey 2024 found that half of UK businesses (50%) reported a breach or attack in the previous 12 months. It estimated that the single most disruptive breach cost businesses of any size an average of about £1,205, rising to about £10,830 for medium and large businesses. Averages hide wide variation between incidents.

Ransomware and similar incidents can bring recovery costs, downtime, investigation, legal costs and lost revenue. A sound investment decision weighs those impacts and the likelihood of the scenario against the cost of the controls. A simple starting point is to estimate what one to three days of downtime would cost and compare it with the cost of tested backups and recovery.

Cyber insurers increasingly ask about controls such as MFA, backups and patching before offering cover, and an undisclosed gap can complicate a claim.

UK GDPR adds a regulatory dimension. Article 32 requires security appropriate to the risk. The higher maximum fine is £17.5 million or 4% of total worldwide annual turnover, whichever is higher, with a lower tier of £8.7 million or 2% for other infringements, including the breach notification duties. These are ceilings applied after an ICO investigation that weighs seriousness and other factors, not automatic penalties.

Where to start if you are starting from scratch

Trying to implement everything at once rarely works. A sensible order for many businesses:

  • Owner and priorities: name who is responsible and agree what matters most, this week
  • MFA on email and remote access: this week
  • Patch management process: define risk-based deadlines, document and execute within the month
  • Backup testing: confirm backups exist and can be restored within your RTO
  • Access review: remove stale accounts and excess privileges
  • Endpoint protection: verify coverage across all devices
  • Email security configuration: SPF, DKIM, DMARC
  • Incident response plan: one page, written down and tested

A security assessment gives you a clear view of where you stand against this baseline, what the gaps are, and what the priority order should be for your specific environment. If you are unsure whether your environment needs attention, our article on IT infrastructure warning signs is a good place to start.

Common questions

Is the NIST CSF mandatory in the UK?

No. NIST CSF 2.0 is a free, voluntary framework from the US National Institute of Standards and Technology. There is no legal requirement to adopt it in the UK, although clients, particularly international ones, may require alignment with it in contracts or security questionnaires.

Does UK GDPR require EDR or MFA?

Not by name. Article 32 requires appropriate technical and organisational measures, proportionate to the risk, but does not specify products or particular controls such as EDR or MFA. Those controls are common ways of showing that your security is appropriate.

Is this baseline enough for UK GDPR compliance?

No. It covers part of the security obligation. UK GDPR also requires a lawful basis for each processing activity, transparency, handling of individuals' rights, records of processing, processor contracts and a breach procedure, among other obligations.