hammer185 Thanks for the feedback and the case scenario. While the risk based authentication methods are the industry standard at this point, you raise some valid points with regards to mobile users, and the behaviors of their telecom providers. I.e. where they are routing traffic through, and how this automatically triggers a device warning on our side.
So what is the problem besides something like arrogance, obstinate stupidity, or just a total lack of common sense? Does LogMeIn lack the intelligence to explain where they got the location data from in any scenario that may come up and cite the source in case it's wrong. Do you have a business policy problems or just stupid programmers or something like that. You obviously have a serious problem if you know often the data in the emails you send out about locations is wrong and yet you refuse to acknowledge that it may be incorrect and cite the source of the data so it can be looked into when its wrong.
hammer185 This is actually the first time something similar has been reported.
Under most circumstances, if a user is having difficulty with the RBA authentication, Customer Care can help to 'whitelist' specific devices. When I use the term 'device', I don't mean one location or computer -- but several qualifying factors that go into the risk factor.
I am the owner and manager for my company on these things. I want accurate location data to be used in making these informed decisions. I expect others in my position making these decisions would feel similarly. These are not personal devices we use, they are work tools often used for remote access when needed in helping our customers and keeping our networks running. I do not want to just "whitelist" a device or devices that could potentially be stolen and we might not notice it until it's been used to get into a system I do not want gotten into by the thiev(ves).
If the location data were accurate there are several cool things we could probably do. The location data has to be accurate though.
hammer185 The good news is that RBA could flag a PC again when it changed locations. Depending on where and when the login attempts were made from, it may even send a security email when the danger is high enough.
** I am still trying to replicate the issue you experienced, though have not been able to see my Verizon mobile internet connection route traffic through Las Vegas yet.
