In this guide
You may have heard that NIS2 is coming, or already here, and wondered whether a small company has to worry. The honest answer is that it depends on your sector and customers, and that even if the law does not apply to you directly, your customers might ask you about it. This guide explains the idea in plain English and focuses on what a small supplier can do on the engineering side.
General information, not legal advice. Rules change and apply differently to each business, so confirm your own position with a solicitor, your accountant or the relevant authority.
What NIS2 is
NIS2 is the revised EU directive on the security of network and information systems. It sets cyber security risk-management and incident-reporting expectations for organisations in a defined list of sectors, and it covers security in the supply chain. Each member state turns it into national law. Whether and when a given organisation is in scope depends on the national law and on its size and sector.
Where Ireland stands
Ireland's route is the National Cyber Security Bill, which would also put the National Cyber Security Centre on a statutory footing. In the sources we checked, the general scheme had been published in 2024 and the bill was still progressing, with the EU's October 2024 transposition date missed. We did not find confirmation of enactment, so check the Oireachtas website and the NCSC pages for the current position instead of relying on this article.
Why smaller suppliers hear about it
Organisations in scope must think about the security of the suppliers they depend on. In practice that often means a questionnaire landing in your inbox, a clause in a new contract or a request for evidence of how you handle access, patching and incidents. A small software or services business may well be asked even if it is not regulated itself.
Engineering habits that answer most questions
- Access control: multi-factor sign-in, least-privilege roles and prompt removal of leavers.
- Patching: a routine for updating operating systems, frameworks and dependencies.
- Backups: regular, tested restores kept apart from the main system.
- Logging: enough audit trail to see who did what and when.
- Secure development: code review, dependency checks and separate test and live environments.
- Incident plan: a short written plan saying who decides, who is told and how fast.
- Supplier list: know which services your own product depends on.
What to ask a developer you commission
- How are secrets and credentials stored and rotated?
- How are dependencies updated and checked for known vulnerabilities?
- Who has access to production, and is it logged?
- How are backups taken and when was a restore last tested?
- What happens, and who is told, if something goes wrong?
What we will not claim
Zenocta can build software with these practices and can help you document how your product behaves, which makes answering a customer questionnaire easier. We do not issue certifications, and we do not say a product is NIS2 compliant, because that depends on your organisation as a whole. Our security page describes our own approach.
A sensible first step
Write a one-page summary of how you handle access, patching, backups and incidents. Even a rough version helps you answer customers faster and shows you where the gaps are. If part of that involves software you are about to commission, raise it during scoping through contact.
Try it live
Open the real thing: demos run in a new tab with sample data, apps link to their own page.
- CServiceCybersecurity supportPractical security help for the software and systems you run.
- CServiceCloud and DevOpsHosting, deployment and monitoring set up with care.
- SBrowse allSecurity at ZenoctaHow Zenocta approaches security in what it builds.
- ABrowse allAll Zenocta servicesCustom software, apps, websites, AI automation, ERP and CRM from one team.
- TBrowse allTalk about your projectSend a few lines about what you need and get a scoped proposal.
Frequently asked questions
01Does NIS2 apply to my small business?
It depends on your sector, size and the national law that implements it. Even if it does not apply directly, a larger customer in scope may ask you about your security. Check with your adviser or the national authority.
02Can Zenocta make us NIS2 compliant?
No. Compliance is an organisational matter and Zenocta does not certify it. We can build and operate software using sound security practices and help document how it works.
03Has Ireland passed its NIS2 law?
In the sources we checked, the National Cyber Security Bill had not been confirmed as enacted. Check the Oireachtas website and the NCSC for the current position.



