Welcome Guest. | Log In | Register | Membership Benefits

Big Data Brings Big Risks

Information stored in data warehouses that service business intelligence applications should be a security priority

Sep 09, 2011 | 12:42 PM | 

By Ericka Chickowski, Contributing Editor
Dark Reading


Business intelligence systems synched with data warehouses provide meaningful information that helps organizations make better business decisions. But what many line-of-business executive types might not realize is that the quicker and easier it is to access these "big data" stores, the greater risk to all of that sensitive information. Just as with the data stored in transactional systems, such as Oracle and DB2, IT needs to protect and monitor access to information stored in data warehouses if it wants to get a handle on that risk.

"Most of the attention in the past has been on transactional database systems, but what about the data warehouses?" says Phil Neray, vice president of data security strategy for IBM. "Those need security, too, because you're still going to have sensitive data, and with big data you're going to have a lot sensitive data, and it's all going to be centralized in one big repository."

According to Neray and other security experts, all the same rules of database security should apply -- things like using the rule of least privilege, encrypting the most sensitive bits of data, monitoring access, and keeping systems patched. But the challenge when dealing with big data is that it is much more difficult to secure it while it is stored in those data warehouses tasked with holding it.

"Discovery is far harder, [and] it's correspondingly easier to leak sensitive information if you don't know what to protect," says Adrian Lane, analyst with Securosis. "Many of these databases are now nonrelational and don't have the same security controls as established relational platforms. For example, many relational platforms have 'labeling' to help segment what a user sees. In nonrelational databases, you need to tag data as it is input and filter the output based on usage rules associated with the tag. "

What's more, it's difficult to encrypt data in warehouses meant to power business intelligence tools because encryption of huge data stores "screws up the processing and analytics," Lane says. It's a conundrum not without readily available technology to solve the problem, though.

"Masking will shield data from people who should not see the real values without effecting the reports. Tokenization is a simple replacement strategy for payment data and PII that does not affect the quality of the metrics," Lane says. "Labeling helps, as does file-level encryption if archives are being made. "

But beyond the technological issues, there lurks around big data a much bigger challenge: politics.

"Data warehouses are expensive and politically sensitive, which causes a tug-of-war between security and cost-effectiveness," says Jake Freivald, vice president of marketing for Information Builders, a business intelligence software firm. "To get the most value from the consolidated, cleansed information data warehouses hold, enterprises should share the information in them as widely as possible. But if that information is valuable to the enterprise, it's also valuable to competitors, saboteurs, and disgruntled employees."

As Freivald explains, even without foul play there's the possibility that someone with access to a data warehouse will accidentally share sensitive information. But it's the motivated malicious insider who can do the most damage without proper monitoring in place.

"Every sales rep should know every detail about every customer in his territory, but you risk having your most successful rep walk out the door with powerful insights about your customers -- insights that you spent an incredible amount of money to develop," he explains, saying the most common security mistake businesses make with big data is not thinking through the threats. "In the business intelligence business, we tend to tout the benefits of information-sharing without considering what could go wrong. Enterprises need to consider carefully how they should balance the need for security with the need to share the data warehouse's information."

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