Last Updated: 2018-07-17 11:48:00 UTC
by Xavier Mertens (Version: 1)
For the human brain, an IP address is not the best IOC because, like phone numbers, we are bad to remember them. That’s why DNS was created. But, in many log management applications, there are features to enrich collected data. One of the possible enrichment for IP addresses is the geolocalization. Based on databases, it is possible to locate an IP address based on the country and/or the city. This information is available in our DShield IP reputation database. But you can also find coordinates with a latitude and a longitude:
$ geoiplookup isc.sans.edu GeoIP Country Edition: US, United States GeoIP City Edition, Rev 1: US, MD, Maryland, Bethesda, 20814, 39.006001, -77.102501, 511, 301 GeoIP ASNum Edition: AS62669 SANS INSTITUTE
The command geoiplookup, as well as the GeoIP databases, are developed by Maxmind  which is one of the companies which provide this kind of services. Of course, you can also create your own/private database of IP address (or subnets) and attach coordinates to them. This is very useful if you operate a worldwide network or if you’re based in a large country like the United States. In this case, if subnets are assigned per branch offices, you can search for their coordinates via Google maps and populate your database:
Once this exercise completed, the idea is to compute the distance between two IP addresses using the”Haversine” formula which determines the distance between two points on a sphere given their longitudes and latitudes. Here is a quick and dirty Python script which implements the formula for two IP addresses GeoIP lookups:
#!/usr/bin/python import sys import geoip2.database import math def haversine((lat1, long1), (lat2, long2)): radius = 6371 # In kilometers dLat = math.radians(lat2 - lat1) dLong = math.radians(long2 - long1) a = (math.sin(dLat / 2) ** 2 + math.cos(math.radians(lat1)) * math.cos(math.radians(lat2)) * math.sin(dLong / 2) ** 2) c = 2 * math.atan2(math.sqrt(a), math.sqrt(1 - a)) d = radius * c return d reader=geoip2.database.Reader('GeoLite2-City.mmdb') r1 = reader.city(sys.argv) r2 = reader.city(sys.argv) print "%s: %s, %s" % (sys.argv, r1.country.name, r1.city.name) print "%s: %s, %s" % (sys.argv, r2.country.name, r2.city.name) d = haversine((float(r1.location.latitude), float(r1.location.longitude)), (float(r2.location.latitude), float(r2.location.longitude))) print "Distance: %f Kms" % d
$ host -t a isc.sans.org isc.sans.org has address 220.127.116.11 $ host -t a www.nsa.gov www.nsa.gov is an alias for www.nsa.gov.edgekey.net. www.nsa.gov.edgekey.net is an alias for e6655.dscna.akamaiedge.net. e6655.dscna.akamaiedge.net has address 18.104.22.168 $ python distance.py 22.214.171.124 126.96.36.199 188.8.131.52: United States, Bethesda 184.108.40.206: United States, Cambridge Distance: 629.667952 Kms
Now, we can implement more tests to detect unusual behaviours when consecutive connections are detected for the same username. Let’s assume that Johannes connected to my server at a specific time from isc.sans.org and, 15 minutes later, the same username was used from www.nsa.gov (this is just an example ;-). From a purely geographical point of view, this is suspicious and must be investigated.
The next checks can be implemented to detect geographically improbable login attempts:
- If the distance between the two connection attempts is <1000 Kms: we can assume that the user will take a train or a car to travel (a slow means of transport). The minimum time between two connections must be above 8 hours (let’s assume the speed up to 100Km/h).
- If the distance is above, we may expect that the user will use a plane to travel: 2 hours for the check-in process, a typical airliner is flying at ~800Km/h and add 2h to get out of the airport and travel to the final destination. We may assume a delay of min 24h.
It's up to you to analyze the behaviour of your users to apply efficient checks. This technique is quite easy to implement in your log management/SIEM solution (just a few math operations). By example, there is a Haversine app available for Splunk.
Note: values have been computed using the metric system but for miles, divide km by 1.609344.
Xavier Mertens (@xme)
ISC Handler - Freelance Security Consultant
If you have more information or corrections regarding our diary, please share.