Attacks/Breaches
4/29/2013
08:17 PM
Connect Directly
RSS
E-Mail
50%
50%
Repost This

Recent Breaches More Likely To Result In Fraud

A victim whose data is stolen in the past year will have a 1-in-4 chance of becoming a fraud victim as well, says Javelin's latest breach analysis

A year-old breach of a Utah Department of Health (UDOH) server that resulted in the theft of personally identifiable information on 780,000 Utahns will likely result in up to $500 million in fraud and other damages to the victims, underscoring the ultimate costs of security lapses, analyst and consulting firm Javelin Strategy & Research said in an analysis of the costs.

The breach, which succeeded because a contractor had set the server up with an easily guessable password, will cost the state up to $10 million, including two years of identity theft protection for the victims. Yet the victims will likely pay much more -- $406 million in fraud losses and $94 million in other costs, including the estimated 2.4 million hours needed to resolve the fraud, according to Javelin.

"The bad guys are getting better at using the information obtained from breaches to commit fraud," says Alphonse R. Pascual, senior analyst in Javelin's Security, Risk & Fraud group. "They are getting better at mining the data, and they are getting better at selling it."

The UDOH breach has led to new state legislation, empaneled a committee of experts to recommend changes to security practices, and could lead to fines. The director of the state of Utah's Department of Technology Services (DTS) lost his job following the breach.

While companies tend to measure breaches in terms of the direct cost to their businesses, they may want to think of the attacks in broader terms: the impact to their customers. Consumers whose information was stolen as part of a data breach in 2012 have a 1-in-4 chance of becoming a victim of fraud, up from a 1-in-10 chance in 2010, Pascual says.

[SQL injection, post-phishing privilege escalation, and poorly secured back-up information all played their part in exposing sensitive government data stores this year. See 10 Top Government Data Breaches Of 2012.]

As companies think about the impact of an attack on their bottom lines, they should consider whether the reputation damage will result in the loss of customers, says Tim Francis, vice president of portfolio management and the cyber lead at Travelers Bond and Financial Products.

"We tend to talk about the cost to the company as the place where the costs live and die, and not about the costs to the actual victims," he says.

While some companies, especially those that have to comply with government or industry regulations, have reduced their data retention to minimize the amount of information that falls within the scope of regulations, most companies will not want to follow that route, Francis argues.

"Companies, by and large, are paying more attention to the data they are taking in, but you also see that companies love data," he says. "They are building analytics around customer data to slice and dice the information so that they can to try to enhance revenue."

Yet Pascual stresses that there are good, and necessary, uses of data, as well as ways that data is poorly used or unnecessarily stored. Social Security numbers (SSNs), for example, are widely compromised and should never be used for a security credential, but many banks still allow them. Javelin found that 80 percent of financial institutions continue to allow customers to identify themselves using their SSNs, an abysmal security practice, the analyst firm states.

"This is static knowledge-based authentication of the worst kind," Pascual wrote in a blog post analyzing the UDOH breach. "SSNs are like the Twinkies of KBA [knowledge-based authentication] in that they have an indefinite shelf life -- they will be valuable for criminals as long as the financial industry continues to use them in this manner."

Finally, companies should educate and train their employees to minimize the risk of data breaches. In an analysis of 2012 data breached, managed security provider Trustwave found that nearly half were caused by remote access systems left vulnerable through misconfiguration. The No. 1 password discovered by the firm? Password1.

Companies need to understand who and what they are securing their systems against to best secure their customers' data, says Chris Pogue, director of SpiderLabs at Trustwave.

"It really is understanding more than just, 'I have stuff, and I need to secure it,'" he says. "It is understanding attack vectors, it is understanding criminal motivations, and it is understanding how crimes are committed."

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Robert Lemos is a veteran technology journalist of more than 16 years and a former research engineer, writing articles that have appeared in Business Week, CIO Magazine, CNET News.com, Computing Japan, CSO Magazine, Dark Reading, eWEEK, InfoWorld, MIT's Technology Review, ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
macker490
50%
50%
macker490,
User Rank: Apprentice
4/30/2013 | 12:51:48 PM
re: Recent Breaches More Likely To Result In Fraud
think about things for a minute: when you use a credit card you are not authorizing the one transaction. you are authorizing the merchant unrestricted access to your account indefinitely.

if the merchant gets hacked the hackers can then rob your card.
Register for Dark Reading Newsletters
White Papers
Cartoon
Latest Comment: LOL.
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2011-3154
Published: 2014-04-17
DistUpgrade/DistUpgradeViewKDE.py in Update Manager before 1:0.87.31.1, 1:0.134.x before 1:0.134.11.1, 1:0.142.x before 1:0.142.23.1, 1:0.150.x before 1:0.150.5.1, and 1:0.152.x before 1:0.152.25.5 does not properly create temporary files, which allows local users to obtain the XAUTHORITY file conte...

CVE-2013-2143
Published: 2014-04-17
The users controller in Katello 1.5.0-14 and earlier, and Red Hat Satellite, does not check authorization for the update_roles action, which allows remote authenticated users to gain privileges by setting a user account to an administrator account.

CVE-2014-0036
Published: 2014-04-17
The rbovirt gem before 0.0.24 for Ruby uses the rest-client gem with SSL verification disabled, which allows remote attackers to conduct man-in-the-middle attacks via unspecified vectors.

CVE-2014-0054
Published: 2014-04-17
The Jaxb2RootElementHttpMessageConverter in Spring MVC in Spring Framework before 3.2.8 and 4.0.0 before 4.0.2 does not disable external entity resolution, which allows remote attackers to read arbitrary files, cause a denial of service, and conduct CSRF attacks via crafted XML, aka an XML External ...

CVE-2014-0071
Published: 2014-04-17
PackStack in Red Hat OpenStack 4.0 does not enforce the default security groups when deployed to Neutron, which allows remote attackers to bypass intended access restrictions and make unauthorized connections.

Best of the Web