IT Security· 20 min read· Author: WSV Redaktion· Reviewed on

IT Security for SMEs: A Guide for Small and Mid-Sized Businesses

IT security in your business, planned rather than improvised: which framework fits your company size (DIN SPEC 27076, VdS 10000, ISO 27001, NIS2), plus a prioritised checklist for week 1, month 1 and quarter 1, linked to the guides that go deeper.

Anyone who takes a serious look at IT security in their business for the first time quickly runs into a wall of standards, acronyms and vendor promises. DIN SPEC 27076, VdS 10000, ISO 27001, NIS2: which of these actually matter for a company with 12, 60 or 180 employees? And where do you start on Monday morning? This guide answers both questions. It maps the common frameworks to company size and gives you a prioritised IT security checklist for your business, split into week 1, month 1 and quarter 1.

Think of this guide as a map. For almost every item there is a dedicated guide that goes into detail. If you want to understand how attacks on small firms actually unfold and how to fend them off, read our guide on stopping cyberattacks on small businesses alongside this one. Here we focus on the big picture: what belongs in the plan, in which order, and which framework suits you.

What is IT security? Definition and protection goals

IT security covers all technical and organisational measures that protect your IT systems and the information they process. You will also hear the term information security. It is slightly broader and includes information on paper or in people's heads. For a small or mid-sized business the distinction matters less, because both pursue the same three protection goals:

  • Confidentiality: Only authorised people can access information. Payroll is visible to accounting, not to the whole team, and customer data does not leave the company unchecked.
  • Integrity: Information stays correct and complete and is not altered unnoticed. A tampered bank account number on an invoice is a textbook integrity failure.
  • Availability: Authorised people can reach their data and systems when they need them. An encrypted server on a Monday morning is first and foremost an availability problem.

DIN Media's overview page on ISO/IEC 27001 names these three as the core goals of information security. They help you classify every measure: multi-factor sign-in mainly protects confidentiality, a tested backup mainly protects availability. If nobody can say which goal an investment strengthens, take a closer look before signing.

Why IT security matters so much for SMEs

Small and mid-sized businesses are rarely singled out. Many attacks are automated and scan for reachable remote access, unpatched systems or mailboxes with weak passwords. Company size hardly matters; the gap does.

At the same time, smaller firms have less slack. A large group can absorb the loss of one site. A trade business with 15 people that loses order data, email and phones can lose several days of revenue very quickly. Questions of responsibility and liability follow, which we cover in our guide Who is liable for data loss?

A third driver comes from outside. Customers, insurers and clients increasingly ask for evidence. Suppliers to larger organisations receive information security questionnaires. Cyber insurers ask about backups, multi-factor authentication and emergency plans. And NIS2 has added legal obligations in many sectors. IT security is therefore not only about protection but also about staying in business.

The four building blocks of IT security in your business

In practice it helps to split IT security into four building blocks. This is not a standard but a working structure, and it also organises this guide. Each block links to one or more in-depth guides.

1. Technology: securing network, devices and email

The firewall controls what passes between the internet and your network. The different operating models are explained in our guides on managed firewalls for businesses, firewall as a service for SMEs and, if your internet connection cannot tolerate downtime, high-availability firewall clusters. On endpoints, the focus is malware protection; our guide on choosing antivirus for businesses lists what to look for. Since most attacks start in the inbox, email security for companies belongs here too. And if you run your own website, do not forget its upkeep, as described in our guide on website maintenance.

2. Access: accounts, passwords and permissions

Stolen credentials are one of the easiest ways in. This block covers strong passwords, multi-factor sign-in, separate admin accounts and clean permission management. Start with password security in the workplace. A frequently overlooked detail is covered in our article on passwords in the Active Directory description field. When someone leaves, the offboarding checklist makes sure no orphaned accounts remain.

3. People: awareness and a reporting culture

Technology catches a lot, but not everything. Staff who spot a fake invoice and report suspicious messages without fear are a real line of defence. How training can work without boring people is the subject of our guide on IT security training for employees. Practical warning signs are listed in recognising phishing at work, and our piece on the human firewall explains why awareness is an ongoing task. Teams working from home need additional rules, summarised in setting up a secure home office.

4. Operations and emergencies: updates, backup, recovery and obligations

