Security

How do I limit access to specific events in one index?

ips_mandar
Builder

Hi,

I am using OMS add-on. I have one index with one host,source and source type.
Now I want to limit access to specific table like below:-
1. index=idx table=security-----------User1
2. index=idx table=info---------------User2

I am able to create a separate index, but that also causes it to reindex data as one user wants to view all data and not any specific events/table ..So what will be best way to achieve this?

0 Karma
1 Solution

FrankVl
Ultra Champion

You could do that by creating separate roles and setting Search Filters for each of those. But search filters based on search time extracted fields are basically not secure, as users have control over the search time extractions. See also: http://docs.splunk.com/Documentation/Splunk/latest/Security/Addandeditroles#Search_filter_format

In general the recommended way to segregate access is by putting data in separate indexes. If you have users that need to access all data, you can do two indexes named like: idx:security and idx:info and then the users that have access to both, can use index=idx*.

View solution in original post

FrankVl
Ultra Champion

You could do that by creating separate roles and setting Search Filters for each of those. But search filters based on search time extracted fields are basically not secure, as users have control over the search time extractions. See also: http://docs.splunk.com/Documentation/Splunk/latest/Security/Addandeditroles#Search_filter_format

In general the recommended way to segregate access is by putting data in separate indexes. If you have users that need to access all data, you can do two indexes named like: idx:security and idx:info and then the users that have access to both, can use index=idx*.

ips_mandar
Builder

thanks @FrankVl search filters are applicable to host source and sourcetype but not applicable to specific fields like in my case table=security also can you please elaborate about security isssue-" users have control over the search time extractions."

0 Karma

FrankVl
Ultra Champion

A user could create a knowledge object that overwrites the value of the table field, to get access to all the data.

0 Karma

ips_mandar
Builder

Thanks @FrankVI..last question can you please give one example about how can I get access to whole index by editing knowledge objects

0 Karma

FrankVl
Ultra Champion

If your search filter restricts access based on table=info. I can for instance define a calculated field table for that sourcetype, that just sets table=info, overwriting the actual value, which means the search filter will always match and return all the events, regardless of the original table value.

0 Karma

ips_mandar
Builder

Hi @FrankVI, my field name is $table and suppose one role have access to index=abc "$table"=info then what calculated fields (eval expression) give me access to all $table fieldvalues

0 Karma

FrankVl
Ultra Champion

Like I said: a user could define something like EVAL-$table = "info" , so the field always gets the "info" value (regardless of what was actually in the event). That way the filter will allow all events to go through.

0 Karma

ips_mandar
Builder

sorry if I misunderstand but how can user access $table="severity" if user has only access to $table="info"

0 Karma

FrankVl
Ultra Champion

$table="severity" is just a field extraction defined in Splunk (at search time) right. And those can be overruled by assigning another value to that field. So all the events get $table="info" and as a result the user has access to all the events.

0 Karma

ips_mandar
Builder

my bad I have given info just as sample value my actual value is azuredignostic
so one user has access to search string index=abc $table="azuredignostics" then how this user can access $table="Perf" data.
are you saying to create calculated fields? how can i achieve?
yes, $table is extracted at search time using kv_mode=json in props.conf

0 Karma

ips_mandar
Builder

i checked this link and it seems in calculated fields I have option host/source/sourcetype to make it as * but in my case I have only 1 host,1 source and 1 sourcetype so I am not able to override $table="azuredignostics"

0 Karma

493669
Super Champion

As per docs it seems I can write in search filters index=indexname table=security but can you please elaborate about security issue...
As from last 2 months i was having only one input which indexing all data without any filter and now the requirement come about limiting access so thinking to use search filters but first want to undersatnd about security issue..

0 Karma

inventsekar
Ultra Champion

i think you can edit the user1 user2 roles such a way that they have access to the respective tables.

0 Karma
Get Updates on the Splunk Community!

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...

What’s New in Splunk Security Essentials 3.8.0?

Splunk Security Essentials (SSE) is an app that can amplify the power of your existing Splunk Cloud Platform, ...

Let’s Get You Certified – Vegas-Style at .conf24

Are you ready to level up your Splunk game? Then, let’s get you certified live at .conf24 – our annual user ...