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.

Perimeter

2/6/2013
12:38 PM
Adrian Lane
Adrian Lane
Commentary
50%
50%

Restarting Database Security

Why companies ask for a database security program

"How do we put together a database security program?"

That has been the most common database security question I've received in the past nine months. I've been surprised by the number of firms that have asked for my assistance with setting up a database security program -- mostly because large firms are the ones that already have parts of a program in place. More to the point, both large and midsize firms, which have at one time bought database security products and have some database security processes, see they have a problem. The motivation for today's post is not just to relay the trend, but why companies are asking the question.

I've been talking publicly -- occasionally preaching -- about database security for the past 12 years. Database security platforms are no longer merely tools but fully mature, mainstream products. In all honesty, I thought in the evolution of database security that we were past the point of program setup, but I was wrong for a number of reasons: There are teams that broke up or stopped doing what they did due to budget. There are companies that had it, got acquired, and the parent neither had a database security program nor do existing processes from smaller firms work with the much larger parent.

In some cases companies have database security, but it's only implemented within a subset of business lines or limited to specific geographies. Some firms have database security only within one group (security, DBAs, ops), with the program limited to what the group does best (i.e.: DBAs do patching). Many limit security to specific database platforms (e.g.: Oracle experts handle Oracle, but nobody addressed MySQL, Sybase, or other platforms). And finally, companies relaxed security constraints, a little bit at a time, and then found they went too far.

And it's this latter trend that is worrisome. The trend with firms that have not been breached or suffered an "incident" is a slow and gradual pressure to relax controls. Users want additional privileges -- and they usually get what they want. DBAs don't like the hassle of providing, then revoking, privileges every few weeks. DBAs don't like having to log in under different credentials to perform granular tasks, or coordinate straightforward admin work across two or more people. It's easier to leave openings for tools and utilities that streamline tasks and make accessibility easier. It saves time and makes the job less aggravating.

Until they've been breached. Or data is exfiltrated. Or an employee abuses the database. Then everything changes.

For all of these reasons, companies need to reconsider database security. Most of the time, it's a small number of people within very large companies who understand they have a problem and are looking for guidance. They need consistency across the company. It's level-setting -- of getting everyone responsible for security and compliance on the same page about where they are and where they need to go.

So where do you start? What are the first steps in building a database security program? I'll answer that in an upcoming post.

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
Navigating Security in the Cloud
Diya Jolly, Chief Product Officer, Okta,  12/4/2019
SOC 2s & Third-Party Assessments: How to Prevent Them from Being Used in a Data Breach Lawsuit
Beth Burgin Waller, Chair, Cybersecurity & Data Privacy Practice , Woods Rogers PLC,  12/5/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Our Endpoint Protection system is a little outdated... 
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
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-19698
PUBLISHED: 2019-12-10
marc-q libwav through 2017-04-20 has a NULL pointer dereference in wav_content_read() at libwav.c.
CVE-2019-4428
PUBLISHED: 2019-12-09
IBM Watson Assistant for IBM Cloud Pak for Data 1.0.0 through 1.3.0 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session....
CVE-2019-4611
PUBLISHED: 2019-12-09
IBM Planning Analytics 2.0 is vulnerable to cross-site scripting. This vulnerability allows users to embed arbitrary JavaScript code in the Web UI thus altering the intended functionality potentially leading to credentials disclosure within a trusted session. IBM X-Force ID: 168519.
CVE-2019-4612
PUBLISHED: 2019-12-09
IBM Planning Analytics 2.0 is vulnerable to malicious file upload in the My Account Portal. Attackers can make use of this weakness and upload malicious executable files into the system and it can be sent to victim for performing further attacks. IBM X-Force ID: 168523.
CVE-2019-4621
PUBLISHED: 2019-12-09
IBM DataPower Gateway 7.6.0.0-7 throug 6.0.14 and 2018.4.1.0 through 2018.4.1.5 have a default administrator account that is enabled if the IPMI LAN channel is enabled. A remote attacker could use this account to gain unauthorised access to the BMC. IBM X-Force ID: 168883.