> 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/a-suspicious-direct-syscall-was-executed.md).

# A suspicious direct syscall was executed

### 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 with eXtended Threat Hunting (XTH) |
| Detector Tags        | Direct Syscall Analytics                     |
| ATT\&CK Tactic       | Execution (TA0002)                           |
| ATT\&CK Technique    | Native API (T1106)                           |
| Severity             | Low                                          |

### Description

A suspicious direct syscall was executed.

### Attacker's Goals

An attacker might try to use direct syscalls to evade detection from a legitimate program.

### Investigative actions

* Investigate the direct syscall-mapped image to verify if it is malicious.
* Check if this direct syscall is part of the process execution flow.

### Variations

<details>

<summary>A suspicious direct syscall was executed by unsigned process from a user folder</summary>

**Synopsis**

| Field             | Value              |
| ----------------- | ------------------ |
| ATT\&CK Tactic    | Execution (TA0002) |
| ATT\&CK Technique | Native API (T1106) |
| Severity          | High               |

**Description**

A suspicious direct syscall was executed by unsigned process from a user folder.

**Attacker's Goals**

An attacker might try to use direct syscalls to evade detection from a legitimate program.

**Investigative actions**

* Investigate the direct syscall-mapped image to verify if it is malicious.
* Check if this direct syscall is part of the process execution flow.

</details>

<details>

<summary>A suspicious direct syscall was executed by a DLL host application</summary>

**Synopsis**

| Field             | Value              |
| ----------------- | ------------------ |
| ATT\&CK Tactic    | Execution (TA0002) |
| ATT\&CK Technique | Native API (T1106) |
| Severity          | Medium             |

**Description**

A suspicious direct syscall was executed by a DLL host application.

**Attacker's Goals**

An attacker might try to use direct syscalls to evade detection from a legitimate program.

**Investigative actions**

* Investigate the direct syscall-mapped image to verify if it is malicious.
* Check if this direct syscall is part of the process execution flow.

</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/a-suspicious-direct-syscall-was-executed.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.
