Now Available:

line

Featured Resources:

line

Newsletter

Email Address:


line

Ask the Expert

Have a question for our resident expert? Email your questions to Rebecca.

« Preventing Data Leakage Through Email and Instant Messaging | Main | What A Nice Surprise: I'm On the IT Security List of Top 59 IT Security Influencers! »

Trying To Determine Actual Numbers of Privacy Breaches Since 1980; An Exercise in Futility?

Today a press release caught my eye, "Hackers get bum rap for corporate America's digital delinquency."

Hmm...sounds interesting. Let's see what is behind this nicely-hooking title.

According to Philip N. Howard, assistant professor in the Communication Department at the University of Washington the compromise of what he projects to be 2 billion individuals' personally identifiable information (PII) records within the U.S. by the end of this year is primarily the fault of business organizations, and not overwhelmingly the fault of hackers.

Yes, organizations are responsible for securing the PII they possess, and they need to implement an effective information security program to reduce risk as much as is reasonable. However, you can never have 100% security; every organization has unknown vulnerabilities that even the best risk assessment cannot reveal.

He based his research on "a review of breached-record incidents as reported in major U.S. news media from 1980 to 2006."

Well, my skepticism of how accurate his findings are going to be just increased again. Until California SB 1386 very, very few breaches were reported. He even acknowledges this within the report.

Howard is also a little behind on the numbers of current state level breach notice laws; he indicates there are "more than 20," which is true, but significantly less than the at least 35 state breach notice laws for which I'm aware.

Even so, I know many of the privacy breaches still do not reach the news media. I know of at least 4 breaches in the last part of 2006, that were appropriately reported to the individuals impacted, that were not publicized.

Part of the press report for the report states:

"Malicious intrusions by hackers make up a minority (31 percent) of 550 confirmed incidents between 1980 and 2006; 60 percent were attributable to organizational mismanagement such as missing or stolen hardware; the balance of 9 percent was due to unspecified breaches. Likely as a result of California's law and similar legislation adopted by other states, the number of reported incidents more than tripled in 2005 and 2006 (424 cases) compared to the previous 24 years (126 cases). The education sector, primarily colleges and universities, amounted to less than 1 percent of all lost records, but accounted for 30 percent of all reported incidents. A single 2003 incident involving 1.6 billion records held by Acxiom, an Arkansas-based company that stores personal, financial and corporate data, dwarfs all others. In that case, the offender controlled a company that did business with Acxiom and had permission to access some files on Acxiom's servers. But he illegally hacked into other records and then tried to conceal the theft, prosecutors charged.

A much different picture emerges, however, when the past quarter century is viewed in terms of the number of reported incidents. Three out of five point to organizational malfeasance of some variety, including missing or stolen hardware, insider abuse or theft, administrative error, or accidentally exposing data online, Howard and Erickson found.

Thanks to the mandatory reporting process established by California, "We've actually been able to get a much better snapshot of the spectrum of privacy violations," Howard said. "And the surprising part is how much of those violations are organizationally prompted -- they're not about lone wolf hackers doing their thing with malicious intent."

While corporate America would prefer to let "market forces" -- factors such as negative publicity and expenses generated by data loss -- take care of the problem the authors aren't convinced that would make for an effective strategy, especially with identity theft listed as the fastest-growing crime in the United States. Based on recent history, it looks as though states are more apt to fill the regulatory void than the federal government, Howard said.

Another noteworthy trend, he said, is what's happening in the education sector, which accounted for nearly a third of reported breaches. This could be explained, Howard and Erickson said, by the fact that colleges and universities "have an organizational culture geared towards information sharing.""


Yes, it is true that the insider threat is significant and a huge amount of incidents and resulting privacy breaches occur through not only malicious insiders, but also through insider mistakes, lack of controls, and lack of knowledge.

What worries me about this press release is his statement, "And the surprising part is how much of those violations are organizationally prompted -- they're not about lone wolf hackers doing their thing with malicious intent."

It reads as though he is dismissing the bad things outsiders try to do to get their hands on PII. What about phishing schemes used against corporate personnel? The report says it did not take these types of attacks into consideration. What about spyware? What about P2P exploits? What about keyloggers? What about the Choicepoint incident, which impacted 163,000 individuals as a result of malicious outsiders, criminals who wanted to get the PII for identity theft purposes? What about...so many others?

I want to see the full report to see what it actually says. Perhaps it provides some clarification.

It did not take me long to find a pre-publication draft of the report on the World Information Access Project site.

