Splunk Enterprise

Need help locking down SH app

fnetechnology
Engager

Hello, need a quick help... I am working on locking down one of my Splunk applications. I do not want any user/power user roles able to make any changes in the UI to any Knowledge Objects... I would rather have the code checked in SVN (Subversion) and not directly on the UI... Any suggestions would be great! Thank you.

Labels (2)
0 Karma

venkatasri
SplunkTrust
SplunkTrust

Hi @fnetechnology

default.meta is the right file to control Access to Knowledge Objects, Follow below link and set read-only permissions to Object_types  (aka Knowledge Object)  that your app contains.

Set permissions using RBAC | Documentation | Splunk Developer Program

-----------------------------------------------------

An upvote would be appreciated if it helps!

fnetechnology
Engager

Thank you! 

0 Karma

isoutamo
SplunkTrust
SplunkTrust
Please remember that this mach only those versions which are shared as app or globally. If those persons have own version (clones) they can use those as earlier.
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...