Now on Demand Ransomware Resilience & Recovery Summit - All Sessions Available
Connect with us

Hi, what are you looking for?

SecurityWeekSecurityWeek

Incident Response

Yahoo Faces SEC Probe into Breach Disclosures

In November 2016 Yahoo announced that it was cooperating with federal, state and foreign agencies, including the US Securities and Exchange Commission (SEC), who were seeking information on the data breaches also announced during 2016. In December, the SEC issued requests for relevant documents from Yahoo, and Yahoo is now reported to be under investigation.

In November 2016 Yahoo announced that it was cooperating with federal, state and foreign agencies, including the US Securities and Exchange Commission (SEC), who were seeking information on the data breaches also announced during 2016. In December, the SEC issued requests for relevant documents from Yahoo, and Yahoo is now reported to be under investigation.

In September 2016 Yahoo announced that it had suffered a breach in 2014. It claimed that ‘state-sponsored’ attackers had stolen data from 500 million users. Two months later it disclosed that an earlier breach from August 2013 had led to the compromise of 1 billion user accounts. Yahoo has not said when it knew about these breaches.

Different agencies have different rules about the disclosure of data breaches. The SEC’s own 2011 rules are considered to be vague, and have never been enforced. It investigated the Target breach, but concluded that its own rules were not broken. These require that incidents that could have a “material adverse effect on the business” should be disclosed, but they do not define what this would be. The sheer size of the two Yahoo breaches combined with the intended acquisition of the organization by Verizon could make this a new test case for the SEC rules.

Yahoo may consider that simply disclosing the breaches before the Verizon acquisition is completed (expected to be during Q1 2017) may be sufficient to comply with the SEC rules. The SEC’s primary concern is to protect investors rather than users. Although it was thought that the breaches might cause Verizon to pull out of the acquisition, this is now thought to be unlikely. Yahoo can therefore argue that non-disclosure has not affected investors. 

Verizon originally agreed to pay $4.8 billion for Yahoo, although the New York Post reported that it subsequently sought a $1 billion discount following the first disclosure. The report added, “At the same time, the Yahoo deal team is pushing back hard against any attempts to negotiate the price down, sources said.”

The SEC is best known for its actions against fraud rather than data protection. In October 2016, it ordered one of the Big 4 global audit companies, Ernst & Young, to pay $11.8 million ($1 million fines and $10.8 million in audit fee give-backs plus interest) for missing a major accounting fraud at Weatherford International.

Other agencies are more concerned about the compromise of personal data. In Europe, current data protection laws are enforced by individual national authorities (such as the Information Commissioner in the UK). The Article 29 Working Group comprises representation from all of the national regulators. In October 2016 it wrote to Yahoo asking for breach details: “As Data Protection Authorities (DPAs) in charge of the protection of European individuals’ data, we are deeply concerned by the report and the significant number of EU data subjects which may be affected.”

Any subsequent action from European regulators would come from each individual country concerned. For example, the ICO fined TalkTalk $510,000 in October 2016. Such fines could, however, be dwarfed by those available under the upcoming General Data Protection Regulation. Here, the ICO warns, “A notifiable breach has to be reported to the relevant supervisory authority within 72 hours of the organization becoming aware of it… Failing to notify a breach when required to do so can result in a significant fine up to 10 million Euros or 2 per cent of your global turnover.”

Advertisement. Scroll to continue reading.

It seems almost certain that Yahoo did not make its breach notifications within 72 hours of discovery. The implication is that if the GDPR were already operational, Yahoo would have even more problems than it already has.

Written By

Kevin Townsend is a Senior Contributor at SecurityWeek. He has been writing about high tech issues since before the birth of Microsoft. For the last 15 years he has specialized in information security; and has had many thousands of articles published in dozens of different magazines – from The Times and the Financial Times to current and long-gone computer magazines.

Click to comment

Trending

Daily Briefing Newsletter

Subscribe to the SecurityWeek Email Briefing to stay informed on the latest threats, trends, and technology, along with insightful columns from industry experts.

Join the session as we discuss the challenges and best practices for cybersecurity leaders managing cloud identities.

Register

SecurityWeek’s Ransomware Resilience and Recovery Summit helps businesses to plan, prepare, and recover from a ransomware incident.

Register

People on the Move

Bill Dunnion has joined telecommunications giant Mitel as Chief Information Security Officer.

MSSP Dataprise has appointed Nima Khamooshi as Vice President of Cybersecurity.

Backup and recovery firm Keepit has hired Kim Larsen as CISO.

More People On The Move

Expert Insights

Related Content

Cybercrime

A recently disclosed vBulletin vulnerability, which had a zero-day status for roughly two days last week, was exploited in a hacker attack targeting the...

Data Breaches

LastPass DevOp engineer's home computer hacked and implanted with keylogging malware as part of a sustained cyberattack that exfiltrated corporate data from the cloud...

Incident Response

Microsoft has rolled out a preview version of Security Copilot, a ChatGPT-powered tool to help organizations automate cybersecurity tasks.

Data Breaches

GoTo said an unidentified threat actor stole encrypted backups and an encryption key for a portion of that data during a 2022 breach.

Application Security

GitHub this week announced the revocation of three certificates used for the GitHub Desktop and Atom applications.

Incident Response

Meta has developed a ten-phase cyber kill chain model that it believes will be more inclusive and more effective than the existing range of...

Cloud Security

VMware described the bug as an out-of-bounds write issue in its implementation of the DCE/RPC protocol. CVSS severity score of 9.8/10.