ACM Home Page
Please provide us with feedback. Feedback
Model-Carrying Code (MCC): a new paradigm for mobile-code security
Full text PdfPdf (755 KB)
Source New Security Paradigms Workshop archive
Proceedings of the 2001 workshop on New security paradigms table of contents
Cloudcroft, New Mexico
SESSION: Session 1: creative mathematics table of contents
Pages: 23 - 30  
Year of Publication: 2001
ISBN:1-58113-457-6
Authors
R. Sekar  SUNY at Stony Brook, NY
C. R. Ramakrishnan  SUNY at Stony Brook, NY
I. V. Ramakrishnan  SUNY at Stony Brook, NY
S. A. Smolka  SUNY at Stony Brook, NY
Sponsor
SIGSAC: ACM Special Interest Group on Security, Audit, and Control
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 4,   Downloads (12 Months): 21,   Citation Count: 8
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues   peer to peer  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/508171.508175
What is a DOI?

ABSTRACT

A new approach for ensuring the security of mobile code is proposed. Our approach enables a mobile-code consumer to understand and formally reason about what a piece of mobile code can do; check if the actions of the code are compatible with his/her security policies; and, if so, execute the code. The compatibility-checking process is automated, but if there are conflicts, consumers have the opportunity to refine their policies, taking into account the functionality provided by the mobile code. Finally, when the code is executed, our framework uses runtime-monitoring techniques to ensure that the code does not violate the consumer's (refined) policies.At the heart of our method, which we call model-carrying code (MCC), is the idea that a piece of mobile code comes equipped with an expressive yet concise model of the code's (security-relevant) behavior. The generation of such models can be automated. MCC enjoys several advantages over current approaches to mobile-code security. It protects consumers of mobile code from malicious or faulty code without unduly restricting the code's functionality. Also, it is applicable to the vast majority of code that exists today, which is written in C or C++. This contrasts with previous approaches such as Java 2 security and proof-carrying code, which are either language-specific or are limited to type-safe languages. Finally, MCC can be combined with existing techniques such as cryptographic signing and proof-carrying code to yield additional benefits.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
R Bowen, D Chee, M Segal, R Sekar, P Uppuluri, and T Shanbag. Building survivable systems: An integrated approach based on intrusion detection and confinement. In DARPA Information Security Symposium, 2000.
2
 
3
B. Cui, Y. Dong, X. Du, K. Narayan Kumar, C. R. Ramakrishnan, I. V. Ramakrishnan, A. Roychoudhury, S. A. Smolka, and D. S. Warren. Logic programming and model checking. In Static Analysis Symposium. Springer Verlag, 1998.
 
4
S Forrest, S Hofmeyr, and A Somayaji. Intrusion detection using sequences of system calls. Journal of Computer Security, 1998.
 
5
 
6
 
7
K Jain and R Sekar. User-level infrastructure for system call interposition: A platform for intrusion detection and confinement. In ISOC Network and Distributed System Security, 2000.
 
8
C Ko, G Fink, and K Levitt. Automated detection of vulnerabilities in privileged programs by execution monitoring. In Computer Security Application Conference, 1994.
 
9
 
10
 
11
12
13
 
14
15
 
16
17
 
18
 
19
R. Sekar and P. Uppuluri. Synthesizing fast intrusion prevention/detection systems from high-level specifications. In USENIX Security Symposium, 1999.
 
20
 
21
XSB. The XSB tabled logic programming system. Available from http://xsb.sourceforge.net.


Collaborative Colleagues:
R. Sekar: colleagues
C. R. Ramakrishnan: colleagues
I. V. Ramakrishnan: colleagues
S. A. Smolka: colleagues

Peer to Peer - Readers of this Article have also read: