Software protection and simulation on oblivious RAMs
Journal of the ACM (JACM)
AEGIS: architecture for tamper-evident and tamper-resistant processing
ICS '03 Proceedings of the 17th annual international conference on Supercomputing
Architectural support for copy and tamper-resistant software
Architectural support for copy and tamper-resistant software
Architecture for Protecting Critical Secrets in Microprocessors
Proceedings of the 32nd annual international symposium on Computer Architecture
Hardware-rooted trust for secure key management and transient trust
Proceedings of the 14th ACM conference on Computer and communications security
Proceedings of the 13th international conference on Architectural support for programming languages and operating systems
Flicker: an execution infrastructure for tcb minimization
Proceedings of the 3rd ACM SIGOPS/EuroSys European Conference on Computer Systems 2008
Proceedings of the 2012 ACM conference on Computer and communications security
OASIS: on achieving a sanctuary for integrity and secrecy on untrusted platforms
Proceedings of the 2013 ACM SIGSAC conference on Computer & communications security
| Hi-index | 0.02 |
Vulnerabilities in complex software are a major threat to the security of today's computer systems, with the alarming prevalence of malware and rootkits making it difficult to guarantee security in a networked environment. Due to the widespread application of information technology to all aspects of society, these vulnerabilities threaten virtually all aspects of modern life. To protect software and data against these threats, we describe simple extensions to the Power Architecture for running Secure Executables. By using a combination of cryptographic techniques and context labeling in the CPU, these Secure Executables are protected on disk, in memory, and through all stages of execution against malicious or compromised software, and other hardware. Moreover, we show that this can be done efficiently, without significant performance penalty. Secure Executables can run simultaneously with unprotected executables; existing applications can be transformed directly into Secure Executables without changes to the source code.