Security is operations. That means regular updates (patch management for SMEs), a robust backup strategy, an IT emergency plan and monitoring that flags problems before they escalate (monitoring IT systems). Regulatory duties belong here as well. Whether and how NIS2 affects you is covered in NIS2 for small businesses and implementing NIS2 in mid-sized companies.

Which framework fits which company size?

Standards are not an end in themselves. They give you a tested structure so nothing important is missed, and they provide evidence to third parties. What matters is that the effort matches the size and risk of your business. Here are the main frameworks, from lean to comprehensive.

BSI guidance for SMEs. Germany's Federal Office for Information Security (BSI) offers an accessible starting point with its brochure on cybersecurity for SMEs. Among other things, it explains why updates should be installed regularly and why antivirus protection and data backup matter so much. For very small firms this is a good start, but it is not evidence of anything.

DIN SPEC 27076 (CyberRisikoCheck). DIN SPEC 27076, a specification for IT security consulting for small and micro enterprises, was developed under the lead of the BSI. According to the BSI, the CyberRisikoCheck built on it covers 27 requirements across six topic areas. An IT service provider conducts an interview lasting one to two hours. The result is a report with a score and recommendations for every unmet requirement, ordered by urgency; the report also points to possible funding programmes. Note that the BSI stresses this is not a certification but a status assessment.

VdS 10005. VdS Schadenverhütung describes VdS 10005 as designed for companies with up to 20 employees, aiming at resource-appropriate protection of the IT landscape. For small firms that want formal evidence without building a full management system, it can be a sensible intermediate step.

VdS 10000. According to VdS, VdS 10000 is a certifiable information security management system (ISMS) designed for mid-sized companies, aligned with ISO/IEC 27001 and BSI IT-Grundschutz. It is set up to be leaner than a full ISO implementation and suits companies that want to organise information security on a lasting basis and prove it. For NIS2 entities, VdS has published VdS 10100, which builds on VdS 10000.

ISO/IEC 27001. The international standard sets out requirements for an ISMS. DIN Media notes that it can be applied regardless of an organisation's type, nature or size and is worthwhile even for smaller businesses. At its core is a risk assessment whose results are compared with the reference controls in Annex A and documented in a statement of applicability. In Germany there is also the option of "ISO 27001 on the basis of IT-Grundschutz", with a certificate issued by the BSI. The effort is considerable, but the standard is internationally recognised and often named in tenders and supplier requirements.

NIS2. NIS2 is not a standard but an EU directive, transposed into German law. In principle it applies to entities in the sectors listed in Annexes I and II of the directive that at least reach the thresholds for a medium-sized enterprise under the EU SME definition; put simply, 50 or more employees, or more than EUR 10 million in both annual turnover and balance sheet total. In certain cases smaller entities can also be covered. Entities in scope must, among other things, implement risk management measures, which Article 21 of the directive describes across ten areas, from risk analysis through backup and disaster recovery to multi-factor authentication. Under Article 23, significant incidents are reported in stages: an early warning within 24 hours, an incident notification within 72 hours and a final report no later than one month afterwards. Under Article 20, management bodies must approve the measures, oversee their implementation and take part in training. To find out whether your company may be in scope, start with the BSI's free NIS-2 applicability check. The BSI states that its result is not legally binding, but it gives you a first orientation. The BSI also states that the statutory registration deadline has already passed; entities in scope that have not yet registered should do so without delay. If in doubt, have the assessment reviewed by a lawyer.

Our view by company size

The following mapping is guidance from an IT service provider's perspective, not a requirement set by the standard bodies. Your sector, customer requirements and risk may point to a different choice.

  • Up to around 10 employees: Follow the BSI guidance, work through the checklist below and use a CyberRisikoCheck under DIN SPEC 27076 as a status assessment.
  • 10 to 50 employees: Start with a CyberRisikoCheck; if you need evidence and have up to 20 employees, look at VdS 10005. An emergency plan and documented responsibilities become essential in your own interest.
  • 50 to 250 employees: Check whether NIS2 may apply. Depending on customer and sector requirements, build an ISMS under VdS 10000 or ISO/IEC 27001.
  • Regardless of size: If customers or tenders require a specific certificate, that requirement decides. Choose a path that can later lead to ISO 27001 certification.

How to proceed: IT security step by step

