We have found that if an ACL in a WAT does not match the Elasticube table/column security field, it defaults to providing 'all data'. To avoid a potential human error where a table/column has been renamed, we would like the default position to be 'nothing'.
2 Comments
I'd like to see Sisense prioritise this as it could lead to one of their customers having a data breach at some point. Security should always default to no access rather than full access if there's a configuration error.
- Status changed:New IdeatoNeeds Votes & Comments
Hello CCherish ,
Thank you for submitting your idea!
I have brought this Idea to the product team and will post updates here as they are available.
One of the ways we prioritize development efforts is by community interest. I encourage other users to vote and comment on this suggestion. The more engagement an idea receives the higher the likelihood of it being considered for implementation.
Thank you for being a valuable part of our community!
