> 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/a-user-logged-in-from-an-abnormal-country-or-asn.md).

# A user logged in from an abnormal country or ASN

### Synopsis

| Field                | Value                                                                   |
| -------------------- | ----------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                 |
| Training Period      | 30 Days                                                                 |
| Test Period          | N/A (single event)                                                      |
| Deduplication Period | 1 Day                                                                   |
| Required Data        | XDR Agent                                                               |
| 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             | Informational                                                           |

### Description

A user logged in from an unusual country or ASN. This may indicate that the account was compromised.

### Attacker's Goals

Gain user-account credentials.

### Investigative actions

* Check if the user is currently located in the aforementioned country.
* Check for any other suspicious activity related to the account.
* Check other ASNs and Countries that the user logged in from.
* Look for additional login attempts.

### Variations

<details>

<summary>A service account successfully logged in from a new country or ASN</summary>

**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          | Low                                                                     |

**Description**

A service account successfully logged in to an internet facing server from an unusual country or ASN. This may indicate that the account was compromised.

**Attacker's Goals**

Gain user-account credentials.

**Investigative actions**

* Check if the user is currently located in the aforementioned country.
* Check for any other suspicious activity related to the account.
* Check other ASNs and Countries that the user logged in from.
* Look for additional login attempts.

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/a-user-logged-in-from-an-abnormal-country-or-asn.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
