Risk assessment
A written view of what you depend on, what could go wrong and what you do about it. Review it at least yearly.
Home / Security monitoring / NIS2 readiness for small business
You may have heard that NIS2 applies to everyone. It does not. It covers listed sectors, mostly medium-sized and larger organisations, and each EU country writes its own rules. Small businesses can still be pulled in through customers. Here is how to check scope, what readiness means and what evidence to keep.
NIS2 is the EU directive on the security of network and information systems (Directive 2022/2555). It replaces the first NIS directive and widens the list of sectors it covers.
It splits organisations into essential and important entities. Sectors include energy, transport, health, digital infrastructure, ICT service providers, manufacturing of some products, food, waste, postal services and public administration. As a general rule, medium-sized and larger organisations in those sectors are in scope. A few kinds of small provider can be in scope regardless of size, and member states may add others.
That is the honest answer: it depends on your sector, your size and your country. Nobody can tell you from a website. Ask your lawyer or national authority to confirm.
NIS2 is a directive, so each member state writes its own law. The deadline to do so was October 2024, and countries have moved at different speeds. Thresholds, penalties, registration steps and the responsible authority can differ.
Before you spend money, look up your national cybersecurity authority and read what it says about scope and registration. Treat anything from a vendor, including us, as a starting point.
The directive asks in-scope organisations to manage the security of their supply chain. In practice that means their contracts and questionnaires reach down to suppliers.
If your customers are hospitals, energy firms, logistics companies or software providers, expect questions about patching, access control and incident handling. Being ready to answer them with evidence is a sales advantage even where the law does not bind you directly.
A written view of what you depend on, what could go wrong and what you do about it. Review it at least yearly.
A plan for who handles an incident, who you tell, and how you meet reporting deadlines. Part of this is your breach response plan.
You find known flaws in what you run and fix them in a sensible order. Patch management needs dates and owners.
Multi-factor authentication for admin and remote access, and clean joiner and leaver routines.
Backups that restore, and a plan for running without a key system for a few days.
A list of the suppliers that can hurt you, and what you asked of them.
NIS2 makes management bodies accountable for approving and overseeing these measures. Someone senior must own this.
Dated records that show each of the above was done. This is the part most small businesses lack.
For in-scope entities the directive sets a staged process for significant incidents: an early warning within 24 hours, a fuller notification within 72 hours, and a final report after roughly one month. Your national law defines what counts as significant and who receives the report.
You cannot meet a 24-hour deadline if you find out about an exposure weeks later. Continuous monitoring shortens the time between something going wrong and someone knowing.
DORA, the Digital Operational Resilience Act, applies to financial entities and the ICT providers they depend on. The Cyber Resilience Act concerns products with digital elements and has phased application dates. NIS2 sits alongside both. If you sell software to banks or build connected products, more than one may apply. Ask your lawyer which.
We give you the technical evidence: continuous monitoring of your internet-facing systems, findings triaged by a person, a patch and exposure history, and a readiness view against the measures above. See security monitoring and compliance for what is included.
There is no NIS2 certificate, and we do not offer one. We do not decide your scope and we do not promise compliance. This page is general information, not legal advice. Questions about whether a rule applies to you belong with your lawyer or your national authority.
The technical groundwork overlaps with GDPR Article 32 measures, so one set of evidence serves both.
Often not directly. NIS2 mainly covers medium-sized and larger organisations in listed sectors, with some exceptions for small ones. Member states decide the details, so check your national authority. You can still be affected as a supplier to a business that is in scope.
It means you can show the risk-management measures the directive expects: a risk assessment, incident handling, patching, access control, supplier checks and management oversight. Readiness is about evidence you can produce, not a certificate.
The directive sets an early warning within 24 hours of becoming aware of a significant incident, an incident notification within 72 hours and a final report after about a month. Your national rules say who you report to and in what form.
Each EU member state designates its own competent authority. Transposition and enforcement differ from country to country, so look up the authority in the country where you operate.