Securing Analysis Services includes maintaining a secure environment and following all best practices for system security. This page provides links to help you locate the information that you need in order to more securely operate and manage your Analysis Services environment.
Provides a general overview of the steps required to protect the Analysis Services objects (such as databases, dimensions, cubes, data mining models, etc.), and to make sure that only authorized users have permission to access them.
The communication stream between clients and an instance of Microsoft SQL Server Analysis Services must be secured. During the setup process, default security settings are configured that control this communications stream. The default security settings try to guarantee that communication between clients and an instance of Analysis Services is as secure as possible. However, depending on the sensitivity of the data and the security of the networks across which the data is accessed, these default security settings might not be suitable for you. This topic describes how to configure the communications to suit your needs.
In Microsoft SQL Server, members of the server role for SQL Server Analysis Services can create one or more database roles within a database. They can then grant full or limited administrative permissions within the database to these database roles. Finally, they can then add Microsoft Windows users and groups to these database roles.
User access to objects such as cubes, dimensions, and mining models within an instance of Microsoft SQL Server Analysis Services is granted through membership in one or more database roles. Analysis Services administrators create these database roles, grant read or read/write permissions on Analysis Services objects for these roles, and then add Microsoft Windows users and groups to the roles.