Back to all case studies
CASE STUDY Regulations

How We Completed a National Cybersecurity Audit in 2 Months for a Polish Bank by Reusing PCI DSS Evidence

A Polish bank designated as an operator of essential services needed the audit required by Poland’s National Cybersecurity System Act, the national law implementing the EU NIS framework. We combined it with the results of an earlier PCI DSS assessment, cutting the time bank staff spent on the audit by around 40%. The report went through the bank’s internal audit and was accepted by the competent authority without comments.

Read the Full Story
CLIENT CONTEXT

Who the client is and the challenge they brought to us

Industry

The client is a Polish universal bank that is part of an international banking group. As an operator of essential services in the banking sector, it was subject to the Act of 5 July 2018 on the National Cybersecurity System, which implemented the first NIS Directive, before the 2026 amendment transposing the NIS2 Directive (EU) 2022/2555. The bank’s IT estate combines physical servers, virtual machines and container platforms.

The Challenge

The Act requires an operator of essential services to audit the security of the information system used to provide the essential service at least every two years. The bank had already completed a PCI DSS assessment carried out by Patronusec as a QSA. Teams that had recently supplied evidence for one audit were being asked to prepare another package for a second. The bank’s question was simple: can this be done without repeating the same work?

What Was at Stake

The audit report goes to internal audit and, on request, to the competent authority, which for the Polish banking sector is the Polish Financial Supervision Authority (KNF). Every supervisory comment means further explanations, a remediation plan and risk to the regulatory relationship. On the bank’s side, the Security Manager, infrastructure and application teams, and internal audit were involved; internal audit had to stand behind the report before the board and the supervisor.

OUR APPROACH

A statutory audit delivered in 2 months, building on PCI DSS evidence

  1. Mapping Statutory Requirements to PCI DSS Evidence

    We began by setting the requirements of the Act and its implementing regulations against the results of the earlier PCI DSS assessment. For each area we showed whether existing evidence covered it fully, partially or not at all. From day one, the bank knew what we would ask for and what it would not have to supply twice.

  2. Scope Built Around the Essential Service

    The Act covers the information system used to provide the essential service, while PCI DSS protects card data. The two scopes overlap but are not identical. We defined precisely where PCI DSS results could be reused and where the audit had to go beyond the cardholder data environment.

  3. Verification Across Servers, Virtual Machines and Containers

    Our auditors verified controls in every layer of the bank’s technology: physical servers, virtualisation and container orchestration. For each layer we applied the right techniques for checking configuration and evidence, rather than a single checklist. Interviews with technical teams were held in their language, which kept them short.

  4. Findings in the Light of the Upcoming Amendment

    Alongside findings against the Act as it then stood, the report highlighted the areas affected by the planned amendment transposing NIS2. The bank received not only an assessment of its current position, but also a view of where to prepare for the change in law.

  5. Report Through Our Quality Assurance Programme

    The report went through Patronusec’s internal quality assurance programme, the same one we apply to PCI DSS reports as a licensed QSA. Every finding was linked to evidence and a legal basis. The report went to the bank’s internal audit and then to the supervisor, which accepted it without comments.

RESULTS & SUCCESS METRICS

Concrete figures showing the impact of the engagement

  • 2 months for the audit from kick-off to report
  • ~40% less bank staff time thanks to PCI DSS evidence
  • 0 supervisory comments on the audit report
  • 3 technology layers verified: servers, VMs, containers
  • ~50% of statutory requirements covered fully or partly by PCI DSS evidence
  • 1 report accepted by internal audit without revisions

For the board, the result is a statutory audit closed without supervisory comments, meaning no remediation plan and no further correspondence with the regulator. For finance, it means around 40% less time from key staff spent on the audit. For security and internal audit, it is a report in which every finding has evidence and a legal basis, plus guidance ahead of the NIS2-era rules.

What Our Client Says

Feedback from the client's team after the engagement

"Patronusec’s auditors knew the Act and the direction of its amendment, so we talked about what protects our services rather than how to read individual clauses. Our environment is servers, virtualisation and containers, and they were at ease in every one of those technologies. Technology keeps evolving and they keep up with it, which shows immediately in the questions they ask. Evidence gathered for the PCI DSS assessment was reused wherever it made sense, and our people felt the difference straight away. For the first time, the team spoke about the auditor as a partner."

Security Manager Polish bank

"What I expect from an audit above all is accuracy: every finding needs evidence and every assessment needs a basis. Patronusec’s report met that in full, and I could present it to the board without further explanation. I also value that the audit reused material collected earlier instead of pulling the same people in twice. That saved around 40% of our staff’s time, with no loss of quality. The report went to the supervisor and was accepted without comments."

Head of Internal Audit Polish bank
Frequently Asked Questions

Answers to the questions people in a similar position ask us

Yes, in areas where requirements overlap, such as vulnerability management, access control and monitoring. You need to check, however, whether the PCI DSS assessment scope covers the systems used to provide the essential service. Where it does not, the audit must go beyond the cardholder data environment.

Poland’s amended Act transposing the NIS2 Directive has applied since 3 April 2026 and changes both the list of entities and their obligations. For banks, many ICT risk management and incident reporting obligations are governed by the DORA Regulation (EU) 2022/2554 as sector-specific law. The exact set of obligations for a given bank is therefore worth confirming case by case.

In this project, two months passed from kick-off to report. Duration depends on the complexity of the essential service and how much evidence can be reused from earlier assessments. Mapping requirements to existing evidence at the start usually shortens the timeline the most.
START THE CONVERSATION

Facing a Similar Challenge?

Preparing for NIS2 obligations and want to reuse evidence from assessments you already have? Let’s talk about how to avoid doing the same work twice.

Free 20-min scoping call
No obligation
Senior assessor not sales