NIS2
NIS2 network monitoring for mid-sized companies
NIS2 network monitoring means watching how the hosts on your network communicate, so that a significant incident is detected early enough to report it on time and the evidence for the report already exists. NIS2 does not name a specific tool, but it requires incident handling as a risk-management measure (Article 21) and a fixed reporting timeline (Article 23).
The fact to plan around
Directive (EU) 2022/2555 (NIS2), Article 23(4): an early warning within 24 hours of becoming aware of a significant incident, an incident notification within 72 hours, and a final report no later than one month after the notification. Member States had to apply their national rules from 18 October 2024 (Article 41).
Source: Directive (EU) 2022/2555 (NIS2), Articles 21, 23 and 41 — EUR-Lex
What NetSenX does today
- Detects command-and-control beaconing, scanning and lateral movement, and unusual outbound data volume from network behaviour, so a new malware variant without a signature still leaves a trail.
- Tracks each incident against the NIS2 Article 23 deadlines (24 hours, 72 hours, one month) and prepares a GDPR Article 33 breach notification for your DPO. PDF reports from the Starter plan.
- Explains every alert in plain language, on every plan, and writes alerts, analyst decisions and configuration changes to an audit log you can hand to your auditor.
- From the Pro plan, reads Modbus/TCP, DNP3, BACnet/IP, EtherNet/IP and S7comm from passive capture, for manufacturing, energy and utility sites; OT devices are never actively probed.
What NetSenX does not do
NetSenX does not decide whether your organisation is in scope of NIS2, does not register it with your authority and does not submit reports to your CSIRT on your behalf: those duties stay with your organisation, and no tool fulfils them on its own. NetSenX is not an EDR, a SIEM or a managed detection service (MDR), and it does not replace them.
Questions buyers ask
Does NIS2 require network monitoring?
NIS2 does not name network monitoring or NDR, but Article 21 lists incident handling among the required risk-management measures, and Article 23 requires significant incidents to be reported on a fixed timeline. You cannot report an incident you have not detected, so continuous network monitoring is one practical way to meet both.
What are the NIS2 incident reporting deadlines?
Under Article 23(4): an early warning within 24 hours of becoming aware of a significant incident, an incident notification within 72 hours, an intermediate report if the authority asks for one, and a final report no later than one month after the notification. National laws transposing NIS2 can add detail, so check your own country's rules.
Does NIS2 apply to mid-sized companies?
In general, NIS2 applies to entities in the sectors of its Annexes I and II that are at least medium-sized under Recommendation 2003/361/EC (50 or more employees, or an annual turnover and a balance sheet total both above EUR 10 million) and to some entities regardless of size. Your national authority or legal counsel can confirm whether your organisation is in scope.
Does NetSenX submit the NIS2 report for us?
No. NetSenX tracks the Article 23 deadlines for each incident, keeps the alerts and the audit log the report draws on, and prepares a GDPR Article 33 breach notification for your DPO; your organisation submits the reports to its CSIRT or competent authority.
Sources
- Directive (EU) 2022/2555 (NIS2), Articles 21, 23 and 41 — EUR-Lex
- Commission Recommendation 2003/361/EC (definition of micro, small and medium-sized enterprises) — EUR-Lex
- European Commission — NIS2 transposition status by Member State
This page is general information, not legal advice. Check your obligations with your national authority or legal counsel.
Related pages
Try NetSenX on your own network
Start on the Free plan with up to 3 devices, or book a 20-minute demo.