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

11/17/2010
07:58 AM
Adrian Lane
Adrian Lane
Commentary
50%
50%

Survey Provides Peek Inside Database Security Operations

Database security budgets on the rise, 20 percent expect to suffer a data breach in the next 12 months

The big news in database security last week was Application Security Inc.'s Database Security Survey (PDF).

Unisphere conducted the research project, surveying 761 SQL Server database professionals, asking questions about environment, budget, security issues, and drivers for security testing. In essence, the study finds that budget for database security is on the rise, that companies are aware that sensitive information is scattered around their organizations without much in the way of controls, and that some 20 percent think they will suffer a data breach in the coming 12 months.

Having tracked this market closely for a decade now, I had a couple of observations on the study:

* It's interesting that database administrators were only involved in security 75 percent of the time (Figure 4). As it stands, most database security tasks involve the database administrator in some way. The setup of auditing, patch management, vulnerability assessment and many other actions must be performed by the DBA. The fact that DBA involvement was _down_ to 75 percent is indicative of the impact data privacy and regulatory efforts, which require separation of duties, are having on the industry.

* The percentage of respondents with monitoring in place was 41 percent (Figure 26). While this is SQL Server specifically, and by my informal count SQL Server databases are more commonly monitored that DB2, MySQL, Postgres, Sybase or just about any database not called Oracle, this percentage seems high to me. I would have expected less than 30 percent using DAM. When you look at which activities are being monitored (Fig 24), the top three -- or 5 of the top 6 for that matter -- are actions normally gathered by native auditing. If I was to venture a guess I would say that these 'monitoring' functions are not Database Activity Monitoring (DAM), rather auditing provided by native audit features such as tracing or system event logging.

* Those reporting no breaches in the last 12 months were 74 percent (Fig 7). Small firms and even small enterprises are not usually targeted the way large enterprises have been. Even if they were susceptible to 0-day attacks or "drive-by malware," odds are they would not have adequate detection and forensics in place to know that they were breached. The number of actual breaches or incidents of information leakage is likely far higher than being reported during the last 12 months.

* Local state data laws was the biggest driver for security (Fig 29), followed by Sarbanes-Oxley. I am not surprised by this, but I imagine that many people are. If I was taking bets I would have said SOX was number one, with state privacy laws at number two. Activity monitoring and assessment has proven incredibly effective at implementing financial controls in complex accounting systems, and can be done in such a way that the auditor is not totally dependent upon IT or accounting to gather information. Similarly, activity monitoring is effective at identifying data misuse, a key for various state data privacy laws. There is a lot of hoopla around PCI and HIPPA, but the customers I speak with use database encryption for compliance, and are far less likely to invest in monitoring and assessment.

* The report implies that most firms are using generalized "configuration management" tools determine database patch levels, or Microsoft's native revision checker. Specialized database assessment tools that look at patching as well as vulnerabilities, configuration defects and user authorization maps. Maybe it's an issue of budget, but most configuration management tools miss the bigger security picture. This is a serious omissions from my perspective as DB assessment is the single greatest tool for database security as it covers all of the basic database security issues. The report is lengthy, but there is a lot of good information here. And 761 respondents, with a nice distribution of company sizes, is a great cross section of the database security market. Thanks to Application Security for funding this project and publishing the results. Definitely worth your time to review.

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
Mobile Banking Malware Up 50% in First Half of 2019
Kelly Sheridan, Staff Editor, Dark Reading,  1/17/2020
7 Tips for Infosec Pros Considering A Lateral Career Move
Kelly Sheridan, Staff Editor, Dark Reading,  1/21/2020
For Mismanaged SOCs, The Price Is Not Right
Kelly Sheridan, Staff Editor, Dark Reading,  1/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment:   It's a PEN test of our cloud security.
Current Issue
IT 2020: A Look Ahead
Are you ready for the critical changes that will occur in 2020? We've compiled editor insights from the best of our network (Dark Reading, Data Center Knowledge, InformationWeek, ITPro Today and Network Computing) to deliver to you a look at the trends, technologies, and threats that are emerging in the coming year. Download it today!
Flash Poll
How Enterprises are Attacking the Cybersecurity Problem
How Enterprises are Attacking the Cybersecurity Problem
Organizations have invested in a sweeping array of security technologies to address challenges associated with the growing number of cybersecurity attacks. However, the complexity involved in managing these technologies is emerging as a major problem. Read this report to find out what your peers biggest security challenges are and the technologies they are using to address them.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-3693
PUBLISHED: 2020-01-24
A symlink following vulnerability in the packaging of mailman in SUSE SUSE Linux Enterprise Server 11, SUSE Linux Enterprise Server 12; openSUSE Leap 15.1 allowed local attackers to escalate their privileges from user wwwrun to root. Additionally arbitrary files could be changed to group mailman. Th...
CVE-2019-3687
PUBLISHED: 2020-01-24
The permission package in SUSE SUSE Linux Enterprise Server allowed all local users to run dumpcap in the "easy" permission profile and sniff network traffic. This issue affects: SUSE SUSE Linux Enterprise Server permissions versions starting from 85c83fef7e017f8ab7f8602d3163786d57344439 t...
CVE-2019-3692
PUBLISHED: 2020-01-24
The packaging of inn on SUSE SUSE Linux Enterprise Server 11; openSUSE Factory, Leap 15.1 allows local attackers to escalate from user inn to root via symlink attacks. This issue affects: SUSE SUSE Linux Enterprise Server 11 inn version 2.4.2-170.21.3.1 and prior versions. openSUSE Factory inn versi...
CVE-2020-7245
PUBLISHED: 2020-01-23
Incorrect username validation in the registration processes of CTFd through 2.2.2 allows a remote attacker to take over an arbitrary account after initiating a password reset. This is related to register() and reset_password() in auth.py. To exploit the vulnerability, one must register with a userna...
CVE-2019-14885
PUBLISHED: 2020-01-23
A flaw was found in the JBoss EAP Vault system in all versions before 7.2.6.GA. Confidential information of the system property's security attribute value is revealed in the JBoss EAP log file when executing a JBoss CLI 'reload' command. This flaw can lead to the exposure of confidential information...