NIS2 and the National Cybersecurity System.
The NIS2 directive and the Polish Cybersecurity Act require essential and important entities to register with the competent authority, report incidents on a 24h/72h/30-day timeline, and maintain technical measures under Art. 21 NIS2. RealSec makes this operational, not just declarative.
Classification: essential or important?
Classification by sector (energy, transport, banking, health...), size, and supply chain role. The profile determines reporting obligations. Auto-update when the NACE code or company size changes.
- SECTORAnnexes I and II of NIS2
- SIZEEmployees + turnover / balance sheet total
- AUTORe-classification on NACE changes
Reporting timeline to CSIRT GOV.PL.
Early warning at 24h, formal notification at 72h, final report at 30 days. Each threshold has its own template, escalation path and alert. Export to CSIRT in their system format.
- 24HEarly warning ; minimum scope
- 72HFormal notification ; impact assessment
- 30DFinal report with lessons learned
Mapping controls to the 10 areas required by NIS2.
Risk management, incident handling, business continuity, supply chain, secure development, encryption, MFA, access management, asset management, cybersecurity training. Each area mapped to specific controls in the ISMS.
- AREAS10 areas of Art. 21 NIS2
- CONTROLSMapping to ISO 27001 + custom
- EVIDENCELinks to policies and procedures
Vendors with access to NIS2-covered systems.
Every ICT vendor with access to a critical system requires a security assessment. Cross-linked with the DORA module. Vendor risk assessment with a questionnaire tailored to NIS2 Art. 21(2)(d).
- CROSSShared vendor register with DORA
- ASSESSVendor security questionnaire
- AUDITRight-to-audit captured in contract
Najczęstsze pytania
NIS2 without the panic.
Demo on real data: incident timeline, CSIRT export, vendor risk assessment.