We help raise the cybersecurity posture of organisations with CyberSonar24.

Modern cybersecurity and GRC platform for compliance with NIS2, the Polish National Cybersecurity System Act (KSC), GDPR, DORA, the AI Act and ISO/IEC 27001

CyberSonar24 partners

Gold Partner

Product owner

Silver Partner

01 · Platform modules

Risk, compliance and security in one system

CyberSonar24 is made of modules that share the same registers. An asset entered once is visible in the risk assessment, in an incident, in the business continuity plan and in the record of processing activities. You start with what the Act requires, and you add further areas without moving data.

Platform products

CyberSonar24 GRC modules

  1. 01

    Risk management

    Identification, assessment and monitoring of risks against assets and processes, a risk matrix and periodic reviews.

  2. 02

    Asset inventory

    Systems, devices and information together with the processes that depend on them, and a dependency graph.

  3. 03

    Essential services and business continuity

    Criticality analysis of processes with an acceptable downtime and an acceptable data loss, business continuity and disaster recovery plans aligned with ISO 22301, and a test schedule with reminders.

  4. 04

    Incident register

    Registration, classification and notification of an incident. Personal data breaches in the same module.

  5. 05

    Vulnerability register

    Vulnerabilities from the NVD linked to the asset, criticality assessment and remedial actions.

  6. 06

    Supplier risk

    Assessment and monitoring of suppliers across the supply chain, and tracking of certificates.

  7. 07

    Internal audits and compliance

    An audit programme, recommendations, corrective actions and a management review.

  8. 08

    Remedial plans

    Actions arise from risks, vulnerabilities and statutory requirements. Each has an owner and a deadline, and progress is visible as it happens.

  9. 09

    Document repository

    A central place for policies, procedures, instructions and management-system documentation.

  10. 10

    Cybersecurity training

    An e-learning portal with a test and a certificate, training assigned to roles, and the training level visible to the leadership.

  11. 11

    Access control

    A record of the access-rights matrix and access-control policies.

  12. 12

    Calendar and reminders

    Tracking of all deadlines, audits, tests and reviews.

Integrations. Organisation and supplier data from public registers (GUS), a daily check of the NVD vulnerability database, import of assets and suppliers from Excel files, export to Excel and PDF. In an installation on the organisation’s servers, also Active Directory. (applies to Polish companies only)

Specification

02 · Measurable results of implementation

The Act measures in hours and dates. So does the system.

The Polish act implementing NIS2 (KSC) (Dz.U. 2026 poz. 252) sets obligations and deadlines for essential and important entities in every sector. In CyberSonar24 each of them has its place: a register, a responsible person and a reminder.

Significant incident

  1. 24 h

    Early warning

    The first information about a significant incident. The incident is recorded in one module, and the system prompts a notification to the CSIRT team when it concerns an essential service.

  2. 72 h

    Incident notification

    The notification template and the incident’s links to assets, processes, risks and suppliers are at hand. An important entity that is a public entity submits only the notification within 72 hours (art. 12c).

  3. 1 month

    Final report

    The deadline for the final report on handling a significant incident under the Polish act implementing NIS2 (KSC).

Statutory deadlines

  1. 3.10.2026

    Entry in the NIS2 Register

    The deadline to apply for entry for entities that met the criteria on 3.04.2026. Later: 6 months from meeting the criteria. Public entities are entered ex officio.

  2. 3.04.2027

    Security management system

    Registers of assets, risks and suppliers and business continuity plans with documentation in one repository, with versions and a change history.

  3. 3.04.2028

    First audit

    Essential entities: the first security audit (art. 33 para. 2 of the amending Act), then at least once every 3 years. An audit programme, ISO 27001 checklists and corrective actions from nonconformities.

10

Security-measure areas

Each of the ten risk-management areas from Article 21 of the NIS2 Directive, transposed into the Polish act implementing NIS2 (KSC), assigned to a system module.

Deadlines tracked by the system

  • 30 days

    before a supplier contract expires and before a scheduled audit: a reminder for the owner

  • 14 days

    before a business continuity plan test and before a management review: a reminder

  • 7 days

    before a remedial-action deadline: a reminder

  • 1 year

    the longest interval between policy reviews in the document repository

03 · Close-ups

Incidents, audits and assets in the application

Incidents and risk events

Registration, classification and notification of an incident

Registration, classification and handling of incidents. Personal data breaches sit in the same module.

Report to a supervisory authority in CyberSonar24: choosing the authority (CERT Polska or UODO) and the notification stage, here the early warning (24 h)
Fig. 2Report to a supervisory authority: choosing the authority and the notification stage, here the early warning (24 h) (demonstration data).Interface shown in Polish

Internal audits and compliance

Audit recommendations with implementation status

An audit programme, control paths, recommendations and corrective actions, and compliance reports for NIS2 and the Polish act implementing NIS2 (KSC). The management review documents the accountability of the leadership.

Audit recommendations in CyberSonar24: observations and nonconformities with implementation status
Fig. 3Audit recommendations: observations and nonconformities with implementation status (demonstration data).Interface shown in Polish

