Splunk Enterprise Security

Detected deprecated Threat Intelligence Manager inputs- Do I have to completely remove the inputs?

Path Finder


I am recieving the following warning on my alerts:

Health Check: Detected deprecated Threat Intelligence Manager inputs that are not supported by Enterprise Security version 6.4.0 or higher. Recreate these inputs as Threatlist inputs or remove if unnecessary.

Drill downing into the results of the deprecated inputs, I see the following:


Which I have found them to be in the DA-ESS-ThreatIntelligence/local/inputs.conf file and disabled them via making the 0s to 1s in the "disabled" field section under each input.

Do I have to completely remove/comment the inputs out? Why else would I still keep recieving alerts about it when it is disabled? Is there any where else I should be looking or changing for the deprecated intelligence inputs?


Best Regards,

0 Karma
1 Solution

Path Finder

Issue seems to have resolved itself after a server restart

View solution in original post


I was facing similar Problem and I had to comment the inputs (even though they were disabled). After commenting the inputs and restarting the Splunk service, issue was resolved, and the warning disappeared.

0 Karma

Ultra Champion

+1 to that. Disabling inputs wasn't sufficient because theye were still defined albeit disabled. Had to comment them out completely.

New Member


I am also receiving this type of error, but the inputs are necessary, so is there a way to resolve this without disabling them?

They are currently disabled in the same fashion listed above in @zekiramhi  post  ( 0  to 1 in the disabled fields) and still generating the error messages even after several server restarts.

Thanks in advance for any info.



0 Karma

Path Finder

Issue seems to have resolved itself after a server restart

Get Updates on the Splunk Community!

Build Scalable Security While Moving to Cloud - Guide From Clayton Homes

 Clayton Homes faced the increased challenge of strengthening their security posture as they went through ...

Mission Control | Explore the latest release of Splunk Mission Control (2.3)

We’re happy to announce the release of Mission Control 2.3 which includes several new and exciting features ...

Cloud Platform | Migrating your Splunk Cloud deployment to Python 3.7

Python 2.7, the last release of Python 2, reached End of Life back on January 1, 2020. As part of our larger ...