Impossible Travel Auth0 login
Set up the auth0 integration.
このページは日本語には対応しておりません。随時翻訳に取り組んでいます。
翻訳に関してご質問やご意見ございましたら、
お気軽にご連絡ください。
Goal
Detect an Impossible Travel event when two successful authentication events occur in a short time frame.
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.name}} traveled more than 500km at over 1,000km/hr.
Triage and response
- Determine if the user
{{@usr.name}} should have authenticated 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}}. - If
{{@user.name}} should not authenticated 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}}, then consider isolating the account and reset credentials. - Audit any instance actions that may have occurred after the illegitimate login.
NOTE VPNs and other anonymous IPs are filtered out of this signal
Changelog
- 10 October 2022 - Updated query.
- 20 November 2023 - Updated group by values to include
@usr.id. - 30 September 2024 - Updated query to replace attribute
@threat_intel.results.subcategory:anonymizer.
