All sectors

Cybersecurity in banking and financial markets: KSC, NIS2 and DORA

In Annex 1 to the Polish act implementing NIS2 (KSC), the banking and financial-market infrastructure sector covers among others domestic banks, branches of foreign banks, cooperative savings and credit unions (SKOK), operators of a regulated market, ASO and OTF, and administrators of critical benchmarks. For these entities, ICT risk management and the reporting of major incidents are governed primarily by Regulation 2022/2554 (DORA).

A bank and a market infrastructure entity are covered by the KSC Act, which implements the NIS2 Directive, but their main digital resilience requirements come from DORA. In practice this means two regimes, one common register of entities and a large number of ICT service providers to describe. CyberSonar24 combines the register of assets, risks, suppliers and incidents with the DORA module in one system.

01

NIS2 and DORA for banks in Poland: what sets the sector apart

  • DORA and NIS2. For financial entities, DORA is a sector-specific Union legal act within the meaning of Article 4 of the NIS2 Directive (Article 1(2) of DORA). For this reason the KSC Act excludes, for this sector, its provisions on the information security management system and on reporting significant incidents, with the exceptions listed in art. 8i. The requirements in these areas come from DORA.
  • Intensive supervision. The competent authority within the meaning of DORA is the Polish Financial Supervision Authority (KNF) (art. 2 point 14a of the KSC Act). Documentation must be ready for inspection at any time, not only before an audit.
  • An extensive chain of ICT providers. Transaction systems, payments, electronic banking, data centres and cloud services usually come from many providers, and some of them support critical functions.
  • Services available around the clock. Customers use payments and electronic banking without interruption, so any unavailability is visible immediately.
  • Different scale of entities. The same sector includes large banks and small cooperative credit unions, which have smaller teams but a similar scope of documentation.

02

Typical threats and incidents

  • Takeover of customer accounts after phishing for login credentials.
  • Denial-of-service attacks on electronic banking and transaction services.
  • An incident at an external ICT provider that stops a critical function.
  • Ransomware encrypting data in internal systems.
  • Abuse of privileges by persons with privileged access.

03

Obligations under the KSC Act

  • Who is covered. The entities listed in Annex 1 in the banking and financial-market infrastructure sector.
  • Category. An entity that exceeds the thresholds of a medium-sized enterprise is an essential entity (art. 5 para. 1 point 1), and a medium-sized enterprise is an important entity (art. 5 para. 2 point 1).
  • Exclusion under art. 8i. The provisions of the Act on the information security management system and on reporting significant incidents do not apply to essential and important entities in this sector, except for the provisions listed in art. 8i para. 1. The exceptions include the provisions on the register of entities (art. 7 to 7m) and on contact persons (art. 9). The provisions on the responsibility and training of the head of the entity apply accordingly (art. 8c to 8f, art. 8i para. 2).
  • Entry in the register. The application for entry is submitted within 6 months of meeting the conditions (art. 7c para. 1), and a change of data is reported within 14 days (art. 7c para. 3).
  • DORA. Regulation 2022/2554 covers among others ICT risk management, the reporting of major ICT-related incidents, digital operational resilience testing and the management of ICT third-party risk. The scope of obligations of a specific entity should be confirmed with the legal or compliance department.

04

How CyberSonar24 helps

DORA module.

Ready-made templates of DORA requirements, a gap analysis showing implementation progress and mapping of safeguards to requirements. The same system supports NIS2 and KSC templates, ISO/IEC 27001 and the GDPR.

Critical functions and ICT assets (CyberSonar24 GRC).

A register of services and processes with assigned ICT assets and a dependency graph showing which services stop when a system or provider fails. The criticality analysis sets the maximum tolerable downtime and the maximum tolerable data loss for each process.

CyberSonar24 GRC

ICT service providers.

A supplier register with data from GUS by NIP number, contracts, non-disclosure agreements, service level agreements and certificates with expiry dates. Critical suppliers are flagged automatically, the supplier risk assessment covers six areas, and the results can be compared in a table and on a risk map.

ICT risk.

A risk register on a scale from 1 to 25 (1–4 Negligible, 5–9 Low, 10–14 Medium, 15–19 High, 20–25 Critical), with a treatment plan, owner, deadline and review schedule. Export to Excel and PDF.

Incidents and personal data breaches.

An incident register with the handling workflow and report templates, linked to assets, risks, vulnerabilities and suppliers. Personal data breaches are in the same module, shared with CyberSonar24 GDPR.

Evidence for supervisors.

An audit programme with ISO 27001:2022 checklists, corrective actions with an owner and deadline, a repository of policies and procedures with versioning, and a management review documenting the board’s decisions.

Book a presentation of the DORA module

05

Typical rollout

  1. 01

    Presentation. We show the DORA module, the supplier register and the dependency graph on sample data.

  2. 02

    Scope and deployment model. We agree the modules, the entities in the group and the deployment model, in the cloud or on the client’s servers (on-prem). Login can use LDAP, Kerberos or SSO.

  3. 03

    Data migration. Together we transfer existing risk spreadsheets and lists of assets and suppliers.

  4. 04

    Gap analysis. The compliance team assesses the status of DORA requirements and assigns owners.

  5. 05

    Day-to-day work. Owners manage risks, suppliers and incidents, and the board uses the dashboard and the management review.

06 · Frequently asked questions

FAQ

Does a bank apply the KSC Act or the DORA Regulation?

Both acts, to a different extent. The provisions of the KSC Act on the information security management system and on reporting significant incidents do not apply to entities in the banking and financial-market infrastructure sector, with the exceptions listed in art. 8i para. 1. In these areas DORA applies as a sector-specific act in relation to NIS2.

Must a bank be entered in the register of essential and important entities?

Yes. The provisions on the register (art. 7 to 7m) are among the exceptions in art. 8i para. 1, so they also apply to this sector. The application is submitted within 6 months of meeting the conditions (art. 7c para. 1).

Are cooperative savings and credit unions covered by the KSC Act?

Yes, Annex 1 lists them in the banking and financial-market infrastructure sector. The category depends on size: a union that exceeds the thresholds of a medium-sized enterprise is an essential entity, and a medium-sized one is an important entity.

What does the DORA module in CyberSonar24 include?

Ready-made templates of DORA requirements, a gap analysis showing implementation progress and mapping of safeguards to requirements. The module uses the same registers as CyberSonar24 GRC: assets, risks, ICT service providers and incidents.