> 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/rare-signature-signed-executable-executed-in-the-network.md).

# Rare signature signed executable executed in the network

### Synopsis

| Field                | Value                                            |
| -------------------- | ------------------------------------------------ |
| Activation Period    | 14 Days                                          |
| Training Period      | 30 Days                                          |
| Test Period          | N/A (single event)                               |
| Deduplication Period | 30 Days                                          |
| Required Data        | XDR Agent                                        |
| ATT\&CK Tactic       | Defense Impairment (TA0112)                      |
| ATT\&CK Technique    | Subvert Trust Controls: Code Signing (T1553.002) |
| Severity             | Informational                                    |

### Description

Attackers may use signed executables by less known vendors to bypass security features.

### Attacker's Goals

Adversaries may use signed binaries to bypass security features.

### Investigative actions

Check if this is legitimate software installed by a legitimate user and intentionally.

### Variations

<details>

<summary>Rare signature signed forensic tool remotely executed in the network</summary>

**Synopsis**

| Field             | Value                                            |
| ----------------- | ------------------------------------------------ |
| ATT\&CK Tactic    | Defense Impairment (TA0112)                      |
| ATT\&CK Technique | Subvert Trust Controls: Code Signing (T1553.002) |
| Severity          | Medium                                           |

**Description**

Attackers may use signed executables by less known vendors to bypass security features.

**Attacker's Goals**

Adversaries may use signed binaries to bypass security features.

**Investigative actions**

Check if this is legitimate software installed by a legitimate user and intentionally.

* Check the capabilities of the forensic tool, for example if it can read data directly from the disk.
* Check other activities seen from the same remote IP address.

</details>

<details>

<summary>Rare signature signed forensic tool executed in the network</summary>

**Synopsis**

| Field             | Value                                            |
| ----------------- | ------------------------------------------------ |
| ATT\&CK Tactic    | Defense Impairment (TA0112)                      |
| ATT\&CK Technique | Subvert Trust Controls: Code Signing (T1553.002) |
| Severity          | Low                                              |

**Description**

Attackers may use signed executables by less known vendors to bypass security features.

**Attacker's Goals**

Adversaries may use signed binaries to bypass security features.

**Investigative actions**

Check if this is legitimate software installed by a legitimate user and intentionally.

* Check the capabilities of the forensic tool, for example if it can read data directly from the disk.

</details>

<details>

<summary>Rare signature signed executable extracted from an internet-downloaded archive and executed in the network</summary>

**Synopsis**

| Field             | Value                                            |
| ----------------- | ------------------------------------------------ |
| ATT\&CK Tactic    | Defense Impairment (TA0112)                      |
| ATT\&CK Technique | Subvert Trust Controls: Code Signing (T1553.002) |
| Severity          | Low                                              |

**Description**

Attackers may use signed executables by less known vendors to bypass security features.

**Attacker's Goals**

Adversaries may use signed binaries to bypass security features.

**Investigative actions**

Check if this is legitimate software installed by a legitimate user and intentionally.

</details>

<details>

<summary>Rare signature signed executable downloaded from an uncommon source and executed in the network</summary>

**Synopsis**

| Field             | Value                                            |
| ----------------- | ------------------------------------------------ |
| ATT\&CK Tactic    | Defense Impairment (TA0112)                      |
| ATT\&CK Technique | Subvert Trust Controls: Code Signing (T1553.002) |
| Severity          | Low                                              |

**Description**

Attackers may use signed executables by less known vendors to bypass security features.

**Attacker's Goals**

Adversaries may use signed binaries to bypass security features.

**Investigative actions**

Check if this is legitimate software installed by a legitimate user and intentionally.

</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/rare-signature-signed-executable-executed-in-the-network.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.
