Dark Reading is part of the Informa Tech Division of Informa PLC
This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.
With Facebook investigating how a software flaw exposed the accounts of some 50 million of its users, European regulators are already asking for answers and gearing up for possible legal action against the social media giant.
On Saturday, September 29, Ireland's Data Protection Commission asked Facebook for more information about the breach, which the company announced the previous day. About 50 million accounts were exposed, and the company had to reset the security tokens of another 40 million users. (See 50M Facebook Accounts Exposed Due to Software Vulnerability.)
Depending on what happens next, the Irish commission could trigger an investigation using the European Union's newly established General Data Protection Regulation (GDPR). Since a fine under GDPR would total 4% of a firm's global revenue, Facebook could face a $1.63 billion penalty, according to an estimate from the Wall Street Journal.
It would be the first large-scale test of GDPR since the law took effect in May. (See GDPR, AI & a New Age of Consent for Enterprises.)
A lot of the discussion, according to The Journal, is centered on the timing of the disclosure and if Facebook notified regulators within the timeframe that GDPR requires. For example, one reason British Airways reported its recent data breach so quickly was to ensure GDPR compliance. (See British Airways Already Facing Lawsuits Following Data Breach.)
Timur Kovalev, CTO of Untangle, which makes network security tools for small businesses, wrote in an email to Security Now that the timing of Facebook's disclosure to EU regulators, as well as to its customers and users, is critical. Whether or not those disclosures satisfy regulators is key to what happens next.
"The Facebook breach that was announced on Friday may be the first test case for the EU to heavily fine a public company for violating their GDPR laws," Kovalev wrote, adding:
With more than 50 million people affected and Facebook already under intense scrutiny from the United States Congress over privacy and security concerns, the company must take extra steps to safeguard their users' data. Before any fine is handed down, the EU must determine if Facebook notified regulators and their users within 3 days of the breach and ensure that Facebook is cooperating with the regulators during the investigation. While it seems Facebook is taking precautionary steps to reset over 90 million accounts, EU regulators must still determine whether Facebook had sufficient measures in place prior to the breach to avoid any fines.
Rishi Bhargava, co-founder of security automation and orchestration firm Demisto, writes that Facebook can point to its security infrastructure and defenses as a way to show compliance. However, it's the company's data collection methods that could test the fledgling GDPR rules.
"And that's where regulators will have to reconcile the vastness of data Facebook collects with what they consider to be 'relevant' data that Facebook collects," Bhargava wrote. "Facebook will attest that its value stems from collecting personalized user data; even irrelevant, tangential data collected can lead to personalized suggestions and a better experience for users. In this scenario, the final decision taken in this case is sure to act as a powerful precedent for tech firms in GDPR violation investigations going forward."
However, not everyone is convinced that the Facebook data breach will result in a fine.
Chris Morales, head of security analytics at Vectra, which sells automated threat management tools, told Security Now in an email that the data exposed by the software flaw was already in the public domain as opposed to banking or credit card information.
Also, Facebook has already reset the tokens of about 90 million users and it's not clear if any of the data had actually been taken.
"The proposed fine is out of proportion with the breach," Morales wrote. "A lot of content that users post on Facebook is shared publicly and cannot be classified as private information. This data breach is different than leaking your personal credit card, health information, or even your personal browsing history. The worst-case scenario is the compromised user tokens could be used to log in to other websites that leverage the FB authentication framework. However, Facebook reset the affected user accounts to clear the tokens."
Related posts:
— Scott Ferguson is the managing editor of Light Reading and the editor of Security Now. Follow him on Twitter @sferguson_LR.
Everything You Need to Know About DNS AttacksIt's important to understand DNS, potential attacks against it, and the tools and techniques required to defend DNS infrastructure. This report answers all the questions you were afraid to ask.
Domain Name Service (DNS) is a critical part of any organization's digital infrastructure, but it's also one of the least understood. DNS is designed to be invisible to business professionals, IT stakeholders, and many security professionals, but DNS's threat surface is large and widely targeted.
Attackers are causing a great deal of damage with an array of attacks such as denial of service, DNS cache poisoning, DNS hijackin, DNS tunneling, and DNS dangling. They are using DNS infrastructure to take control of inbound and outbound communications and preventing users from accessing the applications they are looking for. To stop attacks on DNS, security teams need to shore up the organization's security hygiene around DNS infrastructure, implement controls such as DNSSEC, and monitor DNS traffic
Incident Readiness and Building Response Playbook
In this special report, learn the Xs and Os of any good security incident readiness and response playbook.
Tweet This
1 Comments
