> 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/uncommon-communication-to-an-instant-messaging-server.md).

# Uncommon communication to an instant messaging server

### 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                    |
| ATT\&CK Tactic       | Command and Control (TA0011) |
| ATT\&CK Technique    | Web Service (T1102)          |
| Severity             | Informational                |

### Description

A rare communication between a process to a known instant messaging server.

### Attacker's Goals

Data exfiltration or attack tool staging through a trusted service.

### Investigative actions

* Examine the legitimacy of the application that made the communication with the provider's server.
* Examine the parent process of this application.
* Check for anomalies regarding the time frame where the communication occurred.

### Variations

<details>

<summary>Uncommon communication to an instant messaging server by a suspicious process</summary>

**Synopsis**

| Field             | Value                        |
| ----------------- | ---------------------------- |
| ATT\&CK Tactic    | Command and Control (TA0011) |
| ATT\&CK Technique | Web Service (T1102)          |
| Severity          | Low                          |

**Description**

A rare communication by a suspicious process to a known instant messaging server.

**Attacker's Goals**

Data exfiltration or attack tool staging through a trusted service.

**Investigative actions**

* Examine the legitimacy of the application that made the communication with the provider's server.
* Examine the parent process of this application.
* Check for anomalies regarding the time frame where the communication occurred.

</details>

<details>

<summary>Uncommon communication to an instant messaging server by an uncommon scripting engine execution</summary>

**Synopsis**

| Field             | Value                        |
| ----------------- | ---------------------------- |
| ATT\&CK Tactic    | Command and Control (TA0011) |
| ATT\&CK Technique | Web Service (T1102)          |
| Severity          | Low                          |

**Description**

A rare communication by an uncommon execution of a scripting engine to a known instant messaging server.

**Attacker's Goals**

Data exfiltration or attack tool staging through a trusted service.

**Investigative actions**

* Examine the legitimacy of the application that made the communication with the provider's server.
* Examine the parent process of this application.
* Check for anomalies regarding the time frame where the communication occurred.

</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 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/uncommon-communication-to-an-instant-messaging-server.md?ask=<question>&goal=<endgoal>
```

`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.
