{"id":68915,"date":"2019-08-04T03:09:36","date_gmt":"2019-08-04T10:09:36","guid":{"rendered":"http:\/\/www.taterboy.com\/blog\/2019\/08\/e3s-organizer-apologizes-after-revealing-information-for-thousands-of-journalists\/"},"modified":"2019-08-04T03:09:36","modified_gmt":"2019-08-04T10:09:36","slug":"e3s-organizer-apologizes-after-revealing-information-for-thousands-of-journalists","status":"publish","type":"post","link":"https:\/\/www.taterboy.com\/blog\/2019\/08\/e3s-organizer-apologizes-after-revealing-information-for-thousands-of-journalists\/","title":{"rendered":"E3\u2019s organizer apologizes after revealing information for thousands of journalists"},"content":{"rendered":"

The Entertainment Software Association issued an apology of sorts after making available the contact information for more than 2,000 journalists and analysts who attended this year\u2019s E3.<\/p>\n

\u201cESA was made aware of a website vulnerability that led to the contact list of registered journalists attending E3 being made public,\u201d the organization said via statement. \u201cOnce notified, we immediately took steps to protect that data and shut down the site, which is no longer available. We regret this this occurrence and have put measures in place to ensure it will not occur again.\u201d<\/p>\n

It\u2019s not clear whether the organization attempted to reach out to those impacted by the breach.<\/p>\n

In a kind of bungle that utterly boggles the mind in 2019, the ESA had made available on its site a full spreadsheet of contact information for thousands of attendees, including email addresses, phone numbers and physical addresses. While many or most of the addresses appear to be businesses, journalists often work remotely, and the availability of a home address online can present a real safety concern.<\/p>\n

After all, many gaming journalists are routinely targets of harassments and threats of physical violence for the simple act of writing about video games on the internet. That\u2019s the reality of the world we currently live in. And while the information leaked could have been worse, there\u2019s a real potential human consequence here.<\/p>\n<\/p>\n

That, in turn, presents a pretty compelling case that the ESA is going to have a pretty big headache on its hands under GDPR. Per the rules,<\/p>\n

\n

In the case of a personal data breach, the controller shall without undue delay and, where feasible, not later than 72 hours after having become aware of it, notify the personal data breach to the supervisory authority competent in accordance with Article 55, unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons. Where the notification to the supervisory authority is not made within 72 hours, it shall be accompanied by reasons for the delay.<\/p>\n<\/blockquote>\n

There is, indeed, a pretty strong argument to made that said breach could \u201cresult in a risk to the rights and freedoms of natural persons.\u201d Failure to notify individuals in the allotted time period could, in turn, result in some hefty fines.<\/p>\n

It\u2019s hard to say how long the ESA knew about the information, though YouTuber Sophia Narwitz, who first brought this information to light publicly, may have also been the first to alert the organization. The ESA appears to have been reasonably responsive in pulling the spreadsheet down, but the internet is always faster, and that information is still floating around online and fairy easily found.<\/p>\n

VentureBeat notes rightfully<\/a> that spreadsheets like these are incredibly valuable to convention organizations, representing contact information some of the top journalists in any given industry. Many will no doubt think twice before sharing this kind of information again, of course.<\/p>\n

Notably (and, yes, ironically), the Black Hat security conference experienced a similar breach<\/a> this time last year. It chalked the issue up to a \u201clegacy system.\u201d<\/p>\n

Natasha Lomas contributed to this report<\/em><\/p>\n

Update:<\/strong> An email has since been sent to those impacted, noting,<\/p>\n

\n

We provide ESA members and exhibitors a media list on a password-protected exhibitor site so they can invite you to E3 press events, connect with you for interviews, and let you know what they are showcasing. For more than 20 years there has never been an issue. When we found out, we took down the E3 exhibitor portal and ensured the media list was no longer available on the E3 website.<\/p>\n

Again, we apologize for the inconvenience and have already taken steps to ensure this will not happen again.<\/p>\n<\/blockquote>\n

So that\u2019s that part taken care of, at least.<\/p>\n

\"\"<\/p>\n

Powered by WPeMatico<\/a><\/small><\/p>\n","protected":false},"excerpt":{"rendered":"

The Entertainment Software Association issued an apology of sorts after making available the contact information for more than 2,000 journalists and analysts who attended this year\u2019s E3. \u201cESA was made aware of a website vulnerability that led to the contact list of registered journalists attending E3 being made public,\u201d the organization said via statement. \u201cOnce… Read the full article…<\/a><\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[174,377],"tags":[],"class_list":["post-68915","post","type-post","status-publish","format-standard","hentry","category-games-media","category-gaming"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t