Attacks/Breaches
1/4/2011
12:41 PM
Connect Directly
RSS
E-Mail
50%
50%

Hackers, Insiders Behind Most Identity Theft

Malicious activity topped human error as a cause of the 662 data breaches recorded in 2010 by the Identity Theft Resource Center.

Top 10 Security Stories Of 2010
(click image for larger view)
Slideshow: Top 10 Security Stories Of 2010
Data breaches continue to plague businesses. According to the Identity Theft Resource Center (ITRC), in 2010, there were at least 662 data breaches, exposing more than 16 million records. Nearly two-thirds of breaches exposed people's social security numbers, and 26% of breaches involved credit or debit card data.

According to the ITRC's analysis, more attacks result from malicious intent than human error. The leading malicious causes of data breaches were hacking attacks (17.1%) and insider theft (15.4%). "Data on the move -- taking information from the workplace unprotected -- was 16.6% and accidental exposure on Web/Internet was 11%," said Linda Foley, founder and chairman of the ITRC. "Both are totally preventable and should be 0%."

While the above statistics provide insights into the scale and extent of data breaches, the ITRC also cautioned that it's only a partial picture. That's because 49% of organizations that suffered a breach didn't detail the number of potentially exposed records. In addition, many organizations simply don't disclose data breaches.

What counts as a data breach? The ITRC said it defines a breach as any event that puts a person's name, as well as some piece of unencrypted, sensitive information -- a person's social security number, driver's license number, financial details, or medical records -- at risk.

Not all data breaches are digital. In fact, according to the ITRC, "paper breaches account for nearly 20% of known breaches and typically go unnoticed until a consumer reports the problem to local media." In general, it said, companies have no legal requirement to disclose when their paper records have been breached.

In 2010, organizations that revealed they'd suffered a data breach included Educational Credit Management (3.3 million records), AvMed Health Plans (1.2 million), Lincoln National Financial Securities (1.2 million), South Shore Hospital in Massachusetts (800,000), and Ohio State University (760,000).

Other organizations, such as Experian and Home Depot, also experienced data breaches, but didn't disclose the number of people or records affected. As that suggests, legally speaking, data breach notification often remains a gray territory.

Some states, but not all, have data breach notification laws, which require any organization that suffers a breach to notify that state's affected residents. Interestingly, the ITRC found that information about 29% of the 662 reported breaches for 2010 could be credited to authorities in those states. "This is a clear argument for mandatory reporting to achieve transparency for the public," said the ITRC.

The organization also renewed its call for a single, nationwide clearinghouse of data breach information. "It should be comprehensive enough to allow readers to find out what happened, what information was compromised, and why the breach happened," said the ITRC. "This would also allow law enforcement to better address this type of crime."

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading, September 16, 2014
Malicious software is morphing to be more targeted, stealthy, and destructive. Are you prepared to stop it?
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-2886
Published: 2014-09-18
GKSu 2.0.2, when sudo-mode is not enabled, uses " (double quote) characters in a gksu-run-helper argument, which allows attackers to execute arbitrary commands in certain situations involving an untrusted substring within this argument, as demonstrated by an untrusted filename encountered during ins...

CVE-2014-4352
Published: 2014-09-18
Address Book in Apple iOS before 8 relies on the hardware UID for its encryption key, which makes it easier for physically proximate attackers to obtain sensitive information by obtaining this UID.

CVE-2014-4353
Published: 2014-09-18
Race condition in iMessage in Apple iOS before 8 allows attackers to obtain sensitive information by leveraging the presence of an attachment after the deletion of its parent (1) iMessage or (2) MMS.

CVE-2014-4354
Published: 2014-09-18
Apple iOS before 8 enables Bluetooth during all upgrade actions, which makes it easier for remote attackers to bypass intended access restrictions via a Bluetooth session.

CVE-2014-4356
Published: 2014-09-18
Apple iOS before 8 does not follow the intended configuration setting for text-message preview on the lock screen, which allows physically proximate attackers to obtain sensitive information by reading this screen.

Best of the Web
Dark Reading Radio