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.


08:23 PM
Adrian Lane
Adrian Lane
Quick Hits

Security Implications Of Big Data Strategies

Big data can introduce new access challenges -- and new security vulnerabilities -- to your organization. Here are some tips for keeping data safe

[Excerpted from "Security Implications Of Big Data Strategies," a new report posted this week on Dark Reading's Database Security Tech Center.]

The term "big data" is often misunderstood. In fact, it has been used so often, by so many people to push such specific agendas that the term has become almost meaningless.

Yes, big data is storing and processing very large data sets. However, it embodies a lot more than that.

When trying to get a handle on big data, it's helpful to consider it more an idea than a specific size or technology. In its simplest terms, the big data phenomenon is driven by the intersection of three trends: mountains of data that contain valuable information, the abundance of cheap commodity computing resources and virtually free analytics tools. When talking about security of big data environments, it's the last item -- virtually free analytics tools -- that often raise security concerns.

As of this writing, there are more than 120 variations of big data management systems focusing on different data types (for example, geolocation data, documents and tuple storage).

These systems use many different query models; different data storage models; and different task management, orchestration and resource management tools. While big data is often described as anti-relational (as shown by the term "NoSQL"), that concept also fails to capture the essence of big data.

It's true that big data implementations cast off many of the core features of relational databases to get around the associated performance issues, but make no mistake: Some big data environments offer relational structures, transactional consistency and structured query processing.

Since conventional definitions fail to capture the essence of big data, think about it in terms of the key elements that comprise big data environments. They use many nodes for distributed data storage and management.

They store multiple copies of data, "sharding" pieces of data across multiple nodes. This provides the benefits of fail-safe operation in the event any single node fails, and it means the data queries move to the data, where processing resources are available. It's this distributed cluster of data nodes that cooperate with each other to handle data management and data queries that makes big data different than "big iron."

The essential characteristics of big data -- the things that allow it to handle data management and processing requirements that outstrip previous data management systems, such as volume, data velocity, distributed architecture and parallel processing -- are what make securing these systems all the more difficult. The clusters are somewhat open and self-organizing, and they allow users to communicate with multiple data nodes simultaneously.

Validating which data nodes and which clients should have access to information is difficult. The elastic nature of big data means new nodes are automatically meshed into the cluster, sharing data and query results to handle client tasks.

In the mad race to do more with big data -- to add new features and push the boundaries of scalabilities -- the vast majority of development resources go to the improvement of big data scalability, ease of use and analysis capabilities.

A very low percentage of resources goes into adding security features. But you want security features embedded with the big data platforms. You want developers to be able to enable features as needed during the design and deployment phases. You want security to be just as scalable, high-performance and self-organizing as the clusters are. The problem is the security products available aren't typically included with open source systems or the majority of commercial bundles.

To find out more about the key security components behind big data -- and for a list of myths about big data, as well as seven key tips on security it -- download the free report on big data security.

Have a comment on this story? Please click "Add a Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. 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


Recommended Reading:

Comment  | 
Print  | 
More Insights
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/28/2020
Stay-at-Home Orders Coincide With Massive DNS Surge
Robert Lemos, Contributing Writer,  5/27/2020
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win a Starbucks Card! Click Here
Latest Comment: Can you smell me now?
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2020-05-29
There is an Incorrect Authorization vulnerability in Micro Focus Service Management Automation (SMA) product affecting version 2018.05 to 2020.02. The vulnerability could be exploited to provide unauthorized access to the Container Deployment Foundation.
PUBLISHED: 2020-05-29
A Denial of Service vulnerability in MuleSoft Mule CE/EE 3.8.x, 3.9.x, and 4.x released before April 7, 2020, could allow remote attackers to submit data which can lead to resource exhaustion.
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.72.2 are vulnerable to Arbitrary File Read. It allows arbitrary file reads for users who have access to Snyk's internal network by appending the URL with a fragment identifier and a whitelisted path e.g. `#package.json`
PUBLISHED: 2020-05-29
All versions of snyk-broker after 4.72.0 including and before 4.73.1 are vulnerable to Arbitrary File Read. It allows arbitrary file reads to users with access to Snyk's internal network of any files ending in the following extensions: yaml, yml or json.
PUBLISHED: 2020-05-29
All versions of snyk-broker before 4.73.1 are vulnerable to Information Exposure. It logs private keys if logging level is set to DEBUG.