Get fresh updates from Hortonworks by email

Once a month, receive latest insights, trends, analytics information and knowledge of Big Data.

cta

Get Started

cloud

Ready to Get Started?

Download sandbox

How can we help you?

closeClose button
August 04, 2014
prev slideNext slide

Hadoop Summit Curated Content: Apache Hadoop Security

“Data is to information society what fuel was to the industrial economy: the critical resource powering the innovations that people rely on,” write Victor Mayer-Schönberger and Kenneth Cukier, in Big Data. Today, big data fuels and engenders innovation of new products and services, according to Forrester.

Just as countries’ fuel repositories need protection and security because they can come under attack, so do companies’ big data repositories. “Companies, markets, and countries are increasingly under attack from cyber-criminals. They need to get much better at protecting [and securing] themselves,” says Martin Giles, of the Economist.

Hence, comprehensive and coordinated security—at the perimeter as well as across all data access points—in the Hadoop Enterprise ecosystem is one of the paramount pillars and a core capability of the Hadoop Enterprise blueprint.

Screen Shot 2014-08-04 at 2.50.58 PM

All security administrators want this core capability administered centrally by placing security controls across an entire Hadoop cluster, from the perimeter down to the Hadoop stack. They want layered security controls that exercise the following:

  • Authentication—who (or what) is accessing data?
  • Authorization—what operations are allowed on data or whom can I trust?
  • Auditing or Accounting—when, where, who, or how data were accessed?
  • Data encryption—how data are ingested (in transit) and stored (at rest)?

These four mechanisms comprise the basic hygiene of comprehensive security, whether securing an entry point or accessing a data source.

Not having absolute control over these undesirable outcomes or not having proper security controls in place can easily become a huge problem—and can easily deprive security administrators and devops of their sleep.
As @DevOps_Borat sanguinely satirizes, you don’t want some rogue command or capricious code drop your schema, delete your HDFS directory, kill a MapReduce job, submit a malicious client to YARN, or query unauthorized sensitive data:

borat_security

Far from being sleepless or powerless against security breaches, security administrators can lock down their Hadoop clusters. The good news is that the Apache Hadoop community, through various Apache projects, shared best practices on how they address and manage complex security challenges at the Hadoop Summit.

Apache Hadoop Security—Curated Content

Although the Hadoop Summit San Jose 2014 has come and gone, the invaluable content is available here. We selected a few sessions below for Hadoop security administrators, curating them under a general Hadoop security theme. Here are a few sessions that speak to security challenges:

Session Title Watch View
Improvements in Hadoop Security Video Slides
Hadoop REST API Security with the Apache Knox Gateway Video Slides
Using Hadoop and Machine Learning to Detect Security Risks and Vulnerabilities, and Predict Breaches in your Enterprise Environment Video Slides
The Future of Hadoop Security Video Slides

We cherry picked these few tracks that best addressed those topics, but you can always peruse through all the tracks on the schedule’s session description along any time slot, on any day, that piques your curiosity. session




For example, when you hover and click on a session description, a popup will display in which you can either elect to watch the video or view the slides.

Discover and Learn More

Tags:

Leave a Reply

Your email address will not be published. Required fields are marked *

If you have specific technical questions, please post them in the Forums

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>