The race for dominance in the Hadoop security market niche is definitively on. Vendors of popular distributions and of security add-ons have started to recognize that clients long for a harmonized approach to Hadoop security that will make controls that are at first specific to the resource effective across a majority of Hadoop components. Two possible routes to this are the extension of the Apache Sentry or the adoption of a XACML-style authorization language. The market currently also argues about the right demarcation point for the security of your data in Hadoop: Will the Hadoop distribution eventually take care of the vast majority of security requirements, or will this become the domain of add-ons similar to the market for database audit and protection tools? And if the Hadoop security market niche is not absorbed by the bigger distributions, will the add-ons eventually also provide security for plain vanilla Hadoop that is part of some Linux distributions but has none of the features of the established Hadoop distributions?
My research note “Protecting Big Data in Hadoop” helps you navigating the lands of big data security and gives you guidance on how to use your choices wisely and what controls and add-ons to put on your pick list.
P.S. Access requires Gartner GTP subscription.
Read Complimentary Relevant Research
100 Data and Analytics Predictions Through 2021
Over the next few years, data and analytics programs will become even more mission-critical throughout the business and across industries....
View Relevant Webinars
Digital Business Architecture: From Strategy to Guiding Execution
New techniques have emerged to help CIOs and EA practitioners leverage business architecture to guide investment and execution decisions,...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.