Splunk Search

updating geolocation DB

wainwrid
Engager

Currently, we are running 6.6.2 and are using the geolite2 DB to do the iplocation mapping.

I have read the following articles:

https://www.splunk.com/blog/2014/07/22/updating-the-iplocation-db.html

http://www.georgestarcher.com/splunk-updating-the-geoip-database/

However, maxmind states that this DB is End of Life'd. There will be no additional updates after next month.

https://support.maxmind.com/geolite-legacy-discontinuation-notice/

How is Splunk going to handle these lookups in the future? What method of updating will be done?

We have been debating creating a lookup table that utilizes BGP routes. Is there a best practice or built in functionality that accomplishes this already?

We looked at ASNGenerator, but this also relies on the End of Life data from maxmind.

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Maxmind is ending the old GeoLite database. Splunk uses GeoLite2, which is not going away.

---
If this reply helps you, Karma would be appreciated.
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: Level up your SOC: Advancing with Splunk Enterprise Security

AI has fundamentally raised the stakes for security operations, and this three-part series is your guide to ...

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 ...

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...