Are there any examples of how GPS coordinate (or any location data really) can be used to detect suspicious locations or validate well known locations?
- Highlighting new or unusual locations
- Simultaneous / concurrent usage (a session in the US and also in China may be indicative of an attack)
- Reduced PW challenges for "known" locations
I'm interested in using Browser Location data, source IP, GPS (on phone devices) or any other metatata that can be used to identify and separate "good "authentication sessions from "bad" sessions.
By the way: Confused deputy attacks are out of scope for this, since that attack will likely have valid location data. I'm mainly focused on validating good sessions, or challenging risky sessions instead of or in combination with a permanent cookie
What I hope to learn is how the implementer has addressed roaming users, VPNs and other data validation techniques. I'd also be interested in seeing the "user story" on what process flow would look like.