> 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/globally-uncommon-ip-address-by-a-common-process-sha256.md).

# Globally uncommon IP address by a common process (sha256)

### 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                          |
| Detector Tags        | Global Anomaly Analytics           |
| ATT\&CK Tactic       | Command and Control (TA0011)       |
| ATT\&CK Technique    | Application Layer Protocol (T1071) |
| Severity             | Informational                      |

### Description

A process with a common sha256 connected to an external IP address that, on a global level, it usually doesn't connect to.

### Attacker's Goals

Attackers may use various methods to execute code from the context of another process to avoid detection.

### Investigative actions

* Check the destination IP address reputation.
* Check if the actor process loaded a suspicious DLL before the alert.
* Check if the actor process was injected before the alert.
* Check if the process execution and connections are legitimate.

### Variations

<details>

<summary>Globally uncommon IP address by a common process (sha256) from an injected thread</summary>

**Synopsis**

| Field             | Value                                                         |
| ----------------- | ------------------------------------------------------------- |
| ATT\&CK Tactic    | Command and Control (TA0011), Stealth (TA0005)                |
| ATT\&CK Technique | Application Layer Protocol (T1071), Process Injection (T1055) |
| Severity          | High                                                          |

**Description**

A process with a common sha256 connected to an external IP address that, on a global level, it usually doesn't connect to.

**Attacker's Goals**

Attackers may use various methods to execute code from the context of another process to avoid detection.

**Investigative actions**

* Check the destination IP address reputation.
* Check if the actor process loaded a suspicious DLL before the alert.
* Check if the actor process was injected before the alert.
* Check if the process execution and connections are legitimate.

</details>

<details>

<summary>Globally uncommon IP address by a common process (sha256) from a known vendor</summary>

**Synopsis**

| Field             | Value                              |
| ----------------- | ---------------------------------- |
| ATT\&CK Tactic    | Command and Control (TA0011)       |
| ATT\&CK Technique | Application Layer Protocol (T1071) |
| Severity          | Medium                             |

**Description**

A process with a common sha256 connected to an external IP address that, on a global level, it usually doesn't connect to.

**Attacker's Goals**

Attackers may use various methods to execute code from the context of another process to avoid detection.

**Investigative actions**

* Check the destination IP address reputation.
* Check if the actor process loaded a suspicious DLL before the alert.
* Check if the actor process was injected before the alert.
* Check if the process execution and connections are legitimate.

</details>

<details>

<summary>Globally uncommon and very rare IP address by a common process (sha256)</summary>

**Synopsis**

| Field             | Value                              |
| ----------------- | ---------------------------------- |
| ATT\&CK Tactic    | Command and Control (TA0011)       |
| ATT\&CK Technique | Application Layer Protocol (T1071) |
| Severity          | Medium                             |

**Description**

A process with a common sha256 connected to an external IP address that, on a global level, it usually doesn't connect to.

**Attacker's Goals**

Attackers may use various methods to execute code from the context of another process to avoid detection.

**Investigative actions**

* Check the destination IP address reputation.
* Check if the actor process loaded a suspicious DLL before the alert.
* Check if the actor process was injected before the alert.
* Check if the process execution and connections are legitimate.

</details>

<details>

<summary>Globally uncommon and a rare IP address by a common process (sha256)</summary>

**Synopsis**

| Field             | Value                              |
| ----------------- | ---------------------------------- |
| ATT\&CK Tactic    | Command and Control (TA0011)       |
| ATT\&CK Technique | Application Layer Protocol (T1071) |
| Severity          | Low                                |

**Description**

A process with a common sha256 connected to an external IP address that, on a global level, it usually doesn't connect to.

**Attacker's Goals**

Attackers may use various methods to execute code from the context of another process to avoid detection.

**Investigative actions**

* Check the destination IP address reputation.
* Check if the actor process loaded a suspicious DLL before the alert.
* Check if the actor process was injected before the alert.
* Check if the process execution and connections are legitimate.

</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/globally-uncommon-ip-address-by-a-common-process-sha256.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.