> 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-remote-monitoring-and-management-tool.md).

# Uncommon remote monitoring and management tool

### 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    | Remote Access Tools (T1219)  |
| Severity             | Low                          |

### Description

An uncommon Remote Monitoring and Management (RMM) product was observed.

### Attacker's Goals

* Accessing a remote machine with full interactive graphic interface capabilities.

### Investigative actions

* Check if the product usage is approved.
* Ask the owners of the machine if they knowingly used this software.
* Investigate why the software was being used.
* Check if it was executed remotely or locally.

### Variations

<details>

<summary>Uncommon renamed remote monitoring and management tool</summary>

**Synopsis**

| Field             | Value                        |
| ----------------- | ---------------------------- |
| ATT\&CK Tactic    | Command and Control (TA0011) |
| ATT\&CK Technique | Remote Access Tools (T1219)  |
| Severity          | Medium                       |

**Description**

An uncommon renamed Remote Monitoring and Management (RMM) product was observed.

**Attacker's Goals**

* Accessing a remote machine with full interactive graphic interface capabilities.

**Investigative actions**

* Check if the product usage is approved.
* Ask the owners of the machine if they knowingly used this software.
* Investigate why the software was being used.
* Check if it was executed remotely or locally.

</details>

<details>

<summary>Uncommon remote monitoring and management tool (browser origin)</summary>

**Synopsis**

| Field             | Value                        |
| ----------------- | ---------------------------- |
| ATT\&CK Tactic    | Command and Control (TA0011) |
| ATT\&CK Technique | Remote Access Tools (T1219)  |
| Severity          | Informational                |

**Description**

An uncommon Remote Monitoring and Management (RMM) product was observed. (browser origin).

**Attacker's Goals**

* Accessing a remote machine with full interactive graphic interface capabilities.

**Investigative actions**

* Check if the product usage is approved.
* Ask the owners of the machine if they knowingly used this software.
* Investigate why the software was being used.
* Check if it was executed remotely or locally.

</details>

<details>

<summary>Uncommon remote monitoring and management tool extracted from an internet-downloaded archive and executed</summary>

**Synopsis**

| Field             | Value                        |
| ----------------- | ---------------------------- |
| ATT\&CK Tactic    | Command and Control (TA0011) |
| ATT\&CK Technique | Remote Access Tools (T1219)  |
| Severity          | Low                          |

**Description**

An uncommon Remote Monitoring and Management (RMM) product extracted from an internet-downloaded archive and executed.

**Attacker's Goals**

* Accessing a remote machine with full interactive graphic interface capabilities.

**Investigative actions**

* Check if the product usage is approved.
* Ask the owners of the machine if they knowingly used this software.
* Investigate why the software was being used.
* Check if it was executed remotely or locally.

</details>

<details>

<summary>Uncommon remote monitoring and management tool downloaded from an uncommon source and executed</summary>

**Synopsis**

| Field             | Value                        |
| ----------------- | ---------------------------- |
| ATT\&CK Tactic    | Command and Control (TA0011) |
| ATT\&CK Technique | Remote Access Tools (T1219)  |
| Severity          | Medium                       |

**Description**

An uncommon Remote Monitoring and Management (RMM) product downloaded from an uncommon source and executed.

**Attacker's Goals**

* Accessing a remote machine with full interactive graphic interface capabilities.

**Investigative actions**

* Check if the product usage is approved.
* Ask the owners of the machine if they knowingly used this software.
* Investigate why the software was being used.
* Check if it was executed remotely or locally.

</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/uncommon-remote-monitoring-and-management-tool.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.
