Impossible travel scenario observed in Cloudflare logs
Set up the cloudflare integration.
Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel,
n'hésitez pas à nous contacter.
Goal
Detect an Impossible Travel event within Cloudflare logs.
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 (@usr.email) traveled more than 500km at over 1,000km/h.
Triage and response
- Determine if
{{@usr.email}} should be connecting 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. - If the user should not be connecting from
{{@impossible_travel.triggering_locations.first_location.city}}, {{@impossible_travel.triggering_locations.first_location.country}} or {{@impossible_travel.triggering_locations.second_location.city}}, {{@impossible_travel.triggering_locations.second_location.country}}, then consider isolating the account and resetting their credentials. - Use the Cloud SIEM - User Investigation dashboard to audit any user actions that may have occurred after the illegitimate login.