Okay, now I'm looking at Table 1. Right away it is looks as though they are basing their conclusions upon vastly incomplete data. They are rolling so many 0's into their interpretation, 0's meaning that either no incidents of PII compromise occurred, as well as 0's that mean no incidents were reported. Just because no incidents were reported in the 1980's, 1990's and early 2000's does not mean no privacy incidents occurred.

So if a tree falls in the forest it does not make a sound? Sounds like the same logic.

Table 2 is also interesting in that it shows hacking to be a significant percentage of breach causes throughout the entire study review period, and the summary shows that 91% of the cumulative breached PII records throughout the years were attributed to hacking. But yet their headline for the press release indicated that hackers were getting a bum rap?

Let's read on...

Yes, organizations are, and should be responsible, for protecting the PII they possess. However, that does not diminish the many different threats hackers also present to PII in the care of organizations.

As I'm reading through this it seems as though the authors have no experience or background as information security practitioners. There is little mention or consideration of the fact that in 1980 data was primarily processed and stored in highly centralized mainframes, but that over the years new technologies have created more mobile computers and more mobile data, putting it at risk in more ways than ever before. Those risks are only going to continue to increase as technology continues it's forward march. Yes, they do acknowledge the technology changes, but it just does not read as being significant within the report.

The report references legal obscenity, indecency, piracy and gambling cases as part of this report when talking about the legal issues of privacy breaches. This seems oddly out of place with the premise of the report findings, even if they are trying to use these cases as a way to show that laws lag behind technology.

It is interesting the report points out that the USA PATRIOT Act strengthened the Computer Fraud and Abuse Act by making it more broadly applicable to computer crimes and increasing the penalties, and how it did not seem to prevent incidents, but the report did not discuss the associated risks to privacy that the USA PATRIOT Act created through the increased surveillance and PII gathering that occurs...data which is then subject to the same breaches risks they are writing about.

Another problem with the report is just with the concept of "hacker." It seems they are basing their description of a hacker upon a referenced text that is 10 years old...and a description of hackers that is even older. That term has definitely changed over the years. And it is still quite subjective. The authors of this report are talking about hackers largely in the original sense of someone who is just curious and wants to learn how a system works and does not really want to do harm. However, a problem with trying to do this is that for the past several years the news media, corporate leaders and most vendors have used the term to mean someone who is malicious and wants to commit crime and mayhem with corporate data. Trying to turn back the clock on the terminology may be a noble academic effort, but it does not translate well to the business leaders who will read the headlines and tell their information security department that they shouldn't worry so much about putting resources toward preventing hackers...information security practitioners have enough trouble getting resources the way it is without having to deal with one more misconception taking away their already meager budgets.

A weakness in this analysis and resulting conclusions is that the data being analyzed is only that which has been reported. The report does acknowledge this:

"Over the decade, journalists would not have discovered all incidents, and even though current California law requires that a person whose data had been compromised be so informed, such a breach is not necessarily noted in news archives."

Indeed.

But I do not believe from the way the report reads that the authors are taking into account how significant the numbers of breaches are that occur but are never reported. And another consideration I did not see accounted for are the numbers of breaches that are never even discovered. Keep in mind that a large number of privacy breaches are not even known to organizations until someone from outside of the organization, most commonly a customer, has notified the organization to let them know that there is unusual activity going on with credit card accounts. Skilled malicious hackers knows how to cover their tracks so that they can continue their crime without being caught for as long as possible.

The report also concedes:

"Consequently, “phishing” or spoofing scams where victims are deceived into volunteering their own personal information are not included in our analysis."

That is too bad, because often times these schemes also exploit in tandem the network upon which the user, many times from their employer's network, is responding.

I am sorry, I am rambling...

All in all I believe the goal of this report was noble and well intended. There are some good pieces of information contained within the report. But I think it is important for information security and privacy practitioners to read it in its entirety and not depend upon the press release that contains the most sensational interpretations of the study.

I really like seeing the results of studies and learning from the interpretations. However, in this case the data used to base conclusions upon are incomplete and cannot be depended upon to truly determine with confidence that hackers are not a significant source of privacy breaches.

As Thoreau said, "we do not know what we do not know."

And it is certainly applicable to determining the true preponderance of PII breaches. There is not consistent data collected for privacy breaches.

Organizations do not collectively all follow the same definitions of breaches to be able to accurately determine the true number of breaches. Most organizations do not even know if they have even been breached.

Trying to put an accurate number, or even range, on the true number of actual PII breaches is a moving target.

I enjoyed reading this report, but my fear is that business executives, CEOs, CIOs and so on, will read the press release and decide that they do not need as many defenses for outside threats.

