Getting Data In

Is crcSalt = still supported?

ontai
Explorer

I'm trying to index Nessus and Snort rules for use in cross-correlation of security events. In previous versions of Splunk, I had to add an entry in props.conf (crcSalt = ) to ensure that Splunk would reindex the entire file any time the contents changed.

But now when I startup Splunk running 4.3.1, I get errors about a potential syntax error:

Possible typo in stanza [nessus_plugins] in /opt/splunk/etc/apps/ResponsysSecurityConsole/local/props.conf, line 5: crcSalt =

Is this option still supported? If not, what can I do to ensure that Splunk always indexes the complete file when any changes to it are detected?

Thx.

Craig

Tags (2)
0 Karma
1 Solution

sdaniels
Splunk Employee
Splunk Employee

Should be fine. I believe it's crcSalt = <SOURCE>. Needs to be capitilized. And you would put it in inputs.conf.

View solution in original post

sdaniels
Splunk Employee
Splunk Employee

Should be fine. I believe it's crcSalt = <SOURCE>. Needs to be capitilized. And you would put it in inputs.conf.

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!

Event Series: Splunk Observability Metrics Cost Optimization

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...