theDocumentId => 742542 SEC Slaps Yahoo Successor With $35M Fine for 2014 ...

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.

Security Management //

Compliance

4/25/2018
07:00 AM
Scott Ferguson
Scott Ferguson
News Analysis-Security Now
50%
50%

SEC Slaps Yahoo Successor With $35M Fine for 2014 Data Breach

The SEC has hit Yahoo's successor, Altaba, with a $35 million fine related to the company's 2014 data breach.

The successor to Yahoo, Altaba, has been hit with a $35 million fine by the US Securities and Exchange Commission related to a massive 2014 data breach that exposed the personal data of 500 million users.

The SEC announced the multimillion dollar fine on April 24, noting that Yahoo failed for nearly two years to disclose the data breach to its customers, despite that fact that company insiders, including top managers, knew about it for months.

It wasn't until Yahoo was about to be sold to Verizon in 2016 that the company admitted to the data breach.

In December 2014, investigators believe that Russian hackers stole Yahoo's "crown jewels," which included the usernames, email addresses, phone numbers, birthdates, encrypted passwords, as well as security questions and answers for nearly 500 million user accounts.

Later, Yahoo and its successor companies were forced to admit to a second massive cyberbreach that affected as many as 2 billion accounts, including users of Yahoo email, Tumblr, Fantasy and Flickr. (See Yahoo Breach News Just Gets Worse.)

During those two years between the 2014 data breach and the Verizon sale, the SEC investigation found that Yahoo filed several quarterly and annual reports, but did not disclose the breach to federal officials. The company also did not share details with its outside auditors or legal counsel.

Finally, the SEC found that Yahoo's security team did not have procedures in place to disclose the data breach.


The fundamentals of network security are being redefined -- don't get left in the dark by a DDoS attack! Join us in Austin from May 14-16 at the fifth-annual Big Communications Event. There's still time to register and communications service providers get in free!

In a statement released Tuesday, Jina Choi, director of the SEC's San Francisco Regional Office, noted:

Yahoo's failure to have controls and procedures in place to assess its cyber-disclosure obligations ended up leaving its investors totally in the dark about a massive data breach. Public companies should have controls and procedures in place to properly evaluate cyber incidents and disclose material information to investors.

Eventually, the US Department of Justice indicted four people, including two associated with the Russian Federated Security Service (FSB), with the 2014 hack. Despite the data breaches and failure to disclose those to the public, Verizon eventually bought Yahoo and renamed it Oath and former CEO Marissa Mayer walked away with a $23 million payout. (See Unknown Document 731194.)

Related posts:

— Scott Ferguson is the managing editor of Light Reading and the editor of Security Now. Follow him on Twitter @sferguson_LR.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-37436
PUBLISHED: 2021-07-24
Amazon Echo Dot devices through 2021-07-02 sometimes allow attackers, who have physical access to a device after a factory reset, to obtain sensitive information via a series of complex hardware and software attacks. NOTE: reportedly, there were vendor marketing statements about safely removing pers...
CVE-2021-32686
PUBLISHED: 2021-07-23
PJSIP is a free and open source multimedia communication library written in C language implementing standard based protocols such as SIP, SDP, RTP, STUN, TURN, and ICE. In PJSIP before version 2.11.1, there are a couple of issues found in the SSL socket. First, a race condition between callback and ...
CVE-2021-32783
PUBLISHED: 2021-07-23
Contour is a Kubernetes ingress controller using Envoy proxy. In Contour before version 1.17.1 a specially crafted ExternalName type Service may be used to access Envoy's admin interface, which Contour normally prevents from access outside the Envoy container. This can be used to shut down Envoy rem...
CVE-2021-3169
PUBLISHED: 2021-07-23
An issue in Jumpserver 2.6.2 and below allows attackers to create a connection token through an API which does not have access control and use it to access sensitive assets.
CVE-2020-20741
PUBLISHED: 2021-07-23
Incorrect Access Control in Beckhoff Automation GmbH & Co. KG CX9020 with firmware version CX9020_CB3011_WEC7_HPS_v602_TC31_B4016.6 allows remote attackers to bypass authentication via the "CE Remote Display Tool" as it does not close the incoming connection on the Windows CE side if t...