• Glossary
  • Support
  • Downloads
  • DataStax Home
Get Live Help
Expand All
Collapse All

DataStax Enterprise 6.8 Security Guide

    • About DSE Advanced Security
    • Security FAQs
    • Security checklists
    • Securing the environment
      • Securing ports
      • Securing the TMP directory
    • Authentication and authorization
      • Configuring authentication and authorization
        • About DSE Unified Authentication
          • Steps for new deployment
          • Steps for production environments
        • Configuring security keyspaces
        • Setting up Kerberos
          • Kerberos guidelines
          • Enabling JCE Unlimited
            • Removing AES-256
          • Preparing DSE nodes for Kerberos
            • DNS and NTP
            • krb5.conf
            • Principal
            • Keytab
        • Enabling authentication and authorization
          • Defining a Kerberos scheme
          • Defining an LDAP scheme
        • Configuring JMX authentication
        • Configuring cache settings
        • Securing schema information
      • Managing database access
        • About RBAC
        • Setting up logins and users
          • Adding a superuser login
          • Adding database users
          • LDAP users and groups
            • LDAP logins
            • LDAP groups
          • Kerberos principal logins
          • Setting up roles for applications
          • Binding a role to an authentication scheme
        • Assigning permissions
          • Database object permissions
            • Data resources
            • Functions and aggregate resources
            • Search indexes
            • Roles
            • Proxy login and execute
            • Authentication schemes
            • DSE Utilities (MBeans)
            • Analytic applications
            • Remote procedure calls
          • Separation of duties
          • Keyspaces and tables
          • Row Level Access Control (RLAC)
          • Search index permissions
          • DataStax Graph keyspace
          • Spark application permissions
          • DataStax Studio permissions
          • Remote procedure calls
          • DSE client-tool spark
          • JMX MBean permissions
          • Deny (denylist) db object permission
          • Restricting access to data
      • Providing credentials from DSE tools
        • About clients
        • Internal and LDAP authentication
          • Command line
          • File
          • Environment variables
          • Using CQLSH
        • Kerberos
          • JAAS configuration file location
          • Keytab
          • Ticket Cache
          • Spark jobs
          • SSTableLoader
          • Graph and gremlin-console
          • dsetool
          • CQLSH
        • Nodetool
        • JConsole
    • Auditing database activity
      • Enabling database auditing
      • Capturing DSE Search HTTP requests
      • Log formats
      • View events from DSE audit table
    • Transparent data encryption
      • About Transparent Data Encryption
      • Configuring local encryption
        • Setting up local encryption keys
        • Encrypting configuration file properties
        • Encrypting system resources
        • Encrypting tables
        • Rekeying existing data
        • Using tools with TDE-encrypted SSTables
        • Troubleshooting encryption key errors
      • Configuring KMIP encryption
      • Encrypting Search indexes
        • Encrypting new Search indexes
        • Encrypting existing Search indexes
        • Tuning encrypted Search indexes
      • Migrating encrypted tables from earlier versions
      • Bulk loading data between TDE-enabled clusters
    • Configuring SSL
      • Steps for configuring SSL
      • Creating SSL certificates, keystores, and truststores
        • Remote keystore provider
        • Local keystore files
      • Securing node-to-node connections
      • Securing client-to-node connections
        • Configuring JMX on the server side
        • nodetool, nodesync, dsetool, and Advanced Replication
        • JConsole (JMX)
        • SSTableloader
        • Connecting to SSL-enabled nodes using cqlsh
      • Enabling SSL encryption for DSEFS
      • Reference: SSL instruction variables
    • Securing Spark connections
  • DataStax Enterprise 6.8 Security Guide
  • Authentication and authorization
  • Managing database access
  • Assigning permissions
  • DataStax Studio permissions

Controlling Access to DataStax Studio

Assign access privileges to roles for DataStax Studio management.

Permissions and syntax

Setting access to DataStax Studio using the following syntax:

  • Allow access for DataStax Studio use:

    GRANT <permission_name>
    ON <keyspace_name>.<table_name>
    TO <role_name>;
  • Remove access to DataStax Studio use:

    REVOKE <permission_name>
    ON <keyspace_name>.<table_name>
    FROM <role_name>;
Table 1. Studio permissions
permission_name CQL command Description

SELECT

GRANT, and REVOKE

Perform select operations for CQL and Graph commands in Studio.

EXECUTE

GRANT and REVOKE

Perform execute operations for REMOTE OBJECT DseClientTool.

PROXY.EXECUTE

GRANT, and REVOKE

Permission to execute AlwaysOn Spark SQL (AOSS) in Studio.

Requirements to GRANT/REVOKE Studio permissions

Roles that manage Studio permissions must have AUTHORIZE on the Studio resources:

  • Manage permissions for all search indexes:

    GRANT AUTHORIZE FOR <permission_name>
    ON KEYSPACE <required_keyspaces>
    TO <role_name>;
  • Limit permissions to manage permissions to individual tables:

    GRANT AUTHORIZE FOR <permission_name>
    ON <required_keyspaces>
    TO <role_name>;

Superuser roles have permission to perform any action and therefore do not require explicitly granting authorize permission on Studio resources.

Procedure

  • A Studio user must have the following SELECT permissions:

    GRANT SELECT ON system_auth.roles to <studio_role>;

    This permission allows validation of the CQL role settings for <studio_role>.

  • A Studio user must have the following SELECT permissions to access DataStax Graph schema views:

    GRANT SELECT ON system_schema.vertices to <studio_role>;
    GRANT SELECT ON system_schema.edges to <studio_role>;

    These permissions are available by default, unless the system_schema keyspace has had permissions altered.

  • If DSE Search is used for any data in Studio, the following permission is required to access the search resources and display search indexes:

    GRANT SELECT ON solr_admin.solr_resources to <studio_role>;
  • The following permissions are required if AlwaysOn SparkSQL is used in Studio, to determine AOSS status, display SparkSQL cached tables in the schema view, identify the current datacenter for the SparkSQL-cached tables, and identify DataStax Graph and AOSS host servers:

    GRANT SELECT ON dse_analytics.alwayson_sql_info to <studio_role>;
    GRANT SELECT ON dse_analytics.alwayson_cache_table to <studio_role>;
    GRANT SELECT ON system.local to <studio_role>;

    Permissions to system.local are available by default, but the role may need permission granted.

  • Additional permissions required if AlwaysOn Spark SQL is used in Studio identify the current datacenter for the SparkSQL-cached tables, and identify DataStax Graph and AOSS host servers:

    GRANT EXECUTE ON REMOTE OBJECT DseClientTool to <studio_role>;
  • Lastly, SparkSQL queries do not execute and no error is displayed if this last permission is not set:

    GRANT PROXY.EXECUTE ON ROLE <studio_role> TO alwayson_sql;
Spark application permissions Remote procedure calls

General Inquiries: +1 (650) 389-6000 info@datastax.com

© DataStax | Privacy policy | Terms of use

DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.

Kubernetes is the registered trademark of the Linux Foundation.

landing_page landingpage