> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/impossible-traveler-sso.md).
# Impossible traveler - SSO
### Synopsis
| Field | Value |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 6 Hours |
| Deduplication Period | 1 Day |
| Required Data | Requires one of the following data sources:
AzureAD OR Azure SignIn Log OR Idira OR Duo OR Okta OR OneLogin OR PingOne
|
| Detection Modules | Identity Analytics |
| ATT\&CK Tactic | Credential Access (TA0006), Resource Development (TA0042) |
| ATT\&CK Technique | Compromise Accounts (T1586), Brute Force: Password Guessing (T1110.001) |
| Severity | Low |
### Description
User connected from several remote countries, at least one of which is not commonly used in the organization, within a short period of time. This may indicate the account is compromised.
### Attacker's Goals
Gain user-account credentials.
### Investigative actions
Check if the user routed their traffic via a VPN, or shared their credentials with a remote employee.
### Variations
Impossible traveler - non-interactive SSO authentication
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Resource Development (TA0042) |
| ATT\&CK Technique | Compromise Accounts (T1586), Brute Force: Password Guessing (T1110.001) |
| Severity | Informational |
**Description**
User connected from several remote countries, at least one of which is not commonly used in the organization, within a short period of time. This may indicate the account is compromised.
**Attacker's Goals**
Gain user-account credentials.
**Investigative actions**
Check if the user routed their traffic via a VPN, or shared their credentials with a remote employee.
Possible Impossible traveler via SSO
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Resource Development (TA0042) |
| ATT\&CK Technique | Compromise Accounts (T1586), Brute Force: Password Guessing (T1110.001) |
| Severity | Informational |
**Description**
User connected from several remote countries, at least one of which is not commonly used in the organization, within a short period of time. This may indicate the account is compromised.
**Attacker's Goals**
Gain user-account credentials.
**Investigative actions**
Check if the user routed their traffic via a VPN, or shared their credentials with a remote employee.
SSO impossible traveler from a VPN or proxy
**Synopsis**
| Field | Value |
| ----------------- | ----------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Resource Development (TA0042) |
| ATT\&CK Technique | Compromise Accounts (T1586), Brute Force: Password Guessing (T1110.001) |
| Severity | Informational |
**Description**
User connected from several remote countries, at least one of which is not commonly used in the organization, within a short period of time. This may indicate the account is compromised.
**Attacker's Goals**
Gain user-account credentials.
**Investigative actions**
Check if the user routed their traffic via a VPN, or shared their credentials with a remote employee.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/impossible-traveler-sso.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.