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/16/2011
11:49 AM
Adrian Lane
Adrian Lane
Commentary
50%
50%

Big Data And Bad Security

The rush to collect and mine big data leaves data security in the dust

Following my most previous post, I received some questions concerning data security and the adoption of NoSQL -- both as a platform and a service -- because many of the cloud providers harness "big data." My goal was to explain to DBAs what they should be aware of because NoSQL will be part of their lives, and they need to understand how it impacts security and operations. Based on the questions I received, there is some ambiguity regarding what's being provided by cloud providers, what's built into any given NoSQL engine, and what the application developer who harnesses NoSQL is responsible for. So let's backtrack a bit and go through the trends as I see them.

Every couple of years we get a new programming language or platform that alters the IT landscape -- a better presentation of content, better use of resources, easier-to-use systems, easier-to-build code, and so forth. Examples might be the Internet, Ruby, Java, birtualization -- and now it's the cloud, big data, and mobile. Simple, lightweight, low cost, and powerful are typical hallmarks of these new technologies, and the very reasons they gain rapid adoption. Soon thousands of developers jump on the proverbial bandwagon and start interesting new projects.

In a short time span, these projects gain acceptance because they provide value and service like never before. And companies get hooked on the value provided. Shortly after the point when we accept the new technology as both an enabler and differentiator for the business, we realize the rush to embrace cool, new technologies has left management and infrastructure far behind. Specifically, that means security -- as always -- comes after the fact.

NoSQL -- which is defined as nonrelational, distributed, and horizontally scalable data stores -- falls squarely into this category. It abandons the constraints of schemas and transactional consistency in favor of simple usage and massive scalability in terms of data storage and processing capabilities. It's a technology that can handle big data, storing more and being able to analyze the aggregate -- at a scale beyond the reach of relational databases.

But from a security standpoint, you're starting from scratch. By and large it is not built in. We are only a couple of years removed from a time when just a few developers were prototyping applications on obscure open-source data repositories. Now we have major firms advancing capabilities and providing the infrastructures to go with these databases. And with millions of mobile devices all feeding data back to providers that want near real-time analysis, demand will continue to grow.

If Hadoop and its various flavors did not have you convinced that Big Data was more than a fad, then Amazon's SimpleDB & Dynamo, Google's BigTable, Cassandra, and 100 other platforms should have. Now that Oracle has jumped into the NoSQL market with both feet, you should start seriously looking at NoSQL installations as something you will be managing, either in-house or in the cloud that augments your infrastructure.

Yes, I've heard the criticism in the database community that Oracle offering NoSQL was purely a marketing effort to slow the erosion of the core relational database business, but I don't think that's true. Big data is built around a different data storage model and a slightly different method of processing data. The concept of what constitutes a data center is being redefined by big data and cloud computing, and these vendors are all vying for customers' attention in this expanding market. So for you DBAs out there, start learning NoSQL because it's going to be around for a while.

But this is where it comes back to security because there isn't much available. Developers and IT managers will, once again, scramble to bolt security on after the fact. The few vendors that claim to provide NoSQL security have nothing more than "cloud-washed" marketing collateral to go with exactly the same product they have been selling for years.

We see some federated identity systems implemented with SAML, and environment security measures embedded with the cloud infrastructure. But there is no such thing as vulnerability assessment or database activity monitoring for NoSQL today. Label security is based on schema, which does not exist in NoSQL. Encryption can be problematic because the data and indices need to be in clear text for analysis, requiring application designers to augment security with masking, tokenization, and select use of encryption in the application layer. Audit trails are whatever the application developer built in, so they are both application-specific and limited in scope. Today, security is sparse, and it likely will be for several years.

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

 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/10/2020
Researcher Finds New Office Macro Attacks for MacOS
Curtis Franklin Jr., Senior Editor at Dark Reading,  8/7/2020
Healthcare Industry Sees Respite From Attacks in First Half of 2020
Robert Lemos, Contributing Writer,  8/13/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: It's a technique known as breaking out of the sandbox kids.
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-20383
PUBLISHED: 2020-08-13
ABBYY network license server in ABBYY FineReader 15 before Release 4 (aka 15.0.112.2130) allows escalation of privileges by local users via manipulations involving files and using symbolic links.
CVE-2020-24348
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, has an out-of-bounds read in njs_json_stringify_iterator in njs_json.c.
CVE-2020-24349
PUBLISHED: 2020-08-13
njs through 0.4.3, used in NGINX, allows control-flow hijack in njs_value_property in njs_value.c. NOTE: the vendor considers the issue to be "fluff" in the NGINX use case because there is no remote attack surface.
CVE-2020-7360
PUBLISHED: 2020-08-13
An Uncontrolled Search Path Element (CWE-427) vulnerability in SmartControl version 4.3.15 and versions released before April 15, 2020 may allow an authenticated user to escalate privileges by placing a specially crafted DLL file in the search path. This issue was fixed in version 1.0.7, which was r...
CVE-2020-24342
PUBLISHED: 2020-08-13
Lua through 5.4.0 allows a stack redzone cross in luaO_pushvfstring because a protection mechanism wrongly calls luaD_callnoyield twice in a row.