Security
NIS2 for mid-sized companies: what your software must meet before an inspection
Tomáš DerzsiFounder and Managing Director
- Published
- Updated
- Reading time
- 2 min read
Article contents
NIS2 has widened the circle of obliged entities to thousands of Slovak companies, including food production, logistics, waste management and engineering, usually from 50 employees. Fines can reach €10 million or 2% of worldwide turnover for essential entities, and €7 million or 1.4% for important ones. And inspectors ask about your software too.
What the law expects from software
- Access management: every user has their own account, role-based permissions and a record of who changed what.
- Multi-factor sign-in, at least for administrators.
- Encryption of data in transit and at rest.
- Backups with tested recovery. Not “we back up” but “we have tested the restore and know how long it takes”.
- Reporting serious incidents within 24 hours, which you can’t do without monitoring.
Where companies most often fall short
On old internal systems: a shared password like “warehouse123”, no change logs, an unencrypted database on a server under the stairs. Paradoxically, NIS2 changes often partly pay for themselves, because the same changes the law requires also reduce outages and errors. If the system is too old to change, consider modernising it piece by piece.
Who is responsible — and why it’s the managing director
NIS2 shifts responsibility to the statutory bodies. Management is liable for non-compliance, not “the IT guy”. The managing director must approve the measures, demonstrate training and know where the company stands. Ignorance is no defence. That’s why cybersecurity is moving from the IT budget onto the management agenda. An inspection isn’t looking for perfection but for proof that management is in control and has a plan.
A timeline not to underestimate
Changing software isn’t a week’s work. Introducing roles, logs, multi-factor sign-in and tested recovery takes months if it’s done properly. Companies that wait for the first inspection end up doing everything at once, under pressure and at a high price. Those who start today spread both the cost and the risk, and have their documentation ready before anyone asks for it.
A sensible approach: compare your current software with the requirements, rank the gaps by risk and prepare a remediation plan with deadlines. Inspectors ask for documentation. Have it ready before they knock.

About the author
Tomáš Derzsi
Founder and Managing Director · Smooth Operator s. r. o.
We work in English and Slovak.
About the company