pith. sign in

arxiv: 1812.09920 · v1 · pith:CDESQSHGnew · submitted 2018-12-24 · 💻 cs.CR · cs.OS

Divide et Impera: MemoryRanger Runs Drivers in Isolated Kernel Spaces

classification 💻 cs.CR cs.OS
keywords driversdatacodememoryrangersecurityexecutingfeatureskernel
0
0 comments X
read the original abstract

One of the main issues in the OS security is to provide trusted code execution in an untrusted environment. During executing, kernel-mode drivers allocate and process memory data: OS internal structures, users private information, and sensitive data of third-party drivers. All this data and the drivers code can be tampered with by kernel-mode malware. Microsoft security experts integrated new features to fill this gap, but they are not enough: allocated data can be stolen and patched and the drivers code can be dumped without any security reaction. The proposed hypervisor-based system (MemoryRanger) tackles this issue by executing drivers in separate kernel enclaves with specific memory attributes. MemoryRanger protects code and data using Intel VT-x and EPT features with low performance degradation on Windows 10 x64.

This paper has not been read by Pith yet.

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.