Skip to content

Banking and finance

Cybersecurity for banks and financial institutions under DORA

We help banks and financial institutions meet DORA in practice: we test applications, APIs and cloud, run red teaming aligned with the TIBER-EU methodology and prepare for TLPT.

DORATIBER-EUPSD2EU AI ActECB Cloud Guide
Book a consultation

We reply within 1 business day

Challenges

DORA and TLPT preparation

DORA requires financial entities to test their digital operational resilience regularly. Entities designated by their competent authority must also undergo TLPT at least every three years. We help prepare the scope, the control team and the environment for that test.

Application and API security

We test online and mobile banking, open banking APIs (PSD2) and new channels such as AI chatbots, following OWASP WSTG and ASVS.

Cloud security

Under DORA, cloud is an ICT service from a third-party provider: it needs a risk assessment, contractual provisions and an entry in the register of information, and, where it supports critical or important functions, an exit strategy. We design cloud security architectures that meet these requirements, as in the migration of retail banking to AWS.

Bank network segmentationThe bank network split into segments. In the primary data centre: channel DMZ, external connections zone, SWIFT secure zone, integration and API, payments, core banking, cardholder data (CDE), data and reporting, shared services and business applications. Outside it: the admin network, head office and branches with ATMs, the backup data centre and test environments. One path leads to the SWIFT zone, through a jump server with MFA; cardholder data is reached only through designated ports, and administration runs only from a separate network. Primary data centre Branches and offices S1Customers and internet outside the bank network Customers PSD2 partners S2Payment systems and SWIFT outside the bank network KIR (Elixir), BLIK Visa, Mastercard SWIFT network S3Channel DMZ Internet banking Mobile app (backend) API gateway (PSD2) S4External connections zone KIR gateway (Elixir) BLIK gateway Visa and Mastercard links S5SWIFT secure zone SWIFT interfaces Jump server HSM S6Integration and API Integration bus (ESB) Internal APIs S7Payments Payment hub SEPA transfers Sanctions screening S8Core banking Core system Databases General ledger S9Cardholder data (CDE) Card processing ATM and POS switch HSM and tokenization S10Data and reporting Data warehouse Regulatory reporting Document archive S11Shared services AD and identity DNS and NTP PKI S12Business applications CRM and lending AML and anti-fraud Contact centre S13Admin network PAM, session recording Admin workstations SIEM and SOC S14ATMs ATMs anddeposit machines S15Branches Teller workstations S16Head office Workstations Dealing room S17ICT providers, cloud outside the bank network Cloud services External support S18Backup data centre System replicas Offline backups S19Test environments Test and development Anonymised data P1WAF DDoS protection, HTTPS and API P2Dedicated links encrypted, to KIR, BLIK, cards P3SWIFT link encrypted, from the zone only P4Firewall documented flows only P5Firewall payment messages only P6Back office encrypted message flow P7Internal firewall rules reviewed every 6 months P8Designated ports segmentation tested yearly P9Jump server + MFA the only path to SWIFT P10ATM network encrypted, ATMs only P11Firewall business applications only P12PAM + MFA administration from here only P13Access via PAM on request, sessions recorded P14Replication dedicated link
Bank network segmentationThe bank network split into segments. In the primary data centre: channel DMZ, external connections zone, SWIFT secure zone, integration and API, payments, core banking, cardholder data (CDE), data and reporting, shared services and business applications. Outside it: the admin network, head office and branches with ATMs, the backup data centre and test environments. One path leads to the SWIFT zone, through a jump server with MFA; cardholder data is reached only through designated ports, and administration runs only from a separate network. Data centre Clearing and SWIFT outside the bank network SWIFT zone Payments Card data (CDE) ATMs Head office P2Dedicated links P6Back office P8Designated ports P9Jump server P10ATM network
Fig. 1. Bank network segmentation. Segmentation following PCI DSS v4.0 (CDE scope), SWIFT CSCF (secure zone) and DORA (RTS 2024/1774, Article 13).

Not sure where to start in your organisation? Tell us which systems and regulations apply to you and we will suggest a first step. We reply within one business day.

Let's talk

Frequently asked questions

How do you help prepare for TLPT?

We assess your readiness for the test: the scope of critical functions, the control team and SOC detection and response capabilities. We run red teaming based on the TIBER-EU methodology and, with your SOC, purple team exercises that check whether selected attack techniques are detected. They show the gaps before the actual test. The TLPT itself is carried out by providers that meet the requirements of DORA Article 27.

Does a bank need a NIS2 audit?

Usually not as the first step. For ICT risk management, incident reporting and resilience testing, financial entities apply DORA, which takes precedence as sector-specific law under Article 4 of the NIS2 Directive. That is why we start with a DORA gap analysis for banks.

We'll discuss scope, methodology, and timeline.

Free consultation, no strings attached.

Book a call