Attacks/Breaches

5/24/2017
10:50 AM
Connect Directly
Twitter
LinkedIn
Google+
RSS
E-Mail
50%
50%

Target Reaches Breach Settlement: $18.5 Million Fine, Security Controls

Target to cough up $18.5 million to 47 states in a settlement following its 2013 security breach, which exposed data of millions of customers.

Target will pay a total of $18.5 million to 47 states and the District of Columbia as part of an agreement with the state attorneys general, the New York Times reports.

The settlement for the 2013 security breach that compromised the data of millions of Target customers also mandates that Target implement specific security controls and a governance framework around cybersecurity, and follow certain audit and reporting guidelines.

The $18.5M payout is only a fraction of the Target breach's total cost. Target has shelled out $202 million on legal fees and other costs since the attack, the company reported in its annual statement. However, the fine is significant for a number of reasons.

"It signals the fact that the AGs will continue to use financial penalties to hold companies accountable for data breaches involving both personally identifiable information and other financial information," says Viewpost CSO Christopher Pierson, noting that $18.5M is the largest fine to date for State AGs.

Pierson acknowledges many of the security controls mandated in the settlement reportedly were already n place at Target, but says this signifies a positive direction toward a "more robust program wrapped around controls from a risk and operations perspective."

He calls this settlement a "shot across the bow" for all companies to take security and privacy seriously, and try to mitigate the number and scope of data breaches. While it does not require the CISO report to the board and CEO, it does require reporting throughout the year.

"Given the size, scope, and impact of this particular breach, it appears like an opportunity was missed to have cybersecurity be a direct reporting line to the CEO in a way that supports the cyber risks faced by major businesses today," Pierson says.

Target confirmed its systems were breached in late December 2013. Attackers stole 40 million credit card numbers, as well as their cardholders' names, expiration dates, and CVV codes. Any customer who used a credit or debit card between Nov. 27 and Dec. 15 was at risk.

This settlement marks the end of an investigation into how the hackers broke in. It was determined that attackers took credentials from a third-party vendor, and used them to breach a customer database and install malware that could be used to pilfer more customer data.

Given the attackers' point of entry, Pierson says this breach calls for the resurgence of holistic security programs that combine information assurance, vendor assurance, and procurement/contracting to ensure companies are monitoring their data and who has access to it.

Related Content

Kelly Sheridan is Associate Editor at Dark Reading. She started her career in business tech journalism at Insurance & Technology and most recently reported for InformationWeek, where she covered Microsoft and business IT. Sheridan earned her BA at Villanova University. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
5/24/2017 | 11:06:52 PM
Re: Settlement
@Joe. Oh wow, I missed the initial sentence. Regardless, thanks for clarifying.
Joe Stanganelli
50%
50%
Joe Stanganelli,
User Rank: Ninja
5/24/2017 | 10:56:32 PM
Re: Settlement
@Ryan: Exactly what it says.  The states (and DC).  They were the entities who brought suit under the laws that give them standing to do so.
RyanSepe
50%
50%
RyanSepe,
User Rank: Ninja
5/24/2017 | 12:15:19 PM
Settlement
Who was that settlement of 18.5M paid to, exactly?
CISOs' No. 1 Concern in 2018: The Talent Gap
Dawn Kawamoto, Associate Editor, Dark Reading,  1/10/2018
How to Attract More Women Into Cybersecurity - Now
Dawn Kawamoto, Associate Editor, Dark Reading,  1/12/2018
AI in Cybersecurity: Where We Stand & Where We Need to Go
Raffael Marty, VP Security Analytics, Sophos,  1/11/2018
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The Year in Security: 2017
A look at the biggest news stories (so far) of 2017 that shaped the cybersecurity landscape -- from Russian hacking, ransomware's coming-out party, and voting machine vulnerabilities to the massive data breach of credit-monitoring firm Equifax.
Flash Poll
[Strategic Security Report] Navigating the Threat Intelligence Maze
[Strategic Security Report] Navigating the Threat Intelligence Maze
Most enterprises are using threat intel services, but many are still figuring out how to use the data they're collecting. In this Dark Reading survey we give you a look at what they're doing today - and where they hope to go.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-0290
Published: 2017-05-09
NScript in mpengine in Microsoft Malware Protection Engine with Engine Version before 1.1.13704.0, as used in Windows Defender and other products, allows remote attackers to execute arbitrary code or cause a denial of service (type confusion and application crash) via crafted JavaScript code within ...

CVE-2016-10369
Published: 2017-05-08
unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

CVE-2016-8202
Published: 2017-05-08
A privilege escalation vulnerability in Brocade Fibre Channel SAN products running Brocade Fabric OS (FOS) releases earlier than v7.4.1d and v8.0.1b could allow an authenticated attacker to elevate the privileges of user accounts accessing the system via command line interface. With affected version...

CVE-2016-8209
Published: 2017-05-08
Improper checks for unusual or exceptional conditions in Brocade NetIron 05.8.00 and later releases up to and including 06.1.00, when the Management Module is continuously scanned on port 22, may allow attackers to cause a denial of service (crash and reload) of the management module.

CVE-2017-0890
Published: 2017-05-08
Nextcloud Server before 11.0.3 is vulnerable to an inadequate escaping leading to a XSS vulnerability in the search module. To be exploitable a user has to write or paste malicious content into the search dialogue.