All products

CyberSonar24 GRCAvailable

Information security management in a large organisation, ready for an NIS2 audit

CyberSonar24 GRC joins risks, assets, processes, suppliers, incidents, audits and security documentation in one system. The leadership sees the current state of the organisation. Every risk and every action has an owner and a deadline. Evidence for the auditor is produced as you go, not just before an inspection.

Interface shown in Polish

01

Deadlines set by the Polish act implementing NIS2 (KSC)

The amended Polish act implementing NIS2 (KSC) (Dz.U. 2026 poz. 252) imposes concrete obligations with concrete dates on essential and important entities.

  • By 3 April 2027 an information security management system together with documentation.
  • By 3 April 2028 the first security audit of the information system in an essential entity (art. 33 para. 2 of the amending Act), and subsequent audits at least once every 3 years (art. 15 para. 1).
  • A significant incident: an early warning within 24 hours, a notification within 72 hours, a final report within one month.

CyberSonar24 GRC runs these obligations in linked registers. You do not have to reconstruct them from spreadsheets and correspondence.

01 / 05

One picture of risk for the whole organisation

The risk register contains an assessment of likelihood and impact, a treatment plan, an owner and a deadline. Threats are assigned to processes and assets according to the control catalogue in Annex A of ISO 27001. The risk map shows what to address first. From unacceptable risks the system creates actions to be carried out. Risk reviews take place according to a schedule, and the register can be exported to Excel or PDF.

How to carry out a risk analysis step by step

Interface shown in Polish

02 / 05

Essential services, processes and assets linked to one another

The essential-service register is the starting point. Processes are assigned to services, and assets to processes: systems, devices, information and people. A process criticality analysis determines the acceptable downtime and the acceptable data loss. Each asset has a confidentiality, integrity and availability assessment and a business and technical owner.

The dependency graph shows how a failure of one element affects services. Link verification points out gaps, for example a process without assets or an asset without an owner. Existing asset lists can be imported from Excel.

Interface shown in Polish

03 / 05

Incidents reported within 24 and 72 hours

Incident handling follows set steps: report, response, repair and analysis. The system prompts a notification to the CSIRT team when a critical incident concerns an essential service. Report templates organise the information required at successive stages. The incident is linked to assets, processes, risks, vulnerabilities and suppliers. Personal data breaches are recorded in the same module, shared with CyberSonar24 GDPR.

CyberSonar24 GDPR

Interface shown in Polish

04 / 05

Business continuity

Business continuity and disaster recovery plans are built on the criticality analysis. The plan contains a crisis team, recovery procedures and an escalation path. Templates are aligned with ISO 22301. The system keeps a test schedule by criticality, records the results and reminds you of deadlines.

Interface shown in Polish

05 / 05

Audits, management review and compliance evidence

The audit programme covers internal and external audits under ISO 27001 and ISO 22301 and NIS2, GDPR and supplier audits. Checklists cover all requirements of Annex A of ISO 27001:2022. Corrective actions with an owner and a deadline arise from nonconformities. A gap analysis shows implementation progress, and the system generates a statement of applicability. The management review gathers data on risks, incidents and compliance in one place and documents the leadership’s decisions.

Interface shown in Polish

Suppliers and the supply chain

The supplier register retrieves data from GUS by NIP number. It stores contracts, non-disclosure agreements, service-level agreements and certificates with validity dates. 30 days before a contract expires the system sends a reminder. Critical suppliers are marked automatically. A supplier risk assessment covers six areas and has a schedule of reassessments. Supplier results can be compared in a table and on a risk map. (applies to Polish companies only)

Supplier risk management in 2026

Vulnerabilities

The vulnerability register links each gap to the asset and its owner. The system checks the NVD vulnerability database every day for technologies entered in assets. Vulnerabilities have a criticality assessment and a priority. Scanner results can be imported from CSV or XML files.

Vulnerability management and GRC

Roles, accountability and change history

The organisation structure reflects departments, posts and responsible persons. The board, the person responsible for security and risk owners have separate dashboards. Each sees their tasks, deadlines and notifications. Tasks can be delegated and commented on. Depending on the plan (local or central) one instance can serve several companies or units.

The document repository has versioning, read and edit access control and a full change history. The change history also covers roles and access rights to assets. Incidents have a record of successive handling stages.

Two implementation models and where data is stored

The same system and the same modules are available in two models. The place of installation and the scope of support differ.

  • Cloud service. A dedicated instance in the European Union. Each organisation has a separate environment. Connections are encrypted. For personal data we conclude a data processing agreement.
  • Installation on your organisation’s servers. The system runs in your infrastructure, with no user limit for an installation on the client’s servers. The dedicated plan also includes import of the organisational structure, Active Directory integration, priority support with a service-level agreement, and dedicated training and implementation support.

In both models the data can be exported.

02

Implementation

  1. 01

    Presentation

    We show the system on sample data and discuss the needs of your organisation.

  2. 02

    Configuration

    We start the needed modules and enter the organisation structure.

  3. 03

    Data transfer

    Together we move the existing risk spreadsheets, asset lists and suppliers.

  4. 04

    Day-to-day work

    Responsible persons carry out tasks, and the leadership uses the dashboard and reports.

Modules are started separately. You can start with the risk register and expand the scope gradually.

criteria for choosing a platform before purchase

03

What the system does and what it does not do

The system organises the documentation and actions required by the law and shows their status. It does not replace leadership decisions or a legal assessment. Compliance is decided by the measures implemented and the organisation’s decisions. CyberSonar24 GRC helps you run and document them.

04

List of functions

  • A risk register with a risk map, a treatment plan, an owner and a deadline
  • A register of essential services, processes and assets with a dependency graph
  • A process criticality analysis and verification of the completeness of links
  • An incident register with a handling path and report templates
  • Personal data breaches in the shared incident module
  • A supplier register with data from GUS and a supplier risk assessment (applies to Polish companies only)
  • A vulnerability register with a daily NVD check
  • Business continuity and recovery plans with a test schedule
  • An audit programme, ISO 27001:2022 checklists and corrective actions
  • A gap analysis, a statement of applicability and a management review
  • A repository of policies and procedures with versioning and a change history
  • A review of access rights to assets
  • Dashboards for the board, the person responsible for security and owners
  • Tasks, a calendar and deadline reminders
  • Reports for the leadership and for inspections, export to Excel and PDF
  • A training record and a link to CyberSonar24 E-learning
  • Two implementation models: a dedicated instance in the EU or an installation on the client’s servers

CyberSonar24 E-learning

05

Who it is for

  • Essential and important entities within the meaning of the Polish act implementing NIS2 (KSC)
  • Hospitals and healthcare entities
  • Water and wastewater utilities
  • Public institutions
  • Officers and information-security departments
  • Internal auditors and compliance teams
  • Boards and directorates accountable for cybersecurity oversight

06

Frequently asked questions

Does the system ensure compliance with the Polish act implementing NIS2 (KSC)?

The system organises the documentation and actions required by the law and shows their status. Compliance is decided by the measures implemented and the organisation’s decisions.

Can we start with one module?

Yes. Modules are started separately, so you can start for example with the risk register.

Where is the data stored?

In the cloud service on a dedicated instance in the European Union. In an installation on the client’s servers the data stays in your organisation’s infrastructure.

Will one instance serve several companies or units?

Depending on the plan (local or central) one instance can serve several companies or units.

Does the system work with the GDPR module?

Yes. GRC and GDPR run in one application. Incidents and assets are shared by both areas.

Let us see how the system will work in your organisation

During the presentation we will show the registers on sample data and discuss the implementation scope and the transfer of the current documentation.

Interface shown in Polish