Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Application Security //

Database Security

5/17/2013
03:32 PM
Adrian Lane
Adrian Lane
Commentary
50%
50%

Why Database Monitoring?

Hoping other people detect your breach before you lose millions is not a good strategy

Why should you monitor database activity? This is why! Hackers stole $45 million from ATMs -- a theft made possible by breaching several bank databases and make simple alterations that allowed thieves to siphon of cash.

Do you understand how hard it is to take $45 million from ATM machines in $2,000 increments? Do you realize that's more than 20,000 withdrawals? What's more troubling is this was the second attack. The first, committed several months before, successfully netted $5 million. Police caught up with some of the attackers on the second attack only after they had managed to steal another $40 million, but not by being nabbed at ATMs or tracked back to the source. Rather, one of the "money mules" got greedy, killed one of the ringleaders, and police stumbled on the theft ring as part of a murder investigation.

The sad thing is that the easiest point of detection should have been through the database. The entire attack is predicated on breaching the database of ATM/gift cards, finding the card numbers, and altering the withdrawal limits of those cards. For you database experts out there, you know that this takes about three or four SQL statements to do. It's also a dead simple attack to detect, and one of the types of attacks that database activity monitoring systems were designed for.

The simplest way to stop the thieves would have been to detect the alterations and then lock the card numbers or limits so they could not be used. Or they could have detected the attack and then coordinated with law enforcement to catch the thieves as they started taking out money. They would have had lots of opportunities to catch them -- about 20,000 or so.

And if you read the Verizon Data Breach Report, you noticed that 69 percent of the breaches were not detected by the company; rather, they were detected by outsiders. So what sounds easier, faster, and cheaper? Hoping someone outside of your company detects the data breach for you before $45 million is stolen, or detecting the first phase of the attack while it happens?

Sure, this is one of the more costly attacks in the past decade, but the point should be clear: Monitor databases that hold financial information!

Adrian Lane is an analyst/CTO with Securosis LLC, an independent security consulting practice. Special to Dark Reading. Adrian Lane is a Security Strategist and brings over 25 years of industry experience to the Securosis team, much of it at the executive level. Adrian specializes in database security, data security, and secure software development. With experience at Ingres, Oracle, and ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Data Leak Week: Billions of Sensitive Files Exposed Online
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/10/2019
Intel Issues Fix for 'Plundervolt' SGX Flaw
Kelly Jackson Higgins, Executive Editor at Dark Reading,  12/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
The Year in Security: 2019
This Tech Digest provides a wrap up and overview of the year's top cybersecurity news stories. It was a year of new twists on old threats, with fears of another WannaCry-type worm and of a possible botnet army of Wi-Fi routers. But 2019 also underscored the risk of firmware and trusted security tools harboring dangerous holes that cybercriminals and nation-state hackers could readily abuse. Read more.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-5252
PUBLISHED: 2019-12-14
There is an improper authentication vulnerability in Huawei smartphones (Y9, Honor 8X, Honor 9 Lite, Honor 9i, Y6 Pro). The applock does not perform a sufficient authentication in a rare condition. Successful exploit could allow the attacker to use the application locked by applock in an instant.
CVE-2019-5235
PUBLISHED: 2019-12-14
Some Huawei smart phones have a null pointer dereference vulnerability. An attacker crafts specific packets and sends to the affected product to exploit this vulnerability. Successful exploitation may cause the affected phone to be abnormal.
CVE-2019-5264
PUBLISHED: 2019-12-13
There is an information disclosure vulnerability in certain Huawei smartphones (Mate 10;Mate 10 Pro;Honor V10;Changxiang 7S;P-smart;Changxiang 8 Plus;Y9 2018;Honor 9 Lite;Honor 9i;Mate 9). The software does not properly handle certain information of applications locked by applock in a rare condition...
CVE-2019-5277
PUBLISHED: 2019-12-13
Huawei CloudUSM-EUA V600R006C10;V600R019C00 have an information leak vulnerability. Due to improper configuration, the attacker may cause information leak by successful exploitation.
CVE-2019-5254
PUBLISHED: 2019-12-13
Certain Huawei products (AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG6000V;eSpace U1981) have an out-of-bounds read vulnerability. An attacker who logs in to the board m...