The bottom line is still the same; organizations need to determine the threats and vulnerabilities applicable for their own unique environments, from both the inside and outside, for all their locations, and establish the controls and safeguards to reduce those resulting risks to an appropriate level for their business.

TrackBack

TrackBack URL for this entry:
http://www.realtime-itcompliance.com/type/mt-tb.cgi/347

Comments

You point out a few significant flaws. My question is, as a person who is educated and keeps up to date on the happenings in the security arena, do you find that such flaws in reports are frequent?

Researching security breaches is of course very important, but is it possible to do it with complete accuracy and precision due to circumstances surrounding available information (breaches not reported, etc.)?

As a side note, Phillip Howard was one of my professors at the University of Washington.

Great questions, Mila.

I believe one flaw was trying to include statistics (basically nonexistant) from clear back to 1980 within the analysis. I personally think it would have strengthed the analysis to instead focus instead upon, and categorized, the breaches that have occurred since California SB 1386 went into effect and then reference the 1980 - 2003 time period examples of breaches without trying to include them in a table used to validate the conclusions.

As the report points out, before passage of California's SB 1386, businesses were not required to report breaches, and so, unless the public somehow found out about an incident, no one outside of the organization ever found out about them. Any statistics of breaches from that period are going to be drastically incomplete.

Another flaw is omitting from analysis consideration of many of the ways in which PII is compromised. Keystroke logging, spyware, phishing, P2p connection exploits, and so on have been used for outside PII breaches.

Also omitting consideration of PII breaches through printed documents and other non-electronic means is a significant gap, but then again, I realize the scope of the analysis was strictly for digital records.

That said, I think the report is good pointing out the need for a comprehensive data protection law. I agree, one law should be applicable to all organizations that handle PII, holding them accountable for protecting PII and applying sanctions based upon the strength of an organization's security and privacy program.

What I thought was another significant flaw was the spin of the publicized headlines for the study. Headlines such as "Forget hackers; companies responsible for most data breaches, study says" that ran in Computerworld. No, organizations should NOT forget hackers; they are still a threat. And the study even shows that around 1/3 of the breaches are due to outside exploits.

In general the attempt to quantify accurate numbers of privacy breaches will always be inaccurate. There will always be a large number of privacy breaches that go unreported, even with laws, the way the laws are written and the large number of loopholes within them. There will always be a large number of privacy breaches that are not even identified. Unknown applications and systems bugs will continue to allow unauthorized access to PII by those exploiting those bugs unless the software vendors make their products more security robust and bug free. The report didn't even address software vendor responsibility from what I saw.

Privacy breaches cannot be quantified with the same degree of accuracy as say, traffic accidents, which occur in the public and always include law enforcement. These types of public, very visible incidents will be possible to more accurately track and maintain statistics about.

Electronic breaches for the most part are not visible, are not public, are often not easy to identify or track the true scope of impact for.

Organizations must be aware of all the types of threats to PII, all the types of vulnerabilities that exist for PII based upon their systems, applications, environments, and practices, and establish the safeguards and controls appropriate for their own unique environment. Organizations need to also demand vendors to create secure applications and systems.

Post a comment

(All comments are approved by site leader before appearing here. Thanks for commenting!)

line

Rebecca Herold's Bio:

Rebecca Herold,CISSP, CIPP, CISM, CISA, FLMI, has been providing information security, privacy and regulatory assistance and services to organizations from a wide range of industries for over 18 years. Rebecca was instrumental in building the information security and privacy program while at Principal Financial Group, which was awarded the CSI Information Security Program of the Year Award in 1998. IT Security ranked Rebecca as one of the top 59 IT security influencers, and Computerworld put Rebecca their list of the 25 top privacy experts and on their list of the 9 best privacy consulting firms. Rebecca has been CPO for two consulting organizations, and has had her own information privacy, security and compliance business since 2004. Rebecca has written chapters for several books, dozens of articles, and has been writing a monthly privacy column for the CSI Alert newsletter since the beginning of 2001, and is working on her 11th book. Some of her other books include The Privacy Papers, Managing an Information Security and Privacy Awareness and Training Program, The Definitive Guide to Security Inside the Perimeter (Realtime Publishers), The Shortcut Guide to Improving IT Service Support through ITIL (Realtime Publishers), and The Practical Guide to HIPAA Privacy and Security Compliance. In addition, Rebecca is the leader of The Realtime IT Compliance Community where she posts to her IT Compliance weblog. You can contact Rebecca at: rebecca_herold@realtimepublishers.net.