ACM Home Page
Please provide us with feedback. Feedback
Combining type-based analysis and model checking for finding counterexamples against non-interference
Full text PdfPdf (240 KB)
Source Conference on Programming Language Design and Implementation archive
Proceedings of the 2006 workshop on Programming languages and analysis for security table of contents
Ottawa, Ontario, Canada
SESSION: Finding security flaws table of contents
Pages: 17 - 26  
Year of Publication: 2006
ISBN:1-59593-374-3
Authors
Hiroshi Unno  University of Tokyo
Naoki Kobayashi  Tohoku University
Akinori Yonezawa  University of Tokyo
Sponsors
SIGPLAN: ACM Special Interest Group on Programming Languages
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 3,   Downloads (12 Months): 32,   Citation Count: 1
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1134744.1134750
What is a DOI?

ABSTRACT

Type systems for secure information flow are useful for efficiently checking that programs have secure information flow. They are, however, conservative, so that they often reject safe programs as ill-typed. Accordingly, users have to check whether the rejected programs indeed have insecure flows. To remedy this problem, we propose a method for automatically finding a counterexample of secure information flow (input states that actually lead to leakage of secret information). Our method is a novel combination of type-based analysis and model checking; Suspicious execution paths (that may cause insecure information flow) are first found by using the result of a type-based information flow analysis, and then a model checker is used to check whether the paths are indeed unsafe. We have formalized and implemented the method. The result of preliminary experiments shows that our method can often find counterexamples faster than a method using a model checker alone.


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
2
 
3
J. A. Goguen and J. Meseguer. Security policies and security models. In IEEE Symposium on Security and Privacy, pages 11--20, 1982.
4
5
6
 
7
 
8
9
 
10
A. C. Myers, N. Nystrom, L. Zheng, and S. Zdancewic. Jif: Java information flow. http://www.cs.cornell.edu/jif, July 2001.
 
11
12
 
13
Y. Oiwa, S. Tatsurou, S. Eijiro, and Y. Akinori. Fail-safe ANSI-C compiler: An approach to making C programs secure: Progress report. In In International Symposium on Software Security, number 2609 in LNCS, pages 133--153. Springer-Verlag, 2002.
14
15
 
16
V. Simonet. Flow Caml in a nutshell. In G. Hutton, editor, Proceedings of the first APPSEM-II workshop, pages 152--165, Nottingham, United Kingdom, March 2003.
17
 
18
T. Terauchi and A. Aiken. Secure information flow as a safety problem. In In Proceedings of the 12th International Static Analysis Symposium, September 2005.
 
19
H. Unno, N. Kobayashi, and A. Yonezawa. Combining type-based analysis and model checking for finding counterexamples against non-interference Full version, February 2006. Available from http://web.yl.is.s.u-tokyo.ac.jp/~uhiro/.
 
20
 
21


Collaborative Colleagues:
Hiroshi Unno: colleagues
Naoki Kobayashi: colleagues
Akinori Yonezawa: colleagues