Welcome Guest. | Log In | Register | Membership Benefits

AntiSec's Dump Of Law Enforcement Data Includes Personal Data Of Thousands

Published info contains more than 2,500 SSNs, 15,000 dates of birth, 8,000 passwords, and 45,000 personal addresses, study says

Aug 10, 2011 | 06:42 PM | 

By Tim Wilson
Dark Reading
What types of information are exposed when Anonymous and affiliated hacker groups publish your organization's data? A research team has done a careful study of AntiSec's most recent dump of data from law enforcement agencies -- and for the individuals whose data was involved, the news is not good.

Identity Finder, a maker of identity protection and data leak prevention tools, this week released a detailed analysis (PDF) of the 10-GB confidential data cache of 70 U.S. law enforcement agencies that was published recently by the AntiSec movement.

The study confirms claims by AntiSec stating that the cache contains "hundreds of private email spools, password information, address and Social Security numbers, credit card numbers, snitch information, training files, and more."

Identity Finder used its DLP tools to analyze the published data, which contains information regarding officers, informants, and law enforcement investigations, according to the company. Using its data analysis tools, Identity Finder found 2,719 Social Security numbers (1,923 unique); 15,798 dates of birth, including duplicates; 8,214 passwords, including duplicates; 45,764 postal addresses, including duplicates; eight credit card numbers; 53 driver's license numbers; 89,589 telephone numbers, including duplicates; and 1.5 million email addresses, including duplicates.

"The 1,923 Social Security numbers were one of the biggest concerns because they could be correlated with full names, addresses, and dates of birth," says Todd Feinman, CEO of Identity Finder. "With that information, a hacker can open up a credit card account, or even steal a tax refund."

The data appears to be the same sort of information that attackers might find if they dumped any average worker's computer, Feinman says. It includes a variety of file types, including PDF, PowerPoint, Word, email, and Web server files.

"Of course, it contains information about law enforcement investigations, but in terms of file types, it's fairly typical of what you'd find on the average person's work computer," Feinman says. "We even found 22 pieces of malware that had infected them."

But the way AntiSec exposed the data is very different than the way most cybercriminals compromise data, Feinman observes. "When a cybercriminal steals data, they usually keep it to themselves or sell it to another party," he says. "Your exposure is limited. But in this case, the data is posted to the the whole Web, so any jerk on the Internet can do identity theft."

If movements such as AntiSec continue to attack in this way, they could change the face of enterprise security, in general -- and identity theft, in particular, Feinman suggests. "Some of these law enforcement agencies were relatively small, which shows that any company could be a target," he says. "And the way the data was dumped, there wasn't much separation between sensitive data and public data, which is different than you'd see in a financially motivated attack."

Feinman recommends that organizations take an inventory of the sensitive data they have and get rid of any data they don't need. "We're seeing more customers using our 'shredder' feature now," he says. "If you aren't going to use it, there's no reason to keep it around."

Data leak prevention can help an enterprise identify sensitive data and secure it, but not all DLP products work the same way, Feinman observes. While some reside at the gateway and monitor traffic going in and out of the enterprise, Identity Finder focuses on the endpoint and encourages the end user to decide whether their data should be stored, shredded, or encrypted, he says.

Have a comment on this story? Please click "Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS



Database Security Reports

report Securing The Data Warehouse
Many enterprises are building data warehouses to centralize the ever-increasing information flowing through their organizations into useful repositories. This makes good business sense, but it opens up a slew of concerns from a security standpoint. IT professionals can apply many of the same security best practices used with databases, but there are new lessons to be learned as well.

report Defend Your Data From Malicious Insiders
The biggest threat to your company?s most sensitive data may be the employee who has legitimate access to corporate databases but less-than-legitimate intentions. And while the incidence of insider data breaches has decreased, external attacks often imitate them--and do serious damage. Follow our advice to mitigate the risk.

report Ensuring Secure Database Access
Role-based access control based on least user privilege is one of the most effective ways to prevent the compromise of corporate data. But proper provisioning is a growing challenging, due to the proliferation of "big data," NoSQLdatabases, and cloud-based data storage.

Other reports from the Database Security Tech Center:

Related Content

Establishing a Strategy for Database Security is No Longer Optional
As databases continue to grow in size, complexity and importance, enterprises struggle to identify the most appropriate controls regarding their use and misuse. The report identifies best practices, including: Implementing database activity monitoring to mitigate the high levels of risk from database vulnerabilities, and address audit findings in areas such as database segregation of duties and change management; using data security measures, such as data masking and data encryption; and monitoring privileged-user access and access to critical data.

Database Activity Monitoring Is Evolving Into Database Audit and Protection
In this report, Gartner writes that "Database audit and protection (DAP) represents an evolutionary advance in database activity monitoring tools." DAP suites provide comprehensive, cross-platform support in heterogeneous database environments to protect sensitive data from inappropriate use. Organizations are increasingly concerned with optimizing database security and mitigating risks associated with database vulnerabilities.

Protecting Against Database Attacks and Insider Threats: Top 5 Scenarios
Data security presents a multi-dimensional challenge in today's complex IT environment. Multiple access paths and permission levels have resulted in a broad array of security threats and vulnerabilities. We invite you to read this new eBook: "Protecting against database attacks and insider threats" to learn the top five scenarios and essential best practices for preventing database attacks and insider threats.

Demo: Distributed Database Security with Real-time Monitoring and Audit Protection
Organizations across the globe continue to experience compromised data caused by malicious attacks, web application vulnerabilities or unauthorized changes. View this demo and learn how IBM InfoSphere Guardium? database activity monitoring can help protect your sensitive data in distributed DBMS environments with a holistic approach to data security and compliance.

Look Beyond Native Database Auditing To Improve Security, Audit Visibility, And Real-Time Protection
Today's attacks on enterprise databases are more sophisticated than ever, and they occur so fast that it's often difficult to stop them in real time. Despite significant efforts to protect enterprise databases, the number of records breached has grown each year - due to all types of internal and external attacks and violations of corporate policy.




Featured Webcasts
Featured Whitepapers
Featured Reports