Cybersecurity Risks Associated with EU Data: Notification Obligations for Companies Without an EU Establishment

  • Author: Arno Schlösser, DP-Dock GmbH
  • Last updated: November 2026
  • Category: Data Security, General Obligations

Companies based outside the EU that fall under the GDPR pursuant to Art. 3(2) face a twofold challenge. The threat landscape has become significantly more severe, and notification obligations weigh on them more heavily in an emergency than on competitors with an EU establishment.

1. Key Points at a Glance

  • AI and geopolitical tensions have made cyberattacks faster, cheaper and more scalable.
  • Without an EU establishment, the one-stop-shop mechanism does not apply. Data breaches must be reported separately in each affected Member State. The European Commission’s Digital Omnibus proposal (November 2025) provides for a single reporting point but has not yet entered into force.
  • A tested incident response process is essential for meeting the 72-hour deadline and limiting liability risks.

2. Effective Protective Measures

  • Identity and access management: phishing-resistant MFA (FIDO2/passkeys), the least-privilege principle and alerts for suspicious logins.
  • Zero trust: every access request is verified regardless of network location, and networks are segmented.
  • Vulnerability management: binding patching deadlines, especially for internet-facing systems (e.g. VPN gateways, firewalls and web applications).
  • Backups: offline or immutable, with regularly tested restoration.
  • Detection and response: continuous monitoring, endpoint detection and response (EDR) and a tested emergency plan.
  • Supply chain: vet service providers, restrict external access and set out reporting channels and response times in contracts.
  • Awareness: regular training covering AI-driven phishing and deepfakes, with mandatory verification procedures for unusual instructions.
  • AI-powered defense: faster detection, better alert prioritization and targeted vulnerability discovery.

Strong authentication, consistent patching and tested backups have the greatest impact. Combined with a rehearsed emergency plan, they are also the foundation for meeting the notification deadline under Art. 33 GDPR.

3. Notification Obligations Without an EU Establishment

Under EDPB Guidelines 9/2022, a personal data breach (Art. 33, 34 GDPR) must be reported to every supervisory authority in whose Member State affected individuals reside. Appointing a representative under Art. 27 GDPR does not change this. Cross-border incidents can therefore require numerous parallel notifications, each with its own forms, some in the local language, and all within 72 hours. The deadline starts when the company becomes aware of the breach, regardless of time zones, weekends or public holidays. Until the Digital Omnibus enters into force, the existing requirements apply.

NIS2 and DORA: Under NIS2, certain digital providers without an EU establishment must appoint an EU representative and report significant security incidents separately. This applies to cloud and data center services, managed service providers, online marketplaces, search engines and social networks, among others. They must submit an early warning within 24 hours, an incident notification within 72 hours and a final report within one month. Companies in the financial sector should also review the DORA requirements.

4. Legal and Economic Consequences

  • Fines from multiple supervisory authorities under Art. 83 GDPR. Violations of notification and documentation obligations alone can cost up to €10 million or 2% of global annual turnover.
  • Damages claims under Art. 82 GDPR, which affected individuals can bring at their place of residence (Art. 79(2) GDPR), increasingly through representative and class actions.
  • Reputational damage in the European market.

5. Recommended Actions

  • Create an incident response plan with an EU focus: a list of supervisory authorities, notification templates and clearly assigned responsibilities.
  • Involve the EU representative in the notification process by contract and ensure they can be reached.
  • Organize 24/7 availability aligned with EU time zones.
  • Determine in advance where EU data subjects’ data is stored, so that the affected countries can be identified quickly in an emergency.
  • Document security measures under Art. 32 GDPR as evidence for authorities and in damages proceedings.

6. Conclusion

Professional attackers call for equally professional preparation. Companies that align protective measures, notification processes and documentation early reduce both the risk of an incident and its legal and economic consequences.

DP-Dock GmbH supports you in an emergency by coordinating and communicating with the authorities and by handling all required notifications efficiently and consistently. Contact us for further information.

Glowing red “Data Breach Detected” alert on a digital background of code and data streams – symbolising a detected cyberattack
© SIGIT / stock.adobe.com | #1370812089

Privacy settings

We use cookies on our website. Some of them are essential, while others help us improve this website and your experience.

In this overview you can select and deselect individual cookies of a category or entire categories. You will also receive more information about the cookies available.
Group essential
Name Matomo
Technical name
Provider
Expire in days 72
Privacy policy /en/privacy-policy
Use Use without cookies
Allowed
Group external media
Name Calendly
Technical name __cf_bm,__cfruid,OptanonConsent
Provider Calendly LLC
Expire in days 365
Privacy policy /en/privacy-policy
Use To arrange appointments via the provider Calendly
Allowed
Name Contao CSRF Token
Technical name csrf_contao_csrf_token
Provider Contao
Expire in days 0
Privacy policy /en/privacy-policy
Use Serves to protect the website from cross-site request forgery attacks. After closing the browser, the cookie is deleted again.
Allowed
Name Contao HTTPS CSRF Token
Technical name csrf_https_contao_csrf_token
Provider Contao
Expire in days 0
Privacy policy /en/privacy-policy
Use Serves to protect the encrypted website (HTTPS) against falsification of cross-site requests. After closing the browser the cookie is deleted again
Allowed
Name PHP SESSION ID
Technical name PHPSESSID
Provider Contao
Expire in days 0
Privacy policy /en/privacy-policy
Use PHP cookie (programming language), PHP data identifier. Contains only a reference to the current session. There is no information in the user's browser saved and this cookie can only be used by the current website. This cookie is used all used in forms to increase usability. Data entered in forms will be e.g. B. briefly saved when there is an input error by the user and the user receives an error message receives. Otherwise all data would have to be entered again
Allowed