Directive (EU) 2022/2555

NIS2 in Poland: what it requires, and how EventSentry helps you meet it

NIS2 is being transposed into Polish law through amendments to the Act on the National Cybersecurity System (Ustawa o Krajowym Systemie Cyberbezpieczeństwa, KSC/UKSC). This page maps the directive's core obligations to concrete EventSentry capabilities - so your compliance work produces working security, not just paperwork.

Scope

Who is affected

NIS2 significantly widens the scope of EU cybersecurity regulation compared to the original NIS Directive, classifying organizations as essential or important entities across roughly 18 sectors - regardless of company size thresholds in several high‑risk categories.

Essential entities

Energy, transport, banking, financial market infrastructure, health, drinking water, wastewater, digital infrastructure, public administration, space.

Important entities

Postal & courier services, waste management, chemicals, food production, manufacturing, digital providers, research organizations.

Supply chain

Obligations extend to ICT service providers and key suppliers - many SMEs are pulled in as subcontractors to regulated entities.

Public sector

Central and local government bodies providing services that, if disrupted, would have a significant impact on public safety.

Timeline & consequences

Reporting deadlines and liability

Within 24 hours - early warning

Notify the competent CSIRT of a significant incident, including whether it is suspected to be caused by unlawful or malicious action.

Within 72 hours - incident notification

Provide an initial assessment of severity, impact and indicators of compromise, updating the earlier warning.

Within 1 month - final report

Submit a detailed account: root cause, mitigation measures taken, and cross‑border impact where relevant.

Entity typeMaximum fine
Essential€10,000,000 or 2% of global annual turnover, whichever is higher
Important€7,000,000 or 1.4% of global annual turnover, whichever is higher

Management bodies must approve risk‑management measures, oversee their implementation, and can face personal liability and training obligations. Exact figures and procedures are finalized in Poland's national KSC/UKSC implementing act - confirm current thresholds with legal counsel.

Article 21 · Risk-management measures

Mapping NIS2 requirements to EventSentry features

Article 21 lists the minimum cybersecurity risk‑management measures every in‑scope entity must implement. Below is how EventSentry's built‑in packages support each one.

NIS2 Art. 21 measureWhat's requiredEventSentry capability
Risk analysis & information system security policies Continuous visibility into systems to inform risk decisions. Real‑time event log monitoring across Windows, Syslog and applications with 68 built‑in packages.
Incident handling Detect, triage and respond within reporting deadlines. Correlation, filter‑rule alerting and automated remediation to shrink detection‑to‑response time.
Business continuity & crisis management Maintain availability and recover from disruption. Performance, disk and uptime monitoring with proactive alerting before failures cascade.
Supply chain security Oversight of vendor and third‑party risk. Asset inventory, software version checks (305 checks) and change auditing across the environment.
Vulnerability handling & disclosure Identify and remediate weaknesses systematically. 293 validation security controls plus compliance‑readiness dashboards.
Basic cyber hygiene & training Reduce exposure from common, preventable issues. Process monitoring, privilege‑escalation detection and tamper validation flag risky behavior early.
Cryptography & encryption Protect data in transit and at rest where applicable. Monitoring of configuration and policy changes affecting cryptographic controls.
Access control & asset management Know what you have, and who can touch it. Active Directory auditing: object/group changes, account lockouts, Group Policy auditing, compromised‑credential detection.
Network & information systems security Visibility into network traffic and anomalies. NetFlow/IPFIX/sFlow analytics, ARP spoof detection, geo‑located threat intelligence.
Multi-factor authentication & secure communications Strengthen authentication where justified by risk. Logon monitoring and suspicious‑authentication alerting feed MFA policy enforcement and review.
Evidence, not scramble

Audit‑ready reporting, built in

EventSentry's pre‑built compliance dashboards and RESTful reporting API turn day‑to‑day monitoring into the documentation CSIRTs, auditors and your own board will ask for - generated continuously, not assembled the week before an audit.

Not sure where your gaps are?

Omnus.pl offers a short NIS2 / KSC readiness conversation and a guided EventSentry proof‑of‑concept on your own infrastructure.

Talk to Omnus.pl