Splunk Search

Still necessary to disable typeahead?

Jason
Motivator

I recently upgraded a Splunk environment from 3.4.x and the previous documentation included recommendations to disable typeahead for search performance and "data leakage" reasons.

Are these still valid concerns in 4.1.x?

Tags (1)

zscgeek
Path Finder

From what I have seen in my install performance of type-ahead is a LOT better in 4.1.x and there is no need to disable it for that.

However the data leakage issue still exists if you are using search filters to restrict access to events between roles or users. Suggestions will include data that would be blocked in search filters. If you don't use search filters per role or user I would not worry about it however.

--- RJ

Get Updates on the Splunk Community!

Detecting Remote Code Executions With the Splunk Threat Research Team

WATCH NOWRemote code execution (RCE) vulnerabilities pose a significant risk to organizations. If exploited, ...

Enter the Splunk Community Dashboard Challenge for Your Chance to Win!

The Splunk Community Dashboard Challenge is underway! This is your chance to showcase your skills in creating ...

.conf24 | Session Scheduler is Live!!

.conf24 is happening June 11 - 14 in Las Vegas, and we are thrilled to announce that the conference catalog ...