Re:Announcing impossible travel detection for all customers
by jjjjoe on Wednesday October 18, 2023 @08:11PM
(#37936550)
Thinking about my own usage patterns, when I'm working from home my laptop is VPNed to somewhere reasonably close lag-wise, but certainly not within 50 miles of my house. Meanwhile my phone is studiously checking my inbox using either the local cell tower or my home WiFi.
So if I go look at my personal access logs, I see myself flitting back and forth across the country constantly. I wonder how they plan to filter out these incredibly common false positives without also clobbering detection of thoroughly-owned (consistently-flitting) accounts.
Re:Announcing impossible travel detection for all customers
by supriyo-biswas on Wednesday October 18, 2023 @09:56PM
(#37937334)
This is a security product focused on the workplace, so they just need to mark their VPN IPs as trusted, or look at the flow logs between the user’s VPN packets to detect the original IP they’re connecting from.
Re:Announcing impossible travel detection for all customers
by chaps on Thursday October 19, 2023 @01:59AM
(#37939041)
GrubHub has this problem, kind of I think. If I'm on a VPN GrubHub will often deny access ("invalid password"...). Worse is, logging off of the VPN doesn't immediately help and neither does using another browser. Only thing I can do is wait until it decides to forget. Absolutely frustrating.
Re:Announcing impossible travel detection for all customers
by ComputerGuru on Thursday October 19, 2023 @10:56AM
(#37943772)
That’s almost certainly nothing related to location detection so much as it is the VPN block of IPs being marked as less trustworthy. Then there’s a cooldown on a flagged account that stops you even after disconnecting.
Re:Announcing impossible travel detection for all customers
by chatmasta on Wednesday October 18, 2023 @09:21PM
(#37937054)
So if I'm browsing your site from a VPN, you'll block me because of a datacenter IP. Then when I turn off my VPN to make your site work, you'll block me because I traveled too fast to my new location.
Re:Announcing impossible travel detection for all customers
by theideaofcoffee on Wednesday October 18, 2023 @11:18PM
(#37937927)
A solution in search of a problem, if past experience is any judge.
I ran into a rather poor implementation of this same 'feature' run by a former employer while I was attending AWS Reinvent a few years back. Apparently the different hotels/conference centers use different internet providers to funnel through conference wireless, and such have different registration info--different states, different address blocks, etc. Because I was disconnecting and connecting in a short amount of time when moving between sessions in different hotels, my VPN got caught up and went up the chain right to the CEO who demanded that I prove who I was to get access back. Such a hassle. Such a waste of time.
100% legitimate use and I get caught up in the mess. Just... no.
Now, the overzealous response by management aside, like other commenters have asked, how are they going to detect and filter and mitigate this incredibly common use case? Especially for individuals that hang around on a forum like this. Are they 'trusted' enough? Who defines who's trusted enough to evade the rules and logic? In the case of the former employer, everyone was remote and on VPN so where does that line get drawn? You could probably trigger this by moving between, say, airport wireless and mobile data because who knows where a mobile provider chooses to 'base' their block that serves that area at that time, it may not necessarily be that same metro-ish location.
Re:Announcing impossible travel detection for all customers
by cypherg on Thursday October 19, 2023 @01:46PM
(#37946045)
If they're not checking if it's the same device (or if it's a new device) that's connecting from the new IP, they're not really helping that much. Again, this is where client-based auth (preventative) is better than a spotty, reactive, response.
I wonder whether they'll remember to bump this up once commercial flights on the Boom Overture start.
So if I go look at my personal access logs, I see myself flitting back and forth across the country constantly. I wonder how they plan to filter out these incredibly common false positives without also clobbering detection of thoroughly-owned (consistently-flitting) accounts.
A better technical solution is prevention of access via IP allowlisting and then only allowing specific (Corp VPN) addresses.
I ran into a rather poor implementation of this same 'feature' run by a former employer while I was attending AWS Reinvent a few years back. Apparently the different hotels/conference centers use different internet providers to funnel through conference wireless, and such have different registration info--different states, different address blocks, etc. Because I was disconnecting and connecting in a short amount of time when moving between sessions in different hotels, my VPN got caught up and went up the chain right to the CEO who demanded that I prove who I was to get access back. Such a hassle. Such a waste of time.
100% legitimate use and I get caught up in the mess. Just... no.
Now, the overzealous response by management aside, like other commenters have asked, how are they going to detect and filter and mitigate this incredibly common use case? Especially for individuals that hang around on a forum like this. Are they 'trusted' enough? Who defines who's trusted enough to evade the rules and logic? In the case of the former employer, everyone was remote and on VPN so where does that line get drawn? You could probably trigger this by moving between, say, airport wireless and mobile data because who knows where a mobile provider chooses to 'base' their block that serves that area at that time, it may not necessarily be that same metro-ish location.