PingOne impossible travel authentication attempts by OTP

This rule is part of a beta feature. To learn more, contact Support.
이 페이지는 아직 영어로 제공되지 않습니다. 번역 작업 중입니다.
현재 번역 프로젝트에 대한 질문이나 피드백이 있으신 경우 언제든지 연락주시기 바랍니다.

Goal

Detect when unusual authentication attempts from different geo locations are made from a single user.

Strategy

The Impossible Travel detection type’s algorithm compares the GeoIP data of the last log and the current log to determine if the user {{@resources.name}} traveled more than 500km at over 1,000km/h. This detection rule aims to identify potential threats early, allowing for timely investigation and mitigation to protect server resources and maintain service availability.

Triage and response

  1. Investigate the source user {{@resources.name}} with a request from different geo location 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}}.
  2. Implement immediate measures to block or limit the impact of the suspicious activity if confirmed as a threat.
PREVIEWING: aliciascott/DOCS-9725-Cloudcraft