Reimagining the Usermode Process Space by Utilizing Hardware-Enforced Sub-Process Isolation

The traditional x86 memory model inherently lacks enforceable trust boundaries, allowing unverified executables and libraries to share process memory. This model assumes the integrity of the operating system and toolchain, yet it remains susceptible to code injection, unauthorized execution, and privilege escalation attacks. This position paper proposes a hardware-enforced, sub-process isolation model that mandates digitally signed executables, ensuring runtime verification and execution integrity. We introduce a Trust-by-Choice execution framework, enabling executables to dynamically assess and regulate dependencies, mitigating supply chain threats. Additionally, we introduce compiler-assisted memory isolation by integrating Trusted Execution Environments (TEEs) into the $\mathbf{C}$ toolchain, enhancing confidentiality and integrity while also suppressing arbitrary code execution between executable modules. Finally, we introduce Share-by-default and Share-by-Choice models of data isolation. By embedding trust enforcement into hardware, our approach eliminates reliance on OS-based security, provides least privilege enforcement, and applies zero trust principles at the architectural level. This model provides a scalable, backward-compatible security framework for modern computing environments.

Authors

Institutions

Publication Details

Published
2025-08-04
DOI
https://doi.org/10.1109/csr64739.2025.11130175
Primary Topic
Flexible and Reconfigurable Manufacturing Systems
Type
article
Field-Weighted Citation Impact
0.00
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
article

Reimagining the Usermode Process Space by Utilizing Hardware-Enforced Sub-Process Isolation

Mehdi Mirakhorli, Mark D. Nelson
Flexible and Reconfigurable Manufacturing Systems
article

Reimagining the Usermode Process Space by Utilizing Hardware-Enforced Sub-Process Isolation

Mehdi Mirakhorli, Mark D. Nelson
article en

Abstract

The traditional x86 memory model inherently lacks enforceable trust boundaries, allowing unverified executables and libraries to share process memory. This model assumes the integrity of the operating system and toolchain, yet it remains susceptible to code injection, unauthorized execution, and privilege escalation attacks. This position paper proposes a hardware-enforced, sub-process isolation model that mandates digitally signed executables, ensuring runtime verification and execution integrity. We introduce a Trust-by-Choice execution framework, enabling executables to dynamically assess and regulate dependencies, mitigating supply chain threats. Additionally, we introduce compiler-assisted memory isolation by integrating Trusted Execution Environments (TEEs) into the $\mathbf{C}$ toolchain, enhancing confidentiality and integrity while also suppressing arbitrary code execution between executable modules. Finally, we introduce Share-by-default and Share-by-Choice models of data isolation. By embedding trust enforcement into hardware, our approach eliminates reliance on OS-based security, provides least privilege enforcement, and applies zero trust principles at the architectural level. This model provides a scalable, backward-compatible security framework for modern computing environments.

University of Hawaii System (US)
Openalex Percentile: Top 69%
Flexible and Reconfigurable Manufacturing Systems
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.

Reimagining the Usermode Process Space by Utilizing Hardware-Enforced Sub-Process Isolation — Mehdi Mirakhorli, Mark D. Nelson · (2025) | TGRS Research Map | TGRS