Application Security // Database Security
9/24/2013
01:50 PM
Adrian Lane
Adrian Lane
Commentary
Connect Directly
RSS
E-Mail
50%
50%

The Big Data Is The New Normal

Big data, not relational, is the new platform of choice

I get a lot of questions on big data. What is it? How are people using it? How do you secure it? How do I leverage it? I've been on the phone with three different journalists in the past couple of weeks talking about what security analytics with big data really means. Be it journalists, security professionals, IT, or management, big data is relatively new to the mainstream practitioner, so the questions are not particularly surprising.

What is surprising is just about every new database installation or project I hear about sits atop a big data foundation. The projects focus on data, looking at new ways to mine data for interesting information. From retail-buying trends, to weather analysis, to security intelligence, these platforms are the direction the market is heading. And it's because you can Hadoop. Cassandra. Mongo. Whatever. And it's developer-driven -- not IT or DBA or security. Developers and information architects specify the data management engine during their design phase. They are in the driver's seat. They are the new "buying center" for database security products.

Since the bulk of the questions I get are now focused on big data, I am going to begin shifting coverage a bit to cover more big data topics and trends. And I'll spend some time addressing the questions I am getting about security and uses for big data. Yes, I will continue coverage of interesting relational security as I get questions or new trends develop, but because most of you are asking about big data, I'm going to rebalance coverage accordingly.

And to kick it off, today I want to address a specific, critical point: Big data is all about databases. But rather than a "relational" database, which has a small number of defining characteristics, these databases come in lots of different configurations, each assembled to address a specific use case. Calling this trend "big data" is even a disservice to the movement that is under way. The size of the data set is about the least interesting aspect of these platforms. It's time to stop thinking about big data as big data and start looking at these platforms as the next logical step in data management.

What we call "big data" is really a building-block approach to databases. Rather than the prepackaged relational systems we have grown accustomed to during the past two decades, we now assemble different pieces (data management, data storage, orchestration, etc.) together in order to fit specific requirements. These platforms, in dozens of different flavors, have more than proved their worth and no longer need to escape the shadow of relational platforms. It's time to simply think of big data as modular databases.

The key here is that these databases are fully customizable to meet different needs. Developers for the past decade have been starting with relational and then stripping it of unneeded parts and tweaking it to get it to work the way they want it. Part of MySQL's appeal in the development community was the ability to change some parts to suit the use case, but it was still kludgy. With big data it's pretty much game on for pure customization. Storage model, data model, task management, data access, and orchestration are all variable. Want a different query engine? No problem, you can run SQL and non-SQL queries on the same data. It's just how you bundle it. Hadoop and Cassandra come with "stock" groupings of features, but most developers I speak with "roll-their-own" infrastructure to suit their use case.

But just as importantly, they work! This is not a fad. These platforms are not going away. It is not always easy to describe what these modular databases look like, as they are as variable as the applications that use them, but they have a set of common characteristics. And one of those characteristics, as of this writing, is the lack of security. I'll be going into a lot more detail in the coming weeks. Till then, call them modular databases or database 3.0 or whatever -- just understand that "NoSQL" and "Big Data" fail to capture what's going on.

Adrian Lane is an analyst/CTO with Securosis LLC, an independent security analyst firm. 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
TechGuy1313
50%
50%
TechGuy1313,
User Rank: Apprentice
9/27/2013 | 8:45:38 PM
re: The Big Data Is The New Normal
Thanks, Adrian.

The term Big Data is so often bandied about rendering into buzzword Hall of Fame territory. I find that so many focus on the "Big" part of the phrase and don't consider the "4 Vs" if you will (Volume, Velocity, Variety, and Veracity) as a whole.

Wanted to share real quick a video (http://www.youtube.com/watch?v... I saw that not only speaks to IT's role in Big Data initiatives G«Ű but also delivers it via at least 8 sci-fi references. The video is based of research but talks more about ways to approach and plan for new large data projects.
Ulf Mattsson
50%
50%
Ulf Mattsson,
User Rank: Apprentice
9/26/2013 | 9:58:21 PM
re: The Big Data Is The New Normal
As the article mentions, there is currently a lack of G«£stockG«• security in big data
platforms.

However, although inherent security is lacking, security vendors now provide many
options to protect big data, from coarse grained approaches, such as volume or
file encryption, to fine grained methods such as masking and Vaultless Tokenization. Much in the same way that the platforms themselves can be assembled in different configurations, each security approach may have particular usefulness for a particular customized big data model. For example, in a storage model, you may only require coarse grained security, while a data access model may require very fine grained security with options to expose business intelligence.

Obviously, in cases such as the ones the article describes with G«£roll-their-ownG«•
infrastructure, itG«÷s necessary to consider that each G«£building blockG«• may require a different security method, in order to ensure that the data is protected throughout the environment, and not just in one or two of the components. This can, and does, create issues where developers fail to consider (or are not realistically able to foresee) what may be coming down the road in this exploding new field. So for many, it is difficult to reconcile this building block database with comprehensive data security, and this most likely plays a large part in why security has thus far been lacking.

But despite the lack of G«£stockG«• security in big data environments, there is hope.
Data security vendors have been keen to develop new solutions to meet these
challenges, and continue to innovate along with this exciting, and ever-expanding new platform. IG«÷m sure Adrian will have plenty to say on this subject in the coming weeks.

Ulf Mattsson, CTO Protegrity
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-4262
Published: 2014-07-28
svnwcsub.py in Subversion 1.8.0 before 1.8.3, when using the --pidfile option and running in foreground mode, allows local users to gain privileges via a symlink attack on the pid file. NOTE: this issue was SPLIT due to different affected versions (ADT3). The irkerbridge.py issue is covered by CVE-...

CVE-2013-4840
Published: 2014-07-28
Unspecified vulnerability in HP and H3C VPN Firewall Module products SECPATH1000FE before 5.20.R3177 and SECBLADEFW before 5.20.R3177 allows remote attackers to cause a denial of service via unknown vectors.

CVE-2013-7393
Published: 2014-07-28
The daemonize.py module in Subversion 1.8.0 before 1.8.2 allows local users to gain privileges via a symlink attack on the pid file created for (1) svnwcsub.py or (2) irkerbridge.py when the --pidfile option is used. NOTE: this issue was SPLIT from CVE-2013-4262 based on different affected versions...

CVE-2014-2974
Published: 2014-07-28
Cross-site request forgery (CSRF) vulnerability in php/user_account.php in Silver Peak VX through 6.2.4 allows remote attackers to hijack the authentication of administrators for requests that create administrative accounts.

CVE-2014-2975
Published: 2014-07-28
Cross-site scripting (XSS) vulnerability in php/user_account.php in Silver Peak VX before 6.2.4 allows remote attackers to inject arbitrary web script or HTML via the user_id parameter.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Sara Peters hosts a conversation on Botnets and those who fight them.