Keycloak impossible user travel detected

This rule is part of a beta feature. To learn more, contact Support.

Set up the keycloak integration.

이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

Goal

Identify instances where users are trying to login from two distant geographical locations within an improbable time frame, potentially indicating credential theft or account compromise.

Strategy

This rule analyzes login events to identify cases where a user appears to perform activities from two different countries or cities within a time frame that would make physical travel between those locations impossible.

Triage and response

  1. Determine if userId {{@usr.id}} connected from {{@impossible_travel.triggering_locations.first_location.city}}, {{@impossible_travel.triggering_locations.first_location.country}} and {{@impossible_travel.triggering_locations.second_location.city}}, {{@impossible_travel.triggering_locations.second_location.country}} in a short period of time.
  2. Check for any failed login attempts or other unusual activities related to the user.
  3. Contact the affected user to verify whether they initiated the login events.
  4. If the user did not perform the logins, restrict their access until their credentials are reset.