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.

Risk

10/2/2015
05:15 PM
50%
50%

Scottrade Breach Hit 4.6 Million Customers, Began 2 Years Ago

Social Security numbers might have been exposed, but the main target appears to have been contact information.

Today, Scottrade Inc. announced a breach of 4.6 million customer contact information records (and possibly Social Security numbers), resulting from an attack that occurred between late 2013 and early 2014. 

Scottrade told customers in an email that it had "not seen any fraudulent activity as a result of this incident." However, the company also stated that it learned about the breach from the FBI, which was investigating a rash of breaches involving financial services firms. The company says it has no reason to believe its trading platforms or client funds were compromised, and that the focus appears to have been contact data, possibly to facilitate stock scams.

"A concerning lack of detective capabilities must not have been in place to have missed data exfiltration to the tune of 4.6 million records," says Stewart Draper, director of insider threat at Securonix. "The timeline specified was a particularly sensitive time in this sector with hacktivist and criminal groups regularly targeting financial companies. Federal authorities should not be the avenue with which companies are discovering they may have been breached.  In 2014 Scottrade was fined for failure to provide complete trade logs, blamed on an internal IT error from a migration. Accountability for these mistakes need to be taken at the highest levels of the organization to help drive awareness and improvement in security defense."

"The FBI is unlikely to explain in detail why notification of this breach took so long, but it's not uncommon for an ongoing investigation to delay notification so that criminals aren't tipped off," Tim Erlin, director of IT security and risk strategy at Tripwire.

A Scottrade representative told Wired that the FBI informed them of the breach in August but did ask them to withhold the information from customers until last Friday while they completed a part of the investigtion.

"Cyber criminals behave more like an infestation than the usual metaphor of a burglar," says Erlin. "Once they're inside, it takes more than a rolled-up newspaper to get rid of them."

"Scottrade customers are in the dark about exactly what was taken (the names and addresses were provided by Federal law enforcement), and don’t yet know where the data was taken from," says Trey Ford, global security strategist at Rapid7. "What we do know is that the data appears to have been taken 18-24 months ago. Few, if any, organizations store log data reaching that far back and it’s no wonder Scottrade cannot definitively state what data was taken for this reason."

See more at Scottrade's notice, at KrebsOnSecurity and Wired.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
prospecttoreza
0%
100%
prospecttoreza,
User Rank: Strategist
10/5/2015 | 9:54:38 AM
Scottrade breach
With all these breaches, it seems that there are more accounts stolen than people in US.

One could argue that by this time, there is almost nothing new to be stolen aside from info on kids just entering their credit lives.

So, what is the point of all these breaches? And do they even matter, if everyone is ultimately affected?
Blog Voyage
50%
50%
Blog Voyage,
User Rank: Strategist
10/3/2015 | 9:16:38 AM
Nice
What a drop ! Hoping the best for them
NSA Appoints Rob Joyce as Cyber Director
Dark Reading Staff 1/15/2021
Vulnerability Management Has a Data Problem
Tal Morgenstern, Co-Founder & Chief Product Officer, Vulcan Cyber,  1/14/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-27852
PUBLISHED: 2021-01-20
A stored Cross-Site Scripting (XSS) vulnerability in the survey feature in Rocketgenius Gravity Forms before 2.4.21 allows remote attackers to inject arbitrary web script or HTML via a textarea field. This code is interpreted by users in a privileged role (Administrator, Editor, etc.).
CVE-2021-3137
PUBLISHED: 2021-01-20
XWiki 12.10.2 allows XSS via an SVG document to the upload feature of the comment section.
CVE-2020-27850
PUBLISHED: 2021-01-20
A stored Cross-Site Scripting (XSS) vulnerability in forms import feature in Rocketgenius Gravity Forms before 2.4.21 allows remote attackers to inject arbitrary web script or HTML via the import of a GF form. This code is interpreted by users in a privileged role (Administrator, Editor, etc.).
CVE-2020-27851
PUBLISHED: 2021-01-20
Multiple stored HTML injection vulnerabilities in the "poll" and "quiz" features in an additional paid add-on of Rocketgenius Gravity Forms before 2.4.21 allows remote attackers to inject arbitrary HTML code via poll or quiz answers. This code is interpreted by users in a privile...
CVE-2020-13134
PUBLISHED: 2021-01-20
Tufin SecureChange prior to R19.3 HF3 and R20-1 HF1 are vulnerable to stored XSS. The successful exploitation requires admin privileges (for storing the XSS payload itself), and can exploit (be triggered by) admin users. All TOS versions with SecureChange deployments prior to R19.3 HF3 and R20-1 HF1...