European Union: privacy and security obligations
The European Union has a general data protection law and, on top of it, separate laws for network security, financial-sector resilience, digital products and artificial intelligence. An organization is often under more than one, each with its own clock, and the work is to see them together.
Which one applies to what
The laws differ in what they attach to. One follows the personal data, one the sector you operate in, one the financial entity and its suppliers, one the product you sell and one the AI system you build or use.
Where to start
| If | Start here |
|---|---|
| You hold personal data of people in the EU | GDPR programme readiness |
| You operate in an energy, transport, health, digital, manufacturing or other listed sector, or supply those who do | NIS2 readiness |
| You are a bank, insurer, payment or investment firm, or you sell ICT services to one | DORA readiness |
| You make hardware or software that is sold in the EU | Cyber Resilience Act readiness |
| You build or use AI systems | EU AI Act readiness |
The GDPR, DORA, the Cyber Resilience Act and the AI Act are Regulations, which apply directly in every Member State. NIS2 is a Directive, so the rules that bind you are the national law of each Member State where you operate, and they differ; the NIS2 page says how we handle that.
Cookies and tracking: the ePrivacy rule
Separately from the GDPR, the ePrivacy Directive (2002/58/EC), in Article 5(3), allows storing or reading information on a user’s device only with the user’s consent, given after clear and comprehensive information, apart from technical storage needed to carry a communication or strictly necessary for a service the user asked for. How we test a site against that is on website consent and cookie review.
The global pages apply here too
The work that is the same in every country sits on the global pages: privacy services, security services, vendor risk management and technology contract terms. Articles on the EU laws are in Writing.
How the work is bounded
The scope is agreed in writing before work starts, and the engagement is quoted in writing with it.
SecHB does not issue certifications, attestations or audit opinions: those come from accredited certification bodies, CPA firms and QSAs. The work here is what an organization does to be ready for them.
Nothing here is legal advice. Where a question turns on the law, the work is done alongside the client’s counsel, not instead of them.
Tell us which of these you meet
Say what you are, which Member States you operate in and what data or products you handle. The reply says which pages apply and what a scope would cover. Canadian organizations selling into the EU: see also Canada.
European Union pages
Each page says what the regime asks, what the work produces and where it is worked alongside your counsel.
Privacy law
GDPR programme
The GDPR as one programme: what applies, what to build, and which of our privacy services builds each part.
Security and resilience law
NIS2 readiness
Scope facts, measures, management oversight and the 24-hour, 72-hour and one-month reporting stages, prepared against national law.
DORA readiness
The ICT risk framework, incident reporting, testing and third-party register DORA expects, for financial entities and the providers they use.
Cyber Resilience Act
Vulnerability handling, the bill of materials, the support period and the 24-hour and 72-hour reports the Act requires of manufacturers.
AI
EU AI Act readiness
Provider and deployer roles, the dates after the July 2026 amendment, and the inventory and controls the Act relies on.