> 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-network-connection-under-an-untrusted-causality-actor.md).
# Uncommon network connection under an untrusted causality actor
### 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 | Exfiltration (TA0010) |
| ATT\&CK Technique | Exfiltration Over Alternative Protocol (T1048) |
| Severity | Informational |
### Description
Uncommon network activity was detected from a process running under an untrusted causality actor. The causality actor is untrusted with a rare hash, and the connection was made to a rare domain. The observed connection pattern is consistent with data exfiltration, command-and-control communication, or covert channel techniques.
### Attacker's Goals
The connection pattern observed is consistent with data exfiltration, command-and-control communication, or covert channel techniques an adversary would use to transfer data out of the network.
### Investigative actions
Investigate the causality chain to determine whether this network activity is expected. Cross-reference with the originating process, destination IP/hostname, and any related alerts on the host.
### Variations
Uncommon network connection from an unsigned process under an untrusted causality actor
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------- |
| ATT\&CK Tactic | Exfiltration (TA0010) |
| ATT\&CK Technique | Exfiltration Over Alternative Protocol (T1048) |
| Severity | Low |
**Description**
Uncommon network activity was detected from a process running under an untrusted causality actor. The causality actor is untrusted with a rare hash, and the connection was made to a rare domain. The observed connection pattern is consistent with data exfiltration, command-and-control communication, or covert channel techniques.
**Attacker's Goals**
The connection pattern observed is consistent with data exfiltration, command-and-control communication, or covert channel techniques an adversary would use to transfer data out of the network.
**Investigative actions**
Investigate the causality chain to determine whether this network activity is expected. Cross-reference with the originating process, destination IP/hostname, and any related alerts on the host.
Uncommon network connection from a LOLBIN under an untrusted causality actor
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------- |
| ATT\&CK Tactic | Exfiltration (TA0010) |
| ATT\&CK Technique | Exfiltration Over Alternative Protocol (T1048) |
| Severity | Low |
**Description**
Uncommon network activity was detected from a process running under an untrusted causality actor. The causality actor is untrusted with a rare hash, and the connection was made to a rare domain. The observed connection pattern is consistent with data exfiltration, command-and-control communication, or covert channel techniques.
**Attacker's Goals**
The connection pattern observed is consistent with data exfiltration, command-and-control communication, or covert channel techniques an adversary would use to transfer data out of the network.
**Investigative actions**
Investigate the causality chain to determine whether this network activity is expected. Cross-reference with the originating process, destination IP/hostname, and any related alerts on the host.
Uncommon network connection from a browser running under an untrusted causality actor
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------- |
| ATT\&CK Tactic | Exfiltration (TA0010) |
| ATT\&CK Technique | Exfiltration Over Alternative Protocol (T1048) |
| Severity | Low |
**Description**
Uncommon network activity was detected from a process running under an untrusted causality actor. The causality actor is untrusted with a rare hash, and the connection was made to a rare domain. The observed connection pattern is consistent with data exfiltration, command-and-control communication, or covert channel techniques.
**Attacker's Goals**
The connection pattern observed is consistent with data exfiltration, command-and-control communication, or covert channel techniques an adversary would use to transfer data out of the network.
**Investigative actions**
Investigate the causality chain to determine whether this network activity is expected. Cross-reference with the originating process, destination IP/hostname, and any related alerts on the host.
---
# 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/uncommon-network-connection-under-an-untrusted-causality-actor.md?ask=&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.