Security

Force tags to be public upon creation

Jason
Motivator

We have a review process set up in Splunk where multiple end users log in and tag individual events. These tags MUST be public by default so other users will not duplicate work. Forcing each user to go into manager and make all their tags public is not acceptable - it is way too much work for hundreds of review items every day.

What options do I have for forcing all tags to be public (app-level) upon creation?

Tags (2)

ziegfried
Influencer

It's possible by influencing the UI Javascript. But that's a rather sophisticated customization.

Jason
Motivator

Ok, I sent you an email.

0 Karma

ziegfried
Influencer

Yes, I've done it in the past. But this is a little too extensive to be described here. Essentially it's modifying the behavior of the EventsViewer module using a custom application.js.

0 Karma

Jason
Motivator

Do you know how to do it?

0 Karma

Jason
Motivator

Symbolic AND hard links don't work, Splunk appears to remove the file before rewriting it. It appears Linux does not have the ability to allow write but disallow delete of the one tags.conf file in etc/users/username/appname/local while allowing updating of the other files.

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...