Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started

Reply
ovonel
Post Prodigy
Post Prodigy

Is hiding tables enough to prevent access?

I have a typical fact table with dimensions Project, Profit Center, etc

 

In a report, I have a table visual that shows individual numbers; and another table shows the department numbers…

 

It looks something like this:

ovonel_0-1672221542865.png

(Left: personal numbers. Right: department numbers)

 

 

 

My goal is that Tim shouldn’t be able to see someone else’s number, but he definitely can (and should) see the aggregated numbers for his department.

 

I realized that someone accessing from PowerBI or excel can connect to the model and play with the tables, pick another name and see someone else’s number, therefore I have hidden most tables...

 

But now, I just realized, someone with access can connect from Visual Studio to the SSAS:

ovonel_1-1672221573918.png

 

 

 

 

 

The person can open the .bim, unhide all tables, and with the “analyze from excel” option in VS see any numbers…

 

Is there any way to avoid/prevent this?

 

More info:

My model:

ovonel_2-1672221602526.png

(Project table has columns Lead1,Lead2,Lead3,Lead4,Lead5 and Lead6… Engagement Role is just an unpivot of this).

 

 

On my left visual I have:

ovonel_3-1672221622726.png

 

(triggering a more restrictive access).

 

 

My RLS:

ovonel_4-1672221647794.png

 

 

1 ACCEPTED SOLUTION
Greg_Deckler
Super User
Super User

@ovonel Hiding tables is not a security thing, it is a convenience to make self-service BI a better experience. Hiding tables affords no real security. RLS and OLS are the only real security features. Typically, your type of scenario is done using dynamic RLS where you tie the RLS rules to the user's USERPRINCIPALNAME. The aggregations are stored in a separate table that does not enforce RLS.


Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
The Definitive Guide to Power Query (M)

DAX is easy, CALCULATE makes DAX hard...

View solution in original post

1 REPLY 1
Greg_Deckler
Super User
Super User

@ovonel Hiding tables is not a security thing, it is a convenience to make self-service BI a better experience. Hiding tables affords no real security. RLS and OLS are the only real security features. Typically, your type of scenario is done using dynamic RLS where you tie the RLS rules to the user's USERPRINCIPALNAME. The aggregations are stored in a separate table that does not enforce RLS.


Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
The Definitive Guide to Power Query (M)

DAX is easy, CALCULATE makes DAX hard...

Helpful resources

Announcements
July 2024 Power BI Update

Power BI Monthly Update - July 2024

Check out the July 2024 Power BI update to learn about new features.

PBI_Carousel_NL_June

Fabric Community Update - June 2024

Get the latest Fabric updates from Build 2024, key Skills Challenge voucher deadlines, top blogs, forum posts, and product ideas.

Top Solution Authors