[/map
{"- map/map "})
[/map/title
{"- topic/title "}) DataSetSecurity_unit (title][/map/topicref
{"- map/topicref "}) [/map/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Data Set Security (navtitle][/map/topicref/topicmeta/linktext
{"- map/linktext "}) Data Set Security (linktext][/map/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) This section describes options for securing your data sets. (shortdesc] (topicmeta][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Sentry (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Sentry (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) Sentry is a Hadoop component that provides role-based authorization in a Hadoop cluster. Among other things, it can be used to restrict access to Hive data at a granular level. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) HDFS data at rest encryption (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) HDFS data at rest encryption (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) HDFS data at rest encryption allows HDFS data to be stored in encrypted directories called encryption zones. All files within an encryption zone are transparently encrypted and decrypted on the client side, meaning decrypted data is never stored in HDFS. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Data set whitelists and blacklists (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Data set whitelists and blacklists (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) BDD whitelists and blacklists control which Hive tables are processed by the DP CLI. Whitelists specify tables that should be processed and blacklists specify tables that should be ignored. Only tables that have been processed are available to BDD and its users. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) User roles (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) User roles (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) Studio users are assigned application-wide roles that determine which parts of the application they can access and the data they can view. Studio administrators can assign and modify user roles. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Project roles (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Project roles (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) In Studio, project roles determine which users can access project data and configuration. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Project types (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Project types (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) In Studio, a project's type determines which users can access it. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Data set permissions (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Data set permissions (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) Default access to data sets in Studio is determined by how they're created. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Custom transform scripts and visualizations (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Custom transform scripts and visualizations (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) Studio enables users to create custom visualizations and transform scripts, which require them to do some coding. In these cases, special security measures have been implemented to prevent users from accessing sensitive data. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref
{"- map/topicref "}) [/map/topicref/topicref/topicmeta
{"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle
{"- topic/navtitle "}) Security Manager (navtitle][/map/topicref/topicref/topicmeta/linktext
{"- map/linktext "}) Security Manager (linktext][/map/topicref/topicref/topicmeta/shortdesc
{"- map/shortdesc "}) The Security Manager is a Studio feature that filters the data that users can see in Studio. If you want to provide extra security for Studio, you can use the Component SDK to create a custom Security Manager to restrict access to specific data. (shortdesc] (topicmeta] (topicref] (topicref]
(map]