Asset inventory and classification

Systems, devices and information together with processes

A record of systems, devices and information together with the processes that depend on them. The dependency graph shows how a failure of one element affects essential services.

Organisation risk map in CyberSonar24: essential services, processes, IT assets and risk cards
Fig. 4Organisation risk map: essential services, processes, IT assets and risk cards (demonstration data).Interface shown in Polish

04 · Who it is for

For essential and important entities

The Polish act implementing NIS2 (KSC) (Dz.U. 2026 poz. 252) covers essential and important entities from the sectors listed in two annexes, as well as public entities. The obligations are shared: a security management system with documentation, handling and reporting of incidents, and supplier-risk management. CyberSonar24 runs them in one system, regardless of sector.

Questions and answers

Who is subject to the Polish act implementing NIS2 (KSC)?

The Act applies to essential and important entities, that is organisations operating in the sectors listed in Annexes 1 and 2 to the Act (Dz.U. 2026 poz. 252) that meet its criteria, above all the size criterion. Public entities are among them.

The final classification should be confirmed with a lawyer. A first step can be the free Audit Zero: the questionnaire does not require an account, and a PDF report is sent to the email address you provide.

What is the difference between an essential entity and an important entity?

The category is decided above all by the sector and the size of the organisation. For planning the work, the most important difference concerns the audit. An essential entity carries out its first security audit of the information system by 3 April 2028 (art. 33 para. 2 of the amending Act), and subsequent audits at least once every 3 years (art. 15 para. 1). An important entity carries out an audit only when the authority orders one by decision (art. 15 para. 1b).

Both categories must have a security management system with documentation by 3 April 2027, and both report significant incidents within 24 hours, 72 hours and one month. An important entity that is a public entity submits only the notification within 72 hours (art. 12c). The name of the annex (“essential sectors”, “important sectors”) describes the sector, not automatically the category of the entity.

Essential sectors · Annex 1

Important sectors · Annex 2

The name of the annex describes the sector. Whether an organisation is an essential or an important entity is decided above all by the type of activity and its size. A first picture is given by the free Audit Zero.

05 · Obligations under the Polish act implementing NIS2 (KSC)

Every obligation has its place in the system

The risk-management measure areas from Article 21 of NIS2, transposed into the Polish act implementing NIS2 (KSC), and the modules in which you carry them out in CyberSonar24.

NIS2 Article 21 risk-management measures and CyberSonar24 modules
PointAreaCyberSonar24 modules
a)Risk analysis and security policiesRisk analysis, Document repository
b)Incident handlingIncidents, Actions
c)Business continuity and crisis managementBusiness continuity plan, Impact analysis
d)Supply-chain securitySuppliers
e)Acquisition and maintenance of systems, vulnerabilitiesVulnerabilities, Organisation assets
f)Effectiveness of measuresAudits, Recommendations, Management review
g)Cyber hygiene and trainingTraining
h)Cryptography and encryptionDocument repository (policies)
i)Human resources and access controlAccess-rights matrix
j)Multi-factor authenticationAccess-rights matrix

06 · How it works

From registers to evidence for the auditor

The platform takes you through the obligations of the Act in the order in which a security management system is built. Each step uses data from the previous one.

How the platform works

  1. 01

    Registers

    Essential services, processes, assets and suppliers go into one system, including from Excel files. The dependency graph shows what a failure of one element will stop.

  2. 02

    Risk

    A risk assessment is built on the registers. Each risk has an owner, a treatment plan, a deadline and a review date.

  3. 03

    Day-to-day work

    You run incidents, remedial actions, training, access reviews and continuity-plan tests in one place. The system reminds you of deadlines.

  4. 04

    Evidence and reports

    The management review, reports for the leadership and documentation for the auditor are produced from the data in the system, with a change history.

How implementation works

  1. 01

    Free Audit Zero

    A questionnaire with no account, a PDF report to the email address. It shows where to start.

  2. 02

    Presentation and scope

    We show the system on sample data. We agree the modules, the number of units and the installation model: a cloud in the European Union or your servers.

  3. 03

    Registers

    Essential services, processes, assets and suppliers go into the system, including from Excel files. A risk assessment and a treatment plan are built on that basis.

  4. 04

    Day-to-day work

    You run incidents, remedial actions, training and audits in one place. The leadership receives a management review, and evidence for the auditor is produced as you go.

Implementation process

07 · CyberSonar24 AI

Artificial-intelligence support

Help with preparing documentation.

Book a presentation

We will show the system on data close to your organisation.

A free presentation with no obligation, in a dedicated and encrypted environment.

Contact details

Presentation request form

* required fields

The controller of the data submitted in this form is BLUE Energy sp. z o.o., ul. Towarowa 35, 61-896 Poznań, Poland, KRS 0000361608, NIP 7781473428. We process the data solely to respond to the enquiry and to contact you about a presentation. Details, including your rights, are set out in the privacy policy.