Welcome Guest. | Log In | Register | Membership Benefits

Database Security Market To Grow 20 Percent Through 2014

Mobility, data volume, and difficulty patching still lead challenges in protecting databases

Sep 30, 2011 | 02:02 PM | 

By Ericka Chickowski, Contributing Editor
Dark Reading

Two analyst reports out this month show that as organizations struggle to protect databases that touch a multiplying list of applications and endpoints, the uptick in database security product deployments will continue at a considerable growth rate in the next few years.

According to Forrester Research analyst Noel Yuhanna in his most recent database security market overview report, the database security market is expected to grow by 20 percent through 2014. Yuhanna pegs the current market at $755 million including new licenses and support, database auditing, real-time protection, data masking, vulnerability assessment, and database encryption across all database management system (DBMS) platforms. As that figure grows to $1.2 billion in 2014, Yuhanna says to expect continued consolidation in the market.

"The database security market is likely to converge with the overall data security market in the future, as DBMS vendors extend the security features that are bundled with their products," he wrote. "Larger database security vendors such as Fortinet, IBM, McAfee, and Oracle will continue to dominate the database security market and are likely to acquire independent vendors to fill gaps in their security portfolio."

This year has seen the nexus of a number of trends that could add up to big growth in everything from database activity monitoring to data masking during the coming years. According to a recent database market landscape report out by Enterprise Strategy Group (ESG), historical under-investment in database security, combined with the increased sophistication of advanced persistent threats and a spike in data volume and mobile access points, have all contributed to IT's concern over the matter.

ESG analyst Julie Lockner says that it's no surprise that in a recent survey, slightly over half of IT decision makers listed management of security and compliance issues as one of the biggest challenges to meet within the database environment.

"The big issue is dealing with the mobility factor. Everyone wants to access the database through applications on their mobile devices," says Lockner. "It's an issue of both data volume and the increasing number of endpoints that people are accessing that data through."

According to Forrester's Yuhanna, organizations still continue to struggle also with database patching. In his report, he writes that 41 percent of enterprises still find it a challenge to deal with database patches, mostly due to the effort required for application testing and the frequent need for database shutdown to deploy patches. He believes it is incumbent upon the DBMS vendors to grease the skids in this area.

"We are likely to see some DBMS vendors such as IBM and Oracle improve the overall experience with security patching by automating the patching process and delivering real-time patching that requires no shutdown of databases," he wrote.

Forrester also reports that database activity monitoring and other auditing tools still lead deployment numbers, but the biggest growth has been in database vulnerability assessment tools. The firm says that the use of vulnerability assessment tools for database environments grew by 66 percent from 2008 to 2010. According to ESG's Lockner, these tools should be a bare minimum database security technology for enterprises today.

"If you really believe that your database systems are important, then the lowest common denominator should be vulnerability assessment," she says. "Companies that don't do it at this point are not very wise. It takes a minimal amount of effort and saves so many headaches."

As IT organizations continue to bring in more types of database security products into the mix, they will need to follow a thoughtful risk management approach to prioritize which technologies and which databases see the first deployments. This starts with solid data classification.

"Classifying database data is kind of a foundation," Lockner says. "Once you've classified it, the data should have a level of risk associated with it and that should help you weigh what types of products you use or what type of architecture to build."

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS



Database Security Reports

report Securing The Data Warehouse
Many enterprises are building data warehouses to centralize the ever-increasing information flowing through their organizations into useful repositories. This makes good business sense, but it opens up a slew of concerns from a security standpoint. IT professionals can apply many of the same security best practices used with databases, but there are new lessons to be learned as well.

report Defend Your Data From Malicious Insiders
The biggest threat to your company?s most sensitive data may be the employee who has legitimate access to corporate databases but less-than-legitimate intentions. And while the incidence of insider data breaches has decreased, external attacks often imitate them--and do serious damage. Follow our advice to mitigate the risk.

report Ensuring Secure Database Access
Role-based access control based on least user privilege is one of the most effective ways to prevent the compromise of corporate data. But proper provisioning is a growing challenging, due to the proliferation of "big data," NoSQLdatabases, and cloud-based data storage.

Other reports from the Database Security Tech Center:

Related Content

Establishing a Strategy for Database Security is No Longer Optional
As databases continue to grow in size, complexity and importance, enterprises struggle to identify the most appropriate controls regarding their use and misuse. The report identifies best practices, including: Implementing database activity monitoring to mitigate the high levels of risk from database vulnerabilities, and address audit findings in areas such as database segregation of duties and change management; using data security measures, such as data masking and data encryption; and monitoring privileged-user access and access to critical data.

Database Activity Monitoring Is Evolving Into Database Audit and Protection
In this report, Gartner writes that "Database audit and protection (DAP) represents an evolutionary advance in database activity monitoring tools." DAP suites provide comprehensive, cross-platform support in heterogeneous database environments to protect sensitive data from inappropriate use. Organizations are increasingly concerned with optimizing database security and mitigating risks associated with database vulnerabilities.

Protecting Against Database Attacks and Insider Threats: Top 5 Scenarios
Data security presents a multi-dimensional challenge in today's complex IT environment. Multiple access paths and permission levels have resulted in a broad array of security threats and vulnerabilities. We invite you to read this new eBook: "Protecting against database attacks and insider threats" to learn the top five scenarios and essential best practices for preventing database attacks and insider threats.

Demo: Distributed Database Security with Real-time Monitoring and Audit Protection
Organizations across the globe continue to experience compromised data caused by malicious attacks, web application vulnerabilities or unauthorized changes. View this demo and learn how IBM InfoSphere Guardium? database activity monitoring can help protect your sensitive data in distributed DBMS environments with a holistic approach to data security and compliance.

Look Beyond Native Database Auditing To Improve Security, Audit Visibility, And Real-Time Protection
Today's attacks on enterprise databases are more sophisticated than ever, and they occur so fast that it's often difficult to stop them in real time. Despite significant efforts to protect enterprise databases, the number of records breached has grown each year - due to all types of internal and external attacks and violations of corporate policy.




Featured Webcasts
Featured Whitepapers
Featured Reports