Troubleshoot messages about unnecessary read or write access to investigation KV Store collections
Issue
Display of Splunk Web messages about roles that have unnecessary read or write access to the investigation KV store collections. You might see the following error messages in Splunk Web:
Health Check: Review roles for unnecessary read or write access to the investigation_attachment collection and remove access if possible
Health Check: Review roles for unnecessary read or write access to the investigation_event collection and remove access if possible
Health Check: Review roles for unnecessary read or write access to the investigative_canvas_entries collection and remove access if possible
Health Check: Review roles for unnecessary read or write access to the files collection and remove access if possible
Health Check: Review roles for unnecessary read or write access to the investigation collection and remove access if possible
Health Check: Review roles for unnecessary read or write access to the investigative_canvas collection and remove access if possible
Cause
These messages are produced by the Audit - Investigation Collection ACLs
saved search. The search looks for non-admin permissions to the investigation KV store collections.
Solution
Remove the unnecessary read or write access from the collections. If you see these messages, remove the corresponding [collections/<stanza_name>]
collections from $SPLUNK_HOME/etc/apps/SplunkEnterpriseSecuritySuite/metadata/local.meta
. Access to these collections by non-admin roles is not recommended. After making the changes, refresh the file cache from Splunk Web: http://<yoursplunkserver>:8000/en-us/debug/refresh?
.
In a search head cluster environment, make these changes to the local.meta
file on each member in the cluster, via the deployer if applicable. Then refresh the file cache from Splunk Web for each search head: http://<yoursplunkserver>:8000/en-us/debug/refresh?
. Alternately, if there are more than a few members in the cluster, a rolling restart can be used instead of the debug/refresh command.
Troubleshoot messages about default indexes searched by the admin role in Splunk Enterprise Security | Troubleshoot failed intelligence downloads in Splunk Enterprise Security |
This documentation applies to the following versions of Splunk® Enterprise Security: 8.0.0
Feedback submitted, thanks!