ACM Home Page
Please provide us with feedback. Feedback
Composing security policies with polymer
Full text PdfPdf (155 KB)
Source Conference on Programming Language Design and Implementation archive
Proceedings of the 2005 ACM SIGPLAN conference on Programming language design and implementation table of contents
Chicago, IL, USA
SESSION: Domain-specific tools table of contents
Pages: 305 - 314  
Year of Publication: 2005
ISBN:1-59593-056-6
Also published in ...
Authors
Lujo Bauer  Carnegie Mellon University, Pittsburgh, PA
Jay Ligatti  Princeton University, Princeton, NJ
David Walker  Princeton University, Princeton, NJ
Sponsors
SIGPLAN: ACM Special Interest Group on Programming Languages
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 10,   Downloads (12 Months): 105,   Citation Count: 26
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

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

ABSTRACT

We introduce a language and system that supports definition and composition of complex run-time security policies for Java applications. Our policies are comprised of two sorts of methods. The first is query methods that are called whenever an untrusted application tries to execute a security-sensitive action. A query method returns a suggestion indicating how the security-sensitive action should be handled. The second sort of methods are those that perform state updates as the policy's suggestions are followed.The structure of our policies facilitates composition, as policies can query other policies for suggestions. In order to give programmers control over policy composition, we have designed the system so that policies, suggestions, and application events are all first-class objects that a higher-order policy may manipulate. We show how to use these programming features by developing a library of policy combinators.Our system is fully implemented, and we have defined a formal semantics for an idealized subset of the language containing all of the key features. We demonstrate the effectiveness of our system by implementing a large-scale security policy for an email client.


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
M. Abadi and C. Fournet. Access control based on execution history. In 10th Annual Network and Distributed System Security Symposium, 2003.
2
 
3
Apache Software Foundation. Byte Code Engineering Library, 2003. http://jakarta.apache.org/bcel/.
 
4
 
5
L. Bauer, J. Ligatti, and D. Walker. A language and system for composing security policies. Technical Report TR-699-04, Princeton University, Jan. 2004.
6
 
7
 
8
D. Evans and A. Twyman. Flexible policy-directed code safety. In IEEE Security and Privacy, Oakland, CA, May 1999.
9
 
10
 
11
M. Kim, M. Viswanathan, H. Ben-Abdallah, S. Kannan, I. Lee, and O. Sokolsky. Formally specified monitoring of temporal properties. In European Conference on Real-time Systems, York, UK, June 1999.
 
12
I. Lee, S. Kannan, M. Kim, O. Sokolsky, and M. Viswanathan. Run-time assurance based on formal specifications. In International Conference on Parallel and Distributed Processing Techniques and Applications, Las Vegas, NV, June 1999.
 
13
J. Ligatti, L. Bauer, and D. Walker. Edit automata: Enforcement mechanisms for run-time security policies. International Journal of Information Security, 4(1--2):2--16, Feb. 2005.
 
14
 
15
E. Meijer and J. Gough. A technical overview of the Common Language Infrastructure. http://research.microsoft.com/~emeijer/Papers/CLR.pdf.
 
16
A. Petersen. Pooka: A Java email client, 2003. http://www.suberic.net/pooka/.
 
17
J. H. Saltzer and M. D. Schroeder. The protection of information in computer systems. In IEEE 63, 9, pages 1278--1308, Sept. 1975.
18
19
20

CITED BY  26

Collaborative Colleagues:
Lujo Bauer: colleagues
Jay Ligatti: colleagues
David Walker: colleagues