Splunk Search

How to restrict one group to see only 1 log file in Splunk

nls7010
Path Finder

I have the following from a client:
I was about to make is for a new AD group “Splunk_CAPS_CAS_Payments” so that they are restricted to data that come from the source logging files
//LOG_CAPS_CAS_PaymentEDMS//CAPS//CAS_IN_msg_prod.log and //LOG_CAS_CAPS_InvoiceGL//CAS//CAPS_IN_msg_prod.log

Is this possible?

These users would only be able to pull the logs from the one CAPS_IN_msg_prod.log. How can this be done?

0 Karma

richgalloway
SplunkTrust
SplunkTrust

The only reliable way to limit access to data is to put that data in a separate index and restrict access to that index. Let's call that index "caps_cas".
AD group "Splunk_CAPS_CAS_Payments" would have their own Splunk role, I'll call it "CAPS_CAS_Payments". That role would have access only to the caps_cas index.

---
If this reply helps you, Karma would be appreciated.
0 Karma

nls7010
Path Finder

Sorry, it's for both the log files.//LOG_CAPS_CAS_PaymentEDMS//CAPS//CAS_IN_msg_prod.log and //LOG_CAS_CAPS_InvoiceGL//CAS//CAPS_IN_msg_prod.log

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...