|
Data elements level Security
The user access matrix should be able to manage access to the views and reports. It should also be able to restrict view on the given dimension, attribute and measure. For example a user A can be allowed to see the Sales monthly scorecard, but is allowed to view the Sales figures for only institutional products and that also for the northern region.
Time of access
A user is disallowed a certain window of usage, to ensure that any query load is distributed. This is also done to ensure that a user is not firing queries for today, while the Data Warehouse refresh is still in progress.
Functions & Procedures
A user access matrix to control on which custom OR pre-built procedures OR functions one can use. This is typically done to manage the kind of queries one can fire.
Operational access
Typically only power users are allowed to define the scheduling and distribution flow for the reports.
User ID vs. user role
A good OLAP tool will have a user role based matrix, where each user can be mapped to a single OR multiple sets of user roles (sometimes called profile as well). This means that the access matrix is defined for 'Sales managers in Northern region' role. If a John Smith is mapped to this role, he will automatically be given the access matrix of the given role. This feature is needed to handle any large system with large set of users.
Support for Digital Certificates and Encryption
This feature is used, when the distribution of data is over wide area networks OR public networks.
Integration with an external security model like LDAP, to enable a single sign-on.
|
