Turn off Splunk platform field filters
READ THIS FIRST: Should you deploy field filters in your organization?
Field filters are a powerful tool that can help many organizations protect their sensitive fields from prying eyes, but it might not be a good fit for everyone. If your organization runs Splunk Enterprise Security or if your users rely heavily on commands that field filters restricts by default (mpreview
, mstats
, tstats
, typeahead
, and walklex
), do not use field filters in production until you have thoroughly planned how you will work around these restricted commands. See READ THIS: Restricted commands do not work in searches on indexes that have field filters.
How to turn off Splunk platform field filters
At some point you might want to turn off all of your organization's field filters at one time. When you turn off field filters, the Splunk platform doesn't apply existing field filters to searches and ignores configuration information, such as role exemptions, target indexes, and limits on target hosts, sources, and source types. In addition, personal identifiable information (PII) and protected health information (PHI) data might be visible in searches when you turn off field filters.
You can turn field filters back on whenever you need to protect sensitive fields again across your organization.
Splunk Cloud Platform
To turn off field filters in your environment, request help from Splunk Support. If you have a support contract, file a new case using the Splunk Support Portal at Support and Services. Otherwise, contact Splunk Customer Support.
Splunk Enterprise
To turn off field filters in your environment, follow these steps.
- Have the permissions to edit configuration files. Only users with file system access, such as system administrators, can edit configuration files.
- Know how to edit configuration files. Review the steps in How to edit a configuration file in the Splunk Enterprise Admin Manual.
- Decide which directory to store configuration file changes in. There can be configuration files with the same name in your default, local, and app directories. See Where you can place (or find) your modified configuration files in the Splunk Enterprise Admin Manual.
Steps
- Open the local limits.conf file at $SPLUNK_HOME/etc/system/local.
- In the
[search]
stanza, setfield_filters=false
. - Open the local web-features.conf file at $SPLUNK_HOME/etc/system/local.
- In the
[feature:field_filters]
stanza, setenable_field_filters_ui=false
. - Restart Splunk Enterprise, so the change to the configuration files take effect.
- If you're using field filters in a distributed search deployment, you must set
field_filters=false
in the limits.conf file andenable_field_filters_ui=false
in the web-features.conf file on all search heads and indexers.