> 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/psexec-was-executed-with-a-suspicious-command-line.md).

# PsExec was executed with a suspicious command line

### 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       | Execution (TA0002), Privilege Escalation (TA0004)                      |
| ATT\&CK Technique    | System Services: Service Execution (T1569.002), Valid Accounts (T1078) |
| Severity             | Informational                                                          |

### Description

PsExec.exe was executed.

### Attacker's Goals

An adversary may attempt to use PsExec to gain execution capabilities, run remote commands or perform privilege escalation.

### Investigative actions

* Check if any other suspicious activities happened under the same causality.
* Confirm the PsExec.exe command is benign.

### Variations

<details>

<summary>PsExec was executed with a suspicious command line by a LOLBIN</summary>

**Synopsis**

| Field             | Value                                                                  |
| ----------------- | ---------------------------------------------------------------------- |
| ATT\&CK Tactic    | Execution (TA0002), Privilege Escalation (TA0004)                      |
| ATT\&CK Technique | System Services: Service Execution (T1569.002), Valid Accounts (T1078) |
| Severity          | Low                                                                    |

**Description**

PsExec.exe was executed with NT/System privilege level by a LOLBIN.

**Attacker's Goals**

An adversary may attempt to use PsExec to gain execution capabilities, run remote commands or perform privilege escalation.

**Investigative actions**

* Check if any other suspicious activities happened under the same causality.
* Confirm the PsExec.exe command is benign.

</details>

<details>

<summary>PsExec was executed with a suspicious command line by an unsigned actor</summary>

**Synopsis**

| Field             | Value                                                                  |
| ----------------- | ---------------------------------------------------------------------- |
| ATT\&CK Tactic    | Execution (TA0002), Privilege Escalation (TA0004)                      |
| ATT\&CK Technique | System Services: Service Execution (T1569.002), Valid Accounts (T1078) |
| Severity          | Medium                                                                 |

**Description**

PsExec.exe was executed with NT/System privilege level by an unsigned actor.

**Attacker's Goals**

An adversary may attempt to use PsExec to gain execution capabilities, run remote commands or perform privilege escalation.

**Investigative actions**

* Check if any other suspicious activities happened under the same causality.
* Confirm the PsExec.exe command is benign.

</details>

<details>

<summary>PsExec was executed with a suspicious command line</summary>

**Synopsis**

| Field             | Value                                                                  |
| ----------------- | ---------------------------------------------------------------------- |
| ATT\&CK Tactic    | Execution (TA0002), Privilege Escalation (TA0004)                      |
| ATT\&CK Technique | System Services: Service Execution (T1569.002), Valid Accounts (T1078) |
| Severity          | Low                                                                    |

**Description**

PsExec.exe was executed with NT/System privilege level.

**Attacker's Goals**

An adversary may attempt to use PsExec to gain execution capabilities, run remote commands or perform privilege escalation.

**Investigative actions**

* Check if any other suspicious activities happened under the same causality.
* Confirm the PsExec.exe command is benign.

</details>

<details>

<summary>PsExec was executed with a suspicious command line</summary>

**Synopsis**

| Field             | Value                                                                  |
| ----------------- | ---------------------------------------------------------------------- |
| ATT\&CK Tactic    | Execution (TA0002), Privilege Escalation (TA0004)                      |
| ATT\&CK Technique | System Services: Service Execution (T1569.002), Valid Accounts (T1078) |
| Severity          | Low                                                                    |

**Description**

PsExec.exe was executed with plain-text credentials.

**Attacker's Goals**

An adversary may attempt to use PsExec to gain execution capabilities, run remote commands or perform privilege escalation.

**Investigative actions**

* Check if any other suspicious activities happened under the same causality.
* Confirm the PsExec.exe command is benign.

</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/psexec-was-executed-with-a-suspicious-command-line.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.
