DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

New report: Data Breach Notifications in Europe

Posted on January 13, 2011 by Dissent

The EU’s ‘cyber security’ Agency ENISA, (the European Network and Information Security Agency) has today issued a report on Data Breach Notifications. The EU data breach notification (DBN) requirement for the electronic communications sector in the ePrivacy Directive (2002/58/EC) is vital to increase in the long term the level of data security in Europe. The Agency has reviewed the current situation and identified the key concerns of both the telecom operators and the Data Protection Authorities (DPA)s in its new report.
Recent high profile incidents of personal data loss in Europe have prompted wide discussion about the level of security applied to personal information shared, processed, stored and transmitted electronically.

The Executive Director of the Agency, Prof. Udo Helmbrecht commented:

“Gaining and maintaining the trust of citizens of that their data is secure and protected is an important factor in the future development and take-up of innovative technologies and online services across Europe.”

The introduction of an EU DBN requirement for the electronic communication sector in ePrivacy Directive (2002/58/EC) is important to increase data security in Europe and to reassure citizens that their data is protected by e-communications operators. The Agency has taken stock of the current situation in a new report, by interviewing the national DPAs and a representative sample of companies. The telecommunications sector recognises that DBN have an important role for data protection and privacy. Yet, operators are seeking clarifications at both EU and local level as to comply with DBN requirements. The expectations of DPAs and operators in most cases overlap, but there are some discrepancies.

Key concerns raised by telecom operators and DPAs include:

  • Risk Prioritisation – The seriousness of a breach should determine the level of response. Breaches should be categorised according to risk levels to avoid ‘notification fatigue’.
  • Communication Channels – Operators need assurances that notification requirements will not impact their brands in a negative way.
  • Resources – some regulatory authorities are already occupied with other priorities
  • Enforcement – DPAs indicated that sanctioning authority enables them to better enforce regulations.
  • Undue Delay in reporting – Regulators wants short deadlines for reporting breaches. Service providers, however want to focus their resources on solving the problem.
  • Content of Notifications – Operators want to make sure the notification content does not impact negatively on customer relations. Regulators want all the necessary information.

In 2011, the Agency will develop guidelines for the technical implementation measures and the procedures, as in Art. 4 of Directive 2002/58/EC and analyse the possibility for extending the general obligation of DBN to other sectors, e.g. the financial sector, health care, and small businesses. This will be discussed at a workshop that ENISA organises in Brussels on 24 January, 2011.

For full report: http://www.enisa.europa.eu/act/it/dbn/

Source: ENISA

Category: Commentaries and AnalysesLegislationOf Note

Post navigation

← CT AG looking into UConn breach, demands credit monitoring services
IN: Hospital Security Breach Puts St. Vincent's Patients' Records At Risk →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Alleged Geisinger hacker will defend himself pro se.
  • Tallahassee Memorial Healthcare reveals it was also impacted by Cerner/Legacy Oracle cyberattack
  • Hospital cyberattack investigation complete, no formal review needed
  • Largest Ever Seizure of Funds Related to Crypto Confidence Scams
  • IMPACT: 170 patients harmed as a result of Qilin’s ransomware attack on NHS vendor Synnovis
  • DOJ’s Data Security Program: Key Compliance Considerations for Impacted Entities
  • UBS reports data leak after cyber attack on provider, client data unaffected
  • Scania confirms insurance claim data breach in extortion attempt
  • Cybersecurity takes a big hit in new Trump executive order
  • Episource notifying 5.4 million patients of cyberattack in January

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • DOJ’s Data Security Program: Key Compliance Considerations for Impacted Entities
  • 23andMe fined £2.31 million for failing to protect UK users’ genetic data
  • DOJ Seeks More Time on Tower Dumps
  • Your household smart products must respect your privacy – including your air fryer
  • Vermont signs Kids Code into law, faces legal challenges
  • Data Categories and Surveillance Pricing: Ferguson’s Nuanced Approach to Privacy Innovation
  • Anne Wojcicki Wins Bidding for 23andMe

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.