Perimeter
2/22/2012
11:19 AM
Adrian Lane
Adrian Lane
Commentary
Connect Directly
RSS
E-Mail
50%
50%
Repost This

Can You Delete A Database?

Data and databases keep growing, but there's a security tradeoff

When was the last time you deleted a database -- not accidentally, but on purpose? Have you ever willfully deleted a database? How about removed sensitive data from one?

Most database administrators I've spoken with have never retired the contents of a database. They may migrate the contents of the old database into a newly architected repository, but seldom have they just deleted a database. Or parsed out old data lying around that was clearly obsolete, or possibly truncated tables of sensitive data. DBA's are trained to keep data consistent and make sure the data can be recovered in case of emergency. It's there job, and there is legitimate fear of being fired if you can't produce data when it's requested.

But from a security perspective removing old data is a simple security precaution. Why do I recommend this approach? First off, you can't steal what's not there. If you deleted it from the database and only keep an encrypted tape backup, you're better off if your systems are breached. Second, it's an inexpensive security option that requires no special products and no additional purchases. And as an added bonus, shrinking a database means smaller storage requirements and less overhead on queries, both of which improve performance.

The real problem is this scares the heck out of database administrators. What happens if someone actually wants that data a year from now? Could you recover it? Do you even know who owns it to ask if you can delete it? What if it was subject to regulatory controls you're not aware of? No, it's easier just to keep the data.

And in this day and age where IT keeps more databases, and collects every tidbit of data they can, databases are growing. We collect more data and look for new ways to derive information from it. More data means more information, resulting in better decisions that hopefully provide some competitive sales advantage. Conceptually, anyway. Some firms are under strict regulatory controls to keep data for five- seven-, or even ten years. But studies show data used for analytics purposes goes "bad" -- as much as 30 percent -- after after just 18 months. For your reports that means "Garbage in, Garbage out."

But unlike garbage, bad data does not smell, so DBA's have no good incentive to get rid of it. Until you're breached, that is.

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
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-5704
Published: 2014-04-15
The mod_headers module in the Apache HTTP Server 2.2.22 allows remote attackers to bypass "RequestHeader unset" directives by placing a header in the trailer portion of data sent with chunked transfer coding. NOTE: the vendor states "this is not a security issue in httpd as such."

CVE-2013-5705
Published: 2014-04-15
apache2/modsecurity.c in ModSecurity before 2.7.6 allows remote attackers to bypass rules by using chunked transfer coding with a capitalized Chunked value in the Transfer-Encoding HTTP header.

CVE-2014-0341
Published: 2014-04-15
Multiple cross-site scripting (XSS) vulnerabilities in PivotX before 2.3.9 allow remote authenticated users to inject arbitrary web script or HTML via the title field to (1) templates_internal/pages.tpl, (2) templates_internal/home.tpl, or (3) templates_internal/entries.tpl; (4) an event field to ob...

CVE-2014-0342
Published: 2014-04-15
Multiple unrestricted file upload vulnerabilities in fileupload.php in PivotX before 2.3.9 allow remote authenticated users to execute arbitrary PHP code by uploading a file with a (1) .php or (2) .php# extension, and then accessing it via unspecified vectors.

CVE-2014-0348
Published: 2014-04-15
The Artiva Agency Single Sign-On (SSO) implementation in Artiva Workstation 1.3.x before 1.3.9, Artiva Rm 3.1 MR7, Artiva Healthcare 5.2 MR5, and Artiva Architect 3.2 MR5, when the domain-name option is enabled, allows remote attackers to login to arbitrary domain accounts by using the corresponding...

Best of the Web