Security

select lookuptable based on role of the current user

FritzWittwer
Contributor

We have an app which is deployed for different user groups which are distinguished by different roles which gives them access to their indexes. The searches use an asterisk in the index specification so each user gets the data from the index to which he gets access based on his role.

We need the same functionality for lookups, e.g.

  • lookuptable_a (belongs role a)
  • lookuptable_b (belongs role b)

spl: index=* | lookup lookuptable_* ...

Depending on the users role either lookuptable_a or lookuptable_b should be used, but wild-carding of lookup-table-name is not supported

0 Karma

somesoni2
Revered Legend

Give this a try

1) Create a macro (read by everyone or by both role_a and role_b)
Name: getlookupname
content:

[| rest /services/authentication/current-context splunk_server=local | table roles | eval search=case(isnotnull(mvfind(roles,"role_a")),"lookuptable_a",isnotnull(mvfind(roles,"role_b")),"lookuptable_b") | table search ]

2) Change sharing permissions on the lookup tables so that lookuptable_a is only accessible by role_a. same for lookuptable_b.

Now your users can use that macro in place of lookup table like this

index=* | lookup `getgetlookupname` ...
0 Karma
Get Updates on the Splunk Community!

Build Scalable Security While Moving to Cloud - Guide From Clayton Homes

 Clayton Homes faced the increased challenge of strengthening their security posture as they went through ...

Mission Control | Explore the latest release of Splunk Mission Control (2.3)

We’re happy to announce the release of Mission Control 2.3 which includes several new and exciting features ...

Cloud Platform | Migrating your Splunk Cloud deployment to Python 3.7

Python 2.7, the last release of Python 2, reached End of Life back on January 1, 2020. As part of our larger ...