Risk
6/19/2005
08:54 PM
Patricia Keefe
Patricia Keefe
Commentary
50%
50%

Data Security Requires A Group Effort

Forty ... million ... credit cards. MasterCard, Visa, Discover, and American Express. That's enough accounts to represent roughly one card each for 19% of the U.S. population that is 18 and over.

Forty ... million ... credit cards. MasterCard, Visa, Discover, and American Express. That's enough accounts to represent roughly one card each for 19% of the U.S. population that is 18 and over.In the last four months we have had at least 14 episodes of exposed data--be it by loss, theft, or hacking. Four of these incidents involved more than a million accounts, but the hacking of CardSystems Solutions last week is the hands-down winner, multiplying by a factor of 10 the number of affected accounts from the next biggest breach from two weeks ago--Citifinancial's 3.9 million accounts.

In this latest incident, roughly 13.9 million of the accessed accounts are MasterCards and about 20 million are Visa cards; Discover and American Express cards account for the remaining 6 million or so accounts.

In most of the 14 data breaches, common sense and or the application of basic security measures appeared to have been lacking. In many of these cases, the victimized companies moved to change their security procedures following the often belated revelations of the breaches.

And so it is with CardSystems. MasterCard's Data Protection policy requires most third-party processors to build and maintain a secure network and implement certain security processes, but whatever CardSystems had in place, it wasn't enough. Following a security audit, the credit processor apparently is changing its security procedures.

But there's no sense getting your knickers in a twist over this one, assures MasterCard. Social Security numbers and other identifying information are not stored on its credit cards, so our identities are safe. And the company claims that only about 68,000 of its affected card holders are at a high level of risk. The other three card issuers haven't had much to say publicly.

So I guess we're all supposed to relax now. Except that we won't. A recent survey by the Cyber Security Industry Alliance found that consumers want something done about the myriad of computer assaults peppering their systems--phishing, viruses and spam--but they don't trust the federal agencies most in a position to legislate protections--Congress and the Federal Trade Commission - to do the right thing. According to another recent survey by Javelin Strategy & Research, consumers think financial institutions focus too much on ID theft resolution, rather than prevention and detection.

Those survey respondents probably won't have to wait long to see some action. My guess is we will now see Congress rush to quell consumer outrage by hastily passing some laws. After all, there are at least four identity-theft-related bills floating around Congress right now, with more on the way.

The thing is, we need a lot more than a federal mandate ordering holders of our data to inform us when it is lost or stolen. That's closing the barn door after all the horses have left. We obviously need to mandate some level of security, and penalties for failing to provide it, since on their own, the data aggregators don't seem able to learn from, or react to, recent history. But thanks to this latest theft, we may have missed the window for some well-thought-out legislation. There is nothing like front-page headlines, angry voters, and the chance the legislators themselves may be victimized to fuel a rush to legislation.

You would think that after the first round of publicized breaches--if not the first round of blustering politicians--a light would have clicked on throughout the tiers of companies involved in collecting and aggregating sensitive consumer data. You would have thought they'd have scrambled to ensure the most basic level of security for this data: Firewalls. Antivirus measures. Encryption. Authentication. New protocols. Overnight shipping and notification for computer tapes. You can doubtless think of more. Some of this will take time to implement, some can be done quickly, and some steps are being taken now, notably at two victims, Bank of America and Visa.

This would be good, but it's not good enough. We don't need a piecemeal approach, every aggregator scrambling for themselves. It's clear the holders of our data are intertwined with one another. And if the industry is smart, they'll lay the groundwork themselves, instead of waiting for Congress to step in.

Last week, we saw the first rustlings of a collective consciousness on this issue. The Liberty Alliance, whose members include vendors, government agencies, and businesses, announced the Identity Theft Protection Group, which will try to provide a group effort toward fighting identity theft. The working group will be headed up by Michael Barrett, VP of security and architecture for American Express.

While it's early yet to divine any specifics, such as target areas or a timetable for something concrete, this is a good sign that someone is paying attention.

More immediately, industry-specific group efforts can pay off. We did it with EDI, we did it with ERP, and we're doing it with RFID right now. What am I talking about? Market-leading companies using their leadership positions like a club and insisting that anyone who wants to do business with them must install and use certain technologies and procedures. It's simple, it works, and it's an opportunity for IT to showcase its leadership, vision, and business acumen. In the case of EDI, vendors pushed by the largest customers speaking as one responded, first by meeting the standard insisted upon, and then by creating PC-based versions of their technology to ensure that companies further down the food chain of suppliers and manufacturers could afford to get on the train. That's what made EDI work. And it will be a big part of making RFID ubiquitous.

We need to do this with data aggregation. We need the credit-card issuers, processors, and reporting bureaus to put aside competitive issues and get together, figure out some security standards, procedures, and protocols, and then to lay down the law throughout the data chain.

We need the enormous political energy and attention that has gone into something silly, such as a small group of overpaid athletes doping themselves, instead diverted into the protection of sensitive personal and financial data.

Just imagine if the regulators and the government announced Monday that no more corporate mergers would be approved until this mess is cleaned up. You can bet the banks would have their acts together in no time. But still, it wouldn't be enough.

This is a cross-industry issue, and it can only be addressed with cross-industry cooperation. IT must help lead the way. We have the know-how. But if it takes legislation to make it so, let's get on with it, before every credit card out there becomes worthless and we start seeing ourselves coming and going.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-8142
Published: 2014-12-20
Use-after-free vulnerability in the process_nested_data function in ext/standard/var_unserializer.re in PHP before 5.4.36, 5.5.x before 5.5.20, and 5.6.x before 5.6.4 allows remote attackers to execute arbitrary code via a crafted unserialize call that leverages improper handling of duplicate keys w...

CVE-2013-4440
Published: 2014-12-19
Password Generator (aka Pwgen) before 2.07 generates weak non-tty passwords, which makes it easier for context-dependent attackers to guess the password via a brute-force attack.

CVE-2013-4442
Published: 2014-12-19
Password Generator (aka Pwgen) before 2.07 uses weak pseudo generated numbers when /dev/urandom is unavailable, which makes it easier for context-dependent attackers to guess the numbers.

CVE-2013-7401
Published: 2014-12-19
The parse_request function in request.c in c-icap 0.2.x allows remote attackers to cause a denial of service (crash) via a URI without a " " or "?" character in an ICAP request, as demonstrated by use of the OPTIONS method.

CVE-2014-2026
Published: 2014-12-19
Cross-site scripting (XSS) vulnerability in the search functionality in United Planet Intrexx Professional before 5.2 Online Update 0905 and 6.x before 6.0 Online Update 10 allows remote attackers to inject arbitrary web script or HTML via the request parameter.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.