Geo-based policies help administrators control where login attempts are allowed to originate from. Using geo-information retrieved from users’ IP address, administrators can automatically deny authentication when access requests come from unwanted locations, or fall outside of location velocity parameters.
Keep reading to learn more about geo-based policies in LoginTC.
Benefits of Geo-based policies
If you know where all your users should be, why not limit authentication requests to only those places?
With geo-based policies, you can limit potential cyber attacks by automatically screening out login attempts that come from unauthorized countries, or that are suspicious based on the speed of travel between the location of two login attempts.
Learn more about the two types of geo-policies available: Geo-Location and Geo-Velocity.
Geo Location Policies
Geo-Location policies allow you to set automated authentication rules spending on the location of a login attempt.
You can set your policy to deny authentications from particular countries, or when the system is unable to determine the location of a login attempt.
Geo-Velocity Policies
Geo-Velocity policies allow you to set automated authentication rules when two login attempts occur within or outside a specific time and distance from one another.
For example, setting a geo-velocity policy of 500 km/hour ensures that a login attempt from Paris cannot be granted only thirty minutes after a login attempt from New York was granted.
Watch the Video
Watch the video to learn about Geo-based policies and how to implement Geo-Location and Geo-Velocity policies in your organization.
Geo Policies and Authentication Logs
Geo-based policies work hand-in-hand with LoginTC Authentication Logs. Use Authentication Logs to determine why users were denied access, and to scan for any suspicious login activity that was granted or denied.
