Vulnerabilities / Threats
7/25/2013
06:31 PM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Record-Setting Data Breach Highlights Corporate Security Risks

Case of five men indicted Thursday for allegedly stealing more than 160 million credit card numbers, in what Justice Department calls a record size scheme, shows how hard it is for business to deal with SQL injection attacks and similar approaches.

Businesses aren't doing enough to defend their systems against hackers, like the five men charged Thursday by the Justice Department with conspiring to steal data from corporate databases over a seven-year period, according to a San Diego State MIS professor. The Justice Department characterized the alleged criminal enterprise as the largest of its kind to be prosecuted in the United States.

The defendants, four Russians and a Ukrainian, are said to have stolen more than 160 million card numbers and to have inflicted hundreds of millions of dollars in financial harm to more than a dozen major companies. No audit of said costs or detailed breakdown was provided.

The indictment says that the men used a variety of hacking techniques, including SQL injection attacks, to place malware on networks, thereby obtaining login credentials and credit card numbers, known as "dumps," for sale. It also says that the men used network sniffer programs to capture credit card transaction data in real-time from payment networks.

One particular passage in the indictment is noteworthy, in light of recent reports about the extent to which U.S. law enforcement and intelligence agencies can monitor global communication channels, even ostensibly encrypted services like Skype. "After becoming aware that law enforcement tracked certain communications using known messaging services, the co-conspirators established private and encrypted communications channels to avoid detection. Fearing that even these encrypted communication channels could be monitored, several of the co-conspirators ultimately attempted to conduct their communications in person."

[ How deep can U.S. surveillance actually go? Read Can The NSA Really Track Turned-Off Cellphones? ]

Even technically savvy computer hackers, it seems, have doubts about their ability to operate computers securely.

Two of the men, Vladimir Drinkman, 32, of Syktyykar and Moscow, Russia, and Dmitriy Smilianets, 29, of Moscow, were arrested June 28, 2012, while traveling in the Netherlands, at the request of the United States. Smilianets was extradited in September 2012.

The three others, Alexandr Kalinin, 26, of St. Petersburg, Russia, Roman Kotov, 32, of Moscow, and Mikhail Rytikov, 26, of Odessa, Ukraine, remain at large.

The men are alleged to have targeted corporate financial transaction data from 7-Eleven, Carrefour, Commidea, Dexia, Diners Singapore, Dow Jones, Euronet, Global Payment, Hannaford, Heartland, Ingenicard, JCP, JetBlue, NASDAQ, Visa Jordan and Wet Seal.

Kalinin and Drinkman were previously charged in a 2009 indictment with Albert Gonzalez, 32, of Miami, in conjunction with five data breaches, including the 2008 breach of Heartland Payment Systems. Gonzalez is currently serving a 20-year sentence in federal prison sentence for his involvement in those incidents.

"Those who have the expertise and the inclination to break into our computer networks threaten our economic well-being, our privacy and our national security," said U.S. attorney Paul J. Fishman of the District of New Jersey, in a statement. "And this case shows, there is a real practical cost because these types of frauds increase the costs of doing business for every American consumer, every day. We cannot be too vigilant and we cannot be too careful."

However, San Diego State University MIS professor Murray Jennex suggests that companies believe they can be too vigilant and careful, at least in terms of security spending. Despite recent improvements in dealing with SQL injection attacks and other hacking techniques, made after the defendants were engaged in their alleged conspiracy, he said many companies are still susceptible because they don't test their systems adequately and they don't spend enough money on security.

"We've had economic issues so people haven't put as much money into security as they should," Jennex said in a phone interview. Computer security, he explained, doesn't generate revenue, so it's often not a priority, and risk assessments are only as good as the people who conduct them.

Both small and large companies could do more, Jennex argues. "We do audits in small companies and what we still find, over and over again, is that companies don't really understand the way hackers attack," he said.

And even in large companies with substantial IT resources, there's a tendency to do something less than due diligence. Many large companies, Jennex said, rely on open source software but fail to adequately examine the code they're implementing. "If you don't do your research and validate the code, you may overlook vulnerabilities," he said.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
proberts551
50%
50%
proberts551,
User Rank: Apprentice
7/29/2013 | 1:30:58 PM
re: Record-Setting Data Breach Highlights Corporate Security Risks
What also disturbs me, is I heard several years ago, that the IRS has it's Storage hosted in India. Why India? Other than cheap costs?
If this is true, this is a National Security problem in not having the data warehousing local so it can be closely guarded and monitored by US experts? You should never trust anyone with the retirement, and identity of all Americans to a foreign country. If true, this is very bad. I think the SSN numbers should not be retained buy any business any longer than it takes to properly identify the person. It should
not be on any medical records, bank servers, nowhere but the IRS. And pray that
they have the means to guard it.
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-2004-2771
Published: 2014-12-24
The expand function in fio.c in Heirloom mailx 12.5 and earlier and BSD mailx 8.1.2 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in an email address.

CVE-2014-3569
Published: 2014-12-24
The ssl23_get_client_hello function in s23_srvr.c in OpenSSL 1.0.1j does not properly handle attempts to use unsupported protocols, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via an unexpected handshake, as demonstrated by an SSLv3 handshak...

CVE-2014-4322
Published: 2014-12-24
drivers/misc/qseecom.c in the QSEECOM driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, does not validate certain offset, length, and base values within an ioctl call, which allows attackers to gain privileges or c...

CVE-2014-6132
Published: 2014-12-24
Cross-site scripting (XSS) vulnerability in the Web UI in IBM WebSphere Service Registry and Repository (WSRR) 6.3 through 6.3.0.5, 7.0.x through 7.0.0.5, 7.5.x through 7.5.0.4, 8.0.x before 8.0.0.3, and 8.5.x before 8.5.0.1 allows remote authenticated users to inject arbitrary web script or HTML vi...

CVE-2014-6153
Published: 2014-12-24
The Web UI in IBM WebSphere Service Registry and Repository (WSRR) 6.3.x through 6.3.0.5, 7.0.x through 7.0.0.5, 7.5.x through 7.5.0.4, 8.0.x before 8.0.0.3, and 8.5.x before 8.5.0.1 does not set the secure flag for a cookie in an https session, which makes it easier for remote attackers to capture ...

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.