Before you dive into the checklist, a clear sequence helps. It stops you spending money on isolated measures while the real gap stays open.

  1. Assign responsibility. Name one person to drive the topic and clarify who decides. IT security is a management matter, even when the work is delegated.
  2. Take stock. Which systems, accounts, devices and cloud services exist? Our guide on IT infrastructure analysis shows how a structured inventory works.
  3. Name critical processes. What must run again first after an outage, and how long can you manage without it?
  4. Implement quick wins. The week 1 items close the most common entry points with little effort.
  5. Choose a framework. With the results of steps 2 and 3, you can decide which standard fits.
  6. Review regularly. Security goes stale. Schedule fixed dates for updates, restore tests, training and refreshing your emergency plan and documentation.

IT security checklist for your business: week 1, month 1, quarter 1

The checklist is sorted by impact per effort. Week 1 contains low-cost measures that close common attack paths. Month 1 builds overview and structure, and quarter 1 makes security robust and verifiable.

Week 1: close the most common entry points

  • Enable multi-factor sign-in for email, Microsoft 365 or comparable cloud services, remote access and all admin accounts. Background in password security in the workplace.
  • Separate admin accounts and check whether passwords are stored in plain text anywhere, for example in the Active Directory description field.
  • Disable accounts of former employees and review open shares. The offboarding checklist helps with the comparison.
  • Install critical updates on the firewall, servers, remote access solutions and workstations. Turning this into a routine is covered in updates and patch management.
  • Check your backup: Is it really running, is at least one copy kept separate from the network, and can you restore a file as a test? Details in backup strategy for SMEs.
  • Review remote access and firewall rules: Which services are reachable from the internet, and do you still need them? See managed firewalls for businesses.
  • Verify antivirus on every device: active, up to date, centrally monitored. Criteria in choosing antivirus for businesses.
  • Keep emergency contacts on paper: IT provider, management, insurer, bank. A printed sheet helps when the network is down.

Month 1: build overview and basic structure

Quarter 1: become robust and verifiable

  • Write an emergency plan and walk through it once: who decides, who informs whom, what starts first? Guidance in our IT emergency plan guide.
  • Test restoring entire systems, not just single files, and record how long it takes.
  • Decide on a firewall operating model: in-house, as a managed service or as firewall as a service. With high availability requirements, consider a firewall cluster.
  • Set up monitoring for servers, storage, backups and security alerts. See monitoring IT systems.
  • Make awareness continuous with recurring training and phishing simulations, as described in our piece on the human firewall.
  • Review your website and external services: updates, access, responsibilities. See website maintenance.
  • Choose a framework and set a roadmap: Which framework from this guide fits, and which gaps will you close in the next six months? If NIS2 applies, see implementing NIS2 in mid-sized companies.
  • Write down the rules: short policies on passwords, devices, email and reporting that everyone understands.

Hypothetical example for illustration, not a documented customer case: a tax advisory office with 14 employees works through week 1 over two afternoons. It turns out that a former apprentice still has an active account and the backup has been saving only part of the data for weeks. Both are fixed quickly. Month 1 brings a password manager and training, quarter 1 a written emergency plan with a test restore. Afterwards, management knows where the office stands and can decide whether formal evidence is needed.

Best practices for lasting IT security

  • Fixed dates instead of good intentions. Updates, restore tests, permission reviews and training belong in the calendar, not on a wish list.
  • Least privilege. Every account gets only the rights it needs for its job. When roles change, old rights are removed.
  • Segment the network. Guest Wi-Fi, printers, phones and cameras do not belong in the same segment as servers and accounting.
  • Document. Current documentation of systems, access and dependencies saves hours in an emergency.
  • Build a healthy error culture. Someone who reports a wrong click immediately limits the damage. Someone who fears trouble stays quiet.
  • Include suppliers. Service providers with remote access need their own traceable accounts and clear agreements.

Common IT security mistakes in SMEs

"We're too small to be a target." Automated attacks do not ask about company size. This assumption is the most common reason basic measures never happen.

Buying a product, forgetting operations. A firewall nobody maintains or antivirus whose alerts nobody reads protects only on paper. Security needs ownership and time.

Backups without restore tests. A successful backup job does not prove that data and systems can be recovered in reasonable time. Only a test shows that.

Starting with certification. A 20-person firm aiming straight for ISO 27001 without multi-factor sign-in and working backups is building the roof before the foundation. Basics first, evidence second.

One-off training. A single briefing a year fades fast. Short, recurring formats work better.

