> For the complete documentation index, see [llms.txt](https://notes.qazeer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://notes.qazeer.io/dfir/windows/ttps_analysis/program_execution.md).

# Program execution

**Windows DFIR notes are no longer maintained on InfoSec-Notes. Updated versions can be found on:** [**artefacts.help**](https://artefacts.help/)**.**

### Security.evtx - 4688: A new process has been created

Event: `4688: A new process has been created`.\
Location: victim `Security` hive.\
Requires `Audit Process Creation` to be enabled.

This event is logged upon the creation of every new process on the system.

The `NewProcessName` field stores the full path of the process's executable and the `ProcessId` field the `Process ID (PID)` of the process. The `ParentProcessName` field logs the parent process's executable full path and can be used to identity suspicious processes activity, such as `outlook.exe` or `iexplorer.exe` starting `cmd.exe` or `powershell.exe` processes.

This event includes the SID `SubjectUserSid`, account name `SubjectUserName`, and domain `SubjectDomainName` of the user creating the process. Additionally, the `SubjectLogonId` field can be used to correlate the process creation with the logon session, event `EID: 4624`.

The `TokenElevationType` field represent the privileges of the process and can take the following values:

| Flag     | Correspondence              | Description                                                                                                                                                                                                                                                                               |
| -------- | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `%%1936` | `TokenElevationTypeDefault` | The process is started with a full token with no privileges removed or groups disabled. A full token is only used if `User Account Control (UAC)` is disabled or if the user starting the process is the built-in `Administrator` (`RID: 500`), `NT AUTHORITY\SYSTEM` or service account. |
| `%%1937` | `TokenElevationTypeFull`    | The process is started with an elevated token with no privileges removed or groups disabled. An elevated token is used when `User Account Control (UAC)` is enabled and the user chooses to start the program in a elevated security context (`Run as administrator` for example).        |
| `%%1938` | `TokenElevationTypeLimited` | The process is started with limited privileges, and privileged tokens such as `SeImpersonatePrivilege`, `SeDebugPrivilege`, etc. are removed from the process security context.                                                                                                           |

If the `ProcessCreationIncludeCmdLine_Enabled` audit policy is enabled, the command line specified at the process creation will be logged in the `ProcessCommandLine` field.

This event is followed by the `Security` event `4689: Process Termination: Success and Failure` upon the termination of the process.

### Artefacts

For an overview of the artefacts related to programs execution (`SRUM`, `UserAssist`, `BAM` / `DAM`, `Shimcache`, `Amcache`, `Prefetch`, ...), refer to the [artefacts overview note](/dfir/windows/_artefacts_overview.md).

***

### References

<https://digital-forensics.sans.org/media/dfir\\_poster\\_2014.pdf> <https://www.ultimatewindowssecurity.com/securitylog/encyclopedia/event.aspx?eventID=4688>


---

# 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://notes.qazeer.io/dfir/windows/ttps_analysis/program_execution.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.