Optimistic security: a new access control paradigm
Proceedings of the 1999 workshop on New security paradigms
Characterizing the behavior of a program using multiple-length N-grams
Proceedings of the 2000 workshop on New security paradigms
Model-Carrying Code (MCC): a new paradigm for mobile-code security
Proceedings of the 2001 workshop on New security paradigms
Windows NT/2000 Native API Reference
Windows NT/2000 Native API Reference
Access rights analysis for Java
OOPSLA '02 Proceedings of the 17th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
A Sense of Self for Unix Processes
SP '96 Proceedings of the 1996 IEEE Symposium on Security and Privacy
Model-carrying code: a practical approach for safe execution of untrusted applications
SOSP '03 Proceedings of the nineteenth ACM symposium on Operating systems principles
Gray-box extraction of execution graphs for anomaly detection
Proceedings of the 11th ACM conference on Computer and communications security
On gray-box program tracking for anomaly detection
SSYM'04 Proceedings of the 13th conference on USENIX Security Symposium - Volume 13
Intrusion detection using sequences of system calls
Journal of Computer Security
Reusability of Functionality-Based Application Confinement Policy Abstractions
ICICS '08 Proceedings of the 10th International Conference on Information and Communications Security
| Hi-index | 0.02 |
The well-known Principle of Least Privilege states that a program should run with the minimal authority that it requires to get the job done, and no more. However, application of the principle has been left to software developers, developers of installation procedures, and system administrators with few tools to assist them. How much privilege does a given program need? How do you know if you write a program that uses too much privilege or install a program with too little? Empirical privilege profiling provides a partial answer to this question by tracking a program's actual use of resources, which can be used as a guide during program development and installation, as well as for detecting intrusions and providing assurance for mobile code. In this paper, we introduce the concept of dealing with privilege as a measurable quantity, rather than in terms of a "rule of thumb."