Checkpoint firewall log storage policy is set to rotate everyday at midnight where new "file id" is created for the log file "fw.log" every midnight.
In the Splunk forwarder -
For every new file id - splunk app creates a new stanza under the file : opsec-log-status.conf
Eg:
[
[email protected]]
fileid = 1438127971
filename = 2015-07-29_235900.log
last_rec_pos = 70000
[
[email protected]]
fileid = 1438214351
filename = fw.log
last_rec_pos = 35441
Every time the script triggers, the old file id (which has been already collected data t splunk) also runs and gets the same data again to Splunk. This causes high license usage.
Only the latest file id should be should be monitored with the last loc values it has left.
Check point device maintains the log track file clearly, where every day an entry is made (fw.logtrack) with the current status.
Why doesn't Splunk ignore the already indexed data? OPSEC LEA should only be made to read the current file id to get the data which doesn't happen!
Please advise, is there any workaround ,
... View more