Major Health Data Breach in Poland: Lessons for International Companies
- An incident at a processor can trigger a company's own GDPR obligations
- Companies should regularly review service providers, contracts, and risks
- Sub-processors and international data transfers require transparency
- A tested incident response plan strengthens readiness to act in an emergency
A cyberattack on an external service provider can, within a matter of hours, become its customers’ own legal, operational, and reputational risk. A data breach at a processor is not confined to that organization alone: it can trigger reporting obligations, disrupt business processes, and jeopardize the trust of customers, employees, and business partners.
Virtually every company is exposed to this risk. Personal data today is routinely processed by cloud providers, software companies, HR service providers, platform operators, or external IT providers. Companies must therefore ensure, even before a potential incident occurs, that their service providers are properly vetted, their contracts are robust, and their incident response processes also account for a data breach at a service provider.
The case of the Polish health IT provider MyDr shows the scale such an incident can reach and the questions it raises for German companies as well.
What happened at MyDr?
MyDr provides software for electronic medical documentation used by an estimated 10,000 to 12,000 healthcare facilities in Poland. In August 2026, unauthorized access to the company’s systems became known, along with a possible leak of around 19 million PESEL numbers and approximately 2.5 terabytes of data. Information on prescriptions, medications, medical appointments, and treatments may have been affected, among other things.
The scale becomes clear in relation to the population: Poland has around 37 million inhabitants. The incident could therefore affect the data of roughly half the population.
According to the Polish Ministry of Health, the incident was confined to MyDr’s systems; Poland’s central state e-health systems were not affected. The Polish data protection authority launched a review of the company’s security measures and risk analysis.
The allocation of roles is legally decisive: MyDr processes patient data as a processor. The medical facilities using the system generally remain controllers for their patients’ data. The technical incident therefore occurred at the service provider but could trigger its own review, reporting, and notification obligations for thousands of its customers.
Why can this case also relevant to international companies?
This case is not limited to Poland or the healthcare sector. International companies today outsource numerous data-intensive processes, for example:
- HR administration and payroll,
- cloud hosting and data storage,
- CRM and marketing processes,
- financial accounting and payment processing,
- customer and employee portals,
- document management,
- IT support and cybersecurity.
A cyberattack on a service provider therefore does not only affect that provider’s own systems and interests. Every customer company must quickly determine whether data processed on its behalf has been affected by unauthorized access or a data leak, which individuals may be affected, and what legal or contractual obligations arise as a result.
Engaging an external provider does not relieve the controller of its obligations under the GDPR. The processor must notify the controller without undue delay of any personal data breach that becomes known to it. The controller, in turn, must assess whether a notification to the data protection authority under Art. 33 GDPR and, where applicable, notification of the affected individuals under Art. 34 GDPR is required.
This often involves considerable time pressure. The GDPR’s 72-hour deadline does not wait for the service provider to complete its forensic investigation. If responsibilities, communication channels, and decision-making processes are not defined in advance, a data breach at a service provider can quickly become the company’s own compliance crisis.
What lessons should companies draw from this?
Processors must be continuously reviewed
Art. 28 GDPR requires controllers to use only processors that provide sufficient guarantees of appropriate technical and organizational measures.
This review must not end once the contract is signed. Service providers change their infrastructure, bring in new sub-processors, expand their services, or process significantly larger volumes of data as the cooperation continues. Effective vendor risk management must capture such changes.
How intensively a company should review its processors depends on the respective risk. Key factors include, in particular, the sensitivity and scope of the data processed, the importance of the service provider to business operations, and the potential consequences of a failure or unauthorized access.
A provider’s reputation, market position, or the widespread use of its software are no substitute for a documented risk assessment.
The data processing agreement must include appropriate security requirements
The adequacy of the data processing agreement, including the security requirements set out in it, can be decisive for whether a company can effectively defend itself before the data protection authority or in the event of potential claims by affected individuals.
Under Art. 28 GDPR, controllers may only use processors that provide sufficient guarantees for implementing appropriate technical and organizational measures. This assessment should be documented in a traceable manner. The integration of a solution into a national infrastructure does not, by itself, constitute evidence of lower risk.
Companies must know the entire processing chain
Processing often does not end with the directly engaged provider. That provider may use additional cloud, hosting, support, or analytics service providers.
Controllers should be able to determine at any time which sub-processors are involved, where the data is processed, and which legal safeguards apply to international data transfers. Without this transparency, it becomes significantly more difficult in an actual emergency to assess the risk and reliably inform authorities or affected individuals.
A prepared incident response plan is crucial
The speed and clarity of the response affect both the regulatory and reputational consequences of a security incident. In the MyDr case, several days passed between the first indications of a possible data breach and the public confirmation of its scale. Official statements remained cautious during this time.
An incident response plan prepared and tested in advance should, in particular, govern internal escalation, forensic investigation, and notification of controllers. Such preparation can help ensure that a security incident remains manageable and does not develop into a full-blown crisis.
What should management review?
- Were the processors carefully selected and vetted?
- Is the assessment of the service provider and the risk analysis documented and up to date?
- Do the data processing agreements contain appropriate security and reporting obligations?
- Are sub-processors and international data transfers known and documented?
- Is a prepared and tested incident response plan in place?
If these questions cannot be answered clearly, contracts, risk assessments, and internal processes should be reviewed. The MyDr case shows that the key prerequisites for an effective response are established long before a possible security incident occurs.
Conclusion: A service provider incident quickly becomes a company’s own risk
The MyDr case shows how a security incident at a single processor can simultaneously confront numerous controllers with their own review, reporting, and notification obligations.
What matters most is the careful selection and regular review of processors, appropriate contractual security requirements, transparency regarding sub-processors and international data transfers, and a prepared and tested incident response plan.
Companies cannot completely rule out the risk of a data breach at a processor. However, they can prepare in such a way that they remain able to act even under considerable time pressure, fulfill their legal obligations, and limit legal, financial, and reputational consequences.
Is your company prepared for a data breach at a service provider?
An incident at a processor can require far-reaching legal and organizational decisions at short notice.
As your trusted partner, we can help you identify risks at an early stage, prepare your organization for potential incidents, and respond with legal certainty in an emergency. Please feel free to contact us.