Ignoring or overestimating NIS2. Some firms assume without checking that they are out of scope; others launch a major project out of worry. A documented applicability check avoids both.

No plan for emergencies. Without an emergency plan, people improvise under pressure, and improvisation costs time, money and nerves.

Solutions and tools: where WSV can help

You can tackle much of the checklist with your own team. Where time or expertise is short, we support you with clearly defined services. Our IT security services page gives an overview.

  • Status assessment: For a first impression, try our IT security quick check with eight questions. The IT security check goes further: an interview of about 90 minutes with one of our IT security experts, guided by the BSI IT-Grundschutz framework, with a written report and practical recommendations. It does not replace a full IT-Grundschutz audit. Pricing is listed on the product page.
  • NIS2 orientation: Our NIS2 self-check offers initial pointers, not a binding assessment.
  • Network and endpoints: The managed firewall secures your internet connection at a fixed monthly price, including maintenance and security updates. Managed EDR/XDR based on ESET adds behaviour-based detection to your antivirus, with alerts reviewed by our security experts.
  • Access: With Managed Password, your team gets a central password manager with a permission structure and password policies.
  • People: Security awareness and phishing simulation combines hands-on training with controlled test emails and an evaluation that does not single out individual employees.
  • Backup and emergencies: Online backup sends agreed server data, encrypted, to a German data centre every night. Whether you can actually restore from it is verified by the backup check and restore test. The IT emergency plan defines procedures and recovery and is updated every year.

As an IT service provider with 20 employees, we look after more than 1,500 endpoints and more than 300 servers. Many smaller businesses have no IT department of their own, and for them a checklist like this is the realistic starting point. One customer wrote in a Google review (original in German):

„1A Geschäftskundenservice! Bei Problemen erfolgt schnelle Unterstützung. Sehr kompetente und freundliche Beratung. Hier wird nichts auf Biegen und Brechen verkauft, sondern auf die Wünsche und Bedürfnisse auch kleiner Unternehmen wert gelegt.“

– Customer, Google review (February 2020)

You can read more in our Google reviews.

Frequently asked questions

What are the four pillars of IT security?

There is no single, standardised definition of the "four pillars"; different sources mean different things. What is firmly established are the three protection goals of confidentiality, integrity and availability. For SMEs, we structure IT security into four building blocks: technology, access, people, and operations and emergencies. If you cover all four, you have no major blind spots.

Is ISO 27001 mandatory?

ISO/IEC 27001 is a standard and is not automatically mandatory. Certification is, however, often required by customers, in tenders or by sector-specific rules. NIS2 does not prescribe a particular certification either, but it does require entities in scope to implement risk management measures, and an ISMS under ISO 27001 or VdS 10000 can provide a suitable structure for that. Check your contracts and sector rules to find out whether a specific obligation applies to you.

What does the BSI recommend for SMEs?

The BSI offers SMEs several entry points: the cybersecurity brochure for SMEs covering updates, antivirus and backup, the CyberRisikoCheck under DIN SPEC 27076 as a structured status assessment with an IT service provider, and IT-Grundschutz as a comprehensive methodology. For small organisations, the BSI also describes a "path to basic protection" (Weg in die Basis-Absicherung) with checklists that cover fundamental requirements without a full ISMS.

Does my company have to implement NIS2?

That depends mainly on sector and size. In principle, entities in the sectors named in the directive that reach at least medium-sized enterprise thresholds are covered, and in certain cases smaller ones. The BSI's free applicability check gives a first orientation, although its result is not legally binding. Even if you are not directly in scope, customers may pass similar requirements down the supply chain.

Your next step

You do not have to solve everything at once. Work through the week 1 items, build an overview in month 1 and then decide which framework suits your company. If you would like support or a second opinion on where you stand today, talk to us.

Book a free initial consultation

Sources

Updated on

WhatsAppRequest adviceGet support

Get in touch

Privacy settings

We use cookies and other technologies on our website. Some of them are essential, while others help us improve this website and your experience. Personal data may be processed (e.g. IP addresses), for example for personalized ads and content or ad and content measurement.

There is no obligation to consent to the processing of your data in order to use this offer. You can withdraw or adjust your selection at any time under settings. Please note that due to individual settings, not all functions of the website may be available.

We use technically necessary storage for operating this website. Optional services (statistics, marketing, external media) are only loaded after your consent.

Privacy settings