> 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/image-file-execution-options-ifeo-registry-key-set.md).

# Image file execution options (IFEO) registry key set

### 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)                                  |
| ATT\&CK Tactic       | Privilege Escalation (TA0004), Persistence (TA0003)                           |
| ATT\&CK Technique    | Event Triggered Execution: Image File Execution Options Injection (T1546.012) |
| Severity             | Low                                                                           |

### Description

Attackers may use the Image File Execution Options Registry key to launch their executable whenever the user attempts to execute a certain executable.

### Attacker's Goals

Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by Image File Execution Options debuggers.

### Investigative actions

* Check whether the executing process is benign and if this was a desired behavior as part of its normal execution flow.
* Look at the debugged process and what it is executing to determine if it is malicious.

### Variations

<details>

<summary>Image file execution options (IFEO) registry key set to execute a shell or scripting engine process</summary>

**Synopsis**

| Field             | Value                                                                         |
| ----------------- | ----------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Privilege Escalation (TA0004), Persistence (TA0003)                           |
| ATT\&CK Technique | Event Triggered Execution: Image File Execution Options Injection (T1546.012) |
| Severity          | High                                                                          |

**Description**

Attackers may use the Image File Execution Options Registry key to launch their executable whenever the user attempts to execute a certain executable.

**Attacker's Goals**

Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by Image File Execution Options debuggers.

**Investigative actions**

* Check whether the executing process is benign and if this was a desired behavior as part of its normal execution flow.
* Look at the debugged process and what it is executing to determine if it is malicious.

</details>

<details>

<summary>Image file execution options (IFEO) registry key set to activate Windows licenses illegally</summary>

**Synopsis**

| Field             | Value                                                                         |
| ----------------- | ----------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Privilege Escalation (TA0004), Persistence (TA0003)                           |
| ATT\&CK Technique | Event Triggered Execution: Image File Execution Options Injection (T1546.012) |
| Severity          | Medium                                                                        |

**Description**

Attackers may use the Image File Execution Options Registry key to launch their executable whenever the user attempts to execute a certain executable. This is also used by tools that were made to activate Windows licenses illegally.

**Attacker's Goals**

Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by Image File Execution Options debuggers.

**Investigative actions**

* Check whether the executing process is benign and if this was a desired behavior as part of its normal execution flow.
* Look at the debugged process and what it is executing to determine if it is malicious.

</details>

<details>

<summary>Image file execution options (IFEO) registry key set using reg.exe</summary>

**Synopsis**

| Field             | Value                                                                         |
| ----------------- | ----------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Privilege Escalation (TA0004), Persistence (TA0003)                           |
| ATT\&CK Technique | Event Triggered Execution: Image File Execution Options Injection (T1546.012) |
| Severity          | High                                                                          |

**Description**

Attackers may use the Image File Execution Options Registry key to launch their executable whenever the user attempts to execute a certain executable.

**Attacker's Goals**

Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by Image File Execution Options debuggers.

**Investigative actions**

* Check whether the executing process is benign and if this was a desired behavior as part of its normal execution flow.
* Look at the debugged process and what it is executing to determine if it is malicious.

</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/image-file-execution-options-ifeo-registry-key-set.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.
