Splunk Enterprise Security

Splunk ES correlation searches problem

BAPA157
Engager

Hello,

I have figured out a strange behavior of Splunk correlation searches. I'm using Splunk Enterprise version 7.0.1 and ES version 4.7.4.
I created a new app to store my custom correlation searches and ensured that it is accepted by Enterprise Security by naming it TA-custom-correlation-searches.
Inside that app I created under local a savedsearches.conf configuration with the following content.

#comment1

[Threat - correlation_search_1 - Rule] 
configuration1=... 
configuration2=... 
....

#comment2
#comment3
#comment4
#comment5

[Threat - corelation_search_2 - Rule] 
configuration1=... 
configuration2=... 
....

#comment6

Both correlation searches work as expected. At this point everything is fine.
Now, I disable both correlation searches in the ES app under Content Management and afterwards I took a look into my savedsearches.conf:

#comment1

[Threat - correlation_search_1 - Rule] 
configuration1=...
configuration2=...
....


[Threat - corelation_search_2 - Rule]
configuration1=...
configuration2=...
....

#comment6

Splunk deleted all comments between the two correlation searches.
Did somebody figure out the same issue?
Thank you for your help.

Best regards,
Patrick

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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Analytics Workspace removal in Splunk 10.6

In Splunk Cloud Platform and Splunk Enterprise 10.6, Analytics Workspace is removed from product and no longer ...

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...