__data-level-security-2-image-unique-image-unique

__data-level security

This solution consists of three components:
<ol>
<li>Client side plugin &#8211; applies security for the Sisense application.</li>
<li>Server side plugin &#8211; applies security for the Sisense API.</li>
<li>External plugin &#8211; adds REST API for &#8216;Column Level Security&#8217;.</li>
</ol>
<h3>Installation</h3>
<ol>
<li>Extract the .zip folder.</li>
<li>Install the client-side component: 
Place the ./Plugin/columnLevelSecurity folder in /opt/sisense/storage/plugins/.
<ul>
<li>If the folder does not exist, create it.</li>
</ul>
</li>
<li>Install the external-plugin component: 
Place the external-plugin folder ./Plugin/columnLevelSecurityMicroservice/src/features/columnLevelSecurity into /opt/sisense/storage/external-plugins/apiPlugins/plugins/.
<ul>
<li>If the folder does not exist, create it.</li>
</ul>
</li>
<li>Restart external-plugins pod to apply configuration changes.</li>
<li>Install the server-side plugin component:
<ol>
<li>Open the <a href="https://documentation.sisense.com/latest/administration/system-settings/configmgr_linux.htm#gsc.tab=0">Configuration Manager page</a>.</li>
<li>Scroll to the bottom of the page and click  Show Advanced. 
<img loading="lazy" class="alignnone" src="https://cdn.sisense.com/wp-content/uploads/2021-01-14_15h55_14-1.png" alt="" width="1234" height="1203" /></li>
<li>Expand the Server Side Plugins section and enable the server-side plugins. 
<img loading="lazy" class="alignnone" src="https://cdn.sisense.com/wp-content/uploads/2021-01-14_15h57_36-1.png" alt="" width="980" height="447" /></li>
<li>Click Save.</li>
<li>Copy folder ./Plugin/columnLevelSecurityInterceptors to /opt/sisense/storage/serverSidePlugins.</li>
</ol>
</li>
<li>Restart the Api-gateway pod and the External-plugins pod.</li>
</ol>
<h3>Managing Column-Level Security Rules</h3>
Managing the column-level security rules is done using column-security REST APIs that can be found on the REST API page:
<img loading="lazy" class="alignnone" src="https://cdn.sisense.com/wp-content/uploads/2021-01-13_17h17_39-1.png" alt="" width="2560" height="1262" />
To add new column-security rules, use the POST /columnsecurity endpoint.
<h4>Column-level Security Rule Structure</h4>
<img loading="lazy" class="alignnone" src="https://cdn.sisense.com/wp-content/uploads/2021-01-13_17h20_52.png" alt="" width="479" height="479" />
Rule parameters:
<ul>
<li>cube &#8211; full path of the ElastiCube in format /</li>
<li>dim &#8211; full sensitive dimension name that the rule is applied on. Format: “[ 
.]”</li>
<li>replaceWith &#8211; If specified, the sensitive dimension is replaced by this dimension. Format: “[ 
.]”Notes: The sensitive column has to have a one-to-one relationship with the replacing column.</li>
<li>shares &#8211; array. Users/groups affected by the rule.
<ul>
<li>id &#8211; User/group ID</li>
<li>type &#8211; Type of the share: &#8216;user&#8217; or &#8216;group&#8217;</li>
<li>allowOnDashboard &#8211; boolean. If set to true, the sensitive dimension is hidden or replaced only on export to CSV/Excel and not on the dashboard level</li>
</ul>
</li>
<li>excluded &#8211; array. Users/groups permitted to view the column on export and on dashboard view
<ul>
<li>id &#8211; User/group ID</li>
<li>type &#8211; type of the share: &#8216;user&#8217; or &#8216;group&#8217;</li>
</ul>
</li>
<li>everyoneElse &#8211; default security rule for users that are not in the shares nor in the excluded lists</li>
</ul>
Example:
<pre>{

 "cube": "LocalHost/Sample ECommerce",

 "dim": "[Category.Category]",

 "replaceWith" : "[Category.Category ID]",

 "shares" : [

 {

 "id" : "5c8a85f40bd0266fa8344bf0",

 "type" : "user",

 "allowOnDashboard" : true

 }

 ],

 "everyoneElse" : {

 "allowOnDashboard" : false

 },

 "excluded" : [
 {

 "id" : "5c8a85f40bd0266fa8344bf1",

 "type" : "user"

 }

 ]

}
</pre>
Note: By default, the plugin only replaces columns and does not hide them. To enable hide columns, use the POST /columnsecurity/settings endpoint.
<img loading="lazy" class="alignnone" src="https://cdn.sisense.com/wp-content/uploads/2021-01-13_17h35_38-1.png" alt="" width="957" height="628" />
This setting is global, affecting all the column-level security configuration entries. 
In case the ‘allowHideColumn’ is set to false, all the rules that do not include the replaceWith property are not active until they are updated.
Security rules can make permanent changes to dashboards and widgets in specific cases. Some changes cannot be reverted. Examples:
<ol>
<li>Dashboard filters:
<ul>
<li>Column replacement rules can cause duplications on dashboard filters. In this case, the dashboard filter field will be removed and cannot be replaced. If the duplicated field is part of the cascading filter, the cascading filter is removed completely.</li>
<li>If the replacing field has a different type than the original field, any type-related configurations (such as level configuration for date field) will be removed.</li>
</ul>
</li>
<li>Drill to: 
If a restricted dimension is used in a drill, the widget will be drilled up to the nearest unrestricted dimension.</li>
<li>Restore dashboard when hidden rules became obsolete.
<ul>
<li>Logged in as the dashboard owner: 
Hidden widget fields/filters are permanently removed from the widget in case the widget is re-saved. 
Once the widget is saved without the hidden fields, no changes made to the security rules will add the columns again.</li>
<li>Hidden dashboard filters are permanently removed in case a user adds an additional filter to the dashboard. No changes made to the security rules will add the filters again.</li>
</ul>
</li>
<li>Duplicating a widget: 
When duplicating a widget that contains a sensitive column, the duplicated widget is duplicated as presented to the user &#8211; without the hidden column or with the replacement column.</li>
<li>Formulas: 
If a measure of type formula contains a hidden sensitive column, the measure will be hidden completely.</li>
</ol>
<h3>Limitations</h3>
<ul>
<li>Table and column names can&#8217;t contain the ‘.’ symbol.</li>
<li>If cascading filters have restricted dimensions, all levels below are hidden.</li>
</ul>

Data Security

data security

HIPAA

<h3>Overview</h3>
Using the Column Level Security you can apply data security rules on the column level. Sensitive columns can be configured to be either replaced by another column or completely hidden.
Each column can be configured to be hidden or replaced on export to CSV/Excel only, or on the dashboard level as well.
Note: This add-on does not support exporting to PDF and exporting a widget as an image.
<h4>Use Case</h4>
A hospital is interested in analyzing procedure waiting time. For each procedure, the collected data includes the procedure information, waiting time, and patient information. A unique identifier is set for each patient as well.
As required by the Health Insurance Portability and Accountability Act (HIPAA), sensitive personally identifiable information (PII) must be encrypted to prevent it from harming individuals should a data breach occur.
Using the Column Level Security add-on, all columns that are considered PII can be replaced with the patient’s unique identifier, or they can be completely hidden.

Get the Add-on

Leave Feedback