ACM Home Page
Please provide us with feedback. Feedback
Verifying policy-based web services security
Full text PdfPdf (841 KB)
Source
ACM Transactions on Programming Languages and Systems (TOPLAS) archive
Volume 30 ,  Issue 6  (October 2008) table of contents
Article No. 30  
Year of Publication: 2008
ISSN:0164-0925
Authors
Karthikeyan Bhargavan  Microsoft Research, Cambridge, United Kingdom
Cédric Fournet  Microsoft Research, Cambridge, United Kingdom
Andrew D. Gordon  Microsoft Research, Cambridge, United Kingdom
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 58,   Downloads (12 Months): 582,   Citation Count: 0
Additional Information:

abstract   references   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/1391956.1391957
What is a DOI?

ABSTRACT

WS-SecurityPolicy is a declarative language for configuring web services security mechanisms. We describe a formal semantics for WS-SecurityPolicy and propose a more abstract language for specifying secure links between web services and their clients. We present the architecture and implementation of tools that (1) compile policy files from link specifications, and (2) verify by invoking a theorem prover whether a set of policy files run by any number of senders and receivers correctly implements the goals of a link specification, in spite of active attackers. Policy-driven web services implementations are prone to the usual subtle vulnerabilities associated with cryptographic protocols; our tools help prevent such vulnerabilities. We can verify policies when first compiled from link specifications, and also re-verify policies against their original goals after any modifications during deployment. Moreover, we present general security theorems for all configurations that rely on compiled policies.


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
 
4
 
5
Bhargavan, K., Fournet, C., and Gordon, A. D. 2005b. Verifying policy-based security for web services. Tech. Rep. MSR--TR--2004--84, Microsoft Research. Nov.
 
6
Bhargavan, K., Fournet, C., and Gordon, A. D. 2006b. Policy advisor for WSE 3.0. In Web Service Security: Scenarios, patterns, and implementation guidance for Web Services Enhancements (WSE) 3.0. Microsoft Press, 324--330.
 
7
Bhargavan, K., Fournet, C., and Gordon, A. D. 2006c. Verified reference implementations of WS-Security protocols. In Proceedings of the 3rd International Workshop on Web Services and Formal Methods (WS-FM 2006). Lecture Notes in Computer Science, vol. 4184. Springer-Verlag, New York, 88--106.
8
 
9
Bhargavan, K., Fournet, C., Gordon, A. D., and Pucella, R. 2004. TulaFale: A security tool for web services. In Proceedings of the International Symposium on Formal Methods for Components and Objects (FMCO'03). Lecture Notes in Computer Science, vol. 3188. Springer-Verlag, New York, 197--222. Tool download available from http://Securing.WS.
10
 
11
 
12
 
13
 
14
 
15
Box, D., Christensen, E., Curbera, F., Ferguson, D., Frey, J., Hadley, M., Kaler, C., Langworthy, D., Leymann, F., Lovering, B., Lucco, S., Millet, S., Mukhi, N., Nottingham, M., Orchard, D., Shewchuk, J., Sindambiwe, E., Storey, T., Weerawarana, S., and Winkler, S. 2004. Web Services Addressing (WS-Addressing). W3C Submission.
 
16
Box, D., Curbera, F., Hondo, M., Kaler, C., Langworthy, D., Nadalin, A., Nagaratnam, N., Nottingham, M., von Riegen, C., and Shewchuk, J. 2003a. Web services policy framework (WS-Policy).
 
17
Box, D., Hondo, M., Kaler, C., Maruyama, H., Nadalin, A., Nagaratnam, N., Patrick, P., von Riegen, C., and Shewchuk, J. 2003b. Web services policy assertions language (WS-PolicyAssertions).
 
18
Della-Libera, G., Hallam-Baker, P., Hondo, M., Janczuk, T., Kaler, C., Maruyama, H., Nagaratnam, N., Nash, A., Philpott, R., Prafullchandra, H., Shewchuk, J., Waingold, E., and Zolfonoon, R. 2002. Web services security policy language (WS-SecurityPolicy). Version 1.0.
 
19
Dierks, T. and Rescorla, E. 2006. The Transport Layer Security (TLS) Protocol Version 1.1. RFC 4346, Internet Engineering Task Force Proposed Standard.
 
20
Dolev, D. and Yao, A. 1983. On the security of public key protocols. IEEE Trans. Inform. Theory IT--29, 2, 198--208.
 
21
Eastlake, D., Reagle, J., Imamura, T., Dillaway, B., and Simon, E. 2002a. XML Encryption Syntax and Processing. W3C Recommendation.
 
22
Eastlake, D., Reagle, J., Solo, D., Bartel, M., Boyer, J., Fox, B., LaMacchia, B., and Simon, E. 2002b. XML-Signature Syntax and Processing. W3C Recommendation.
 
23
 
24
 
25
Guttman, J. D. and Herzog, A. L. 2005. Rigorous automated network security management. Int. J. Inform. Secur. 4, 1--2, 29--48.
 
26
Lowe, G. 2002. Analyzing protocols subject to guessing attacks. In Proceedings of the Workshop on Issues in the Theory of Security (WITS'02). Portland, Oregon.
 
27
Lukell, S., Veldman, C., and Hutchison, A. C. M. 2003. Automated attack analysis and code generation in a multi-dimensional security protocol engineering framework. In Proceedings of the Southern African Telecommunication Networks and Applications Conference (SATNAC).
 
28
Microsoft Corporation 2004. Web Services Enhancements (WSE) 2.0. Microsoft Corporation.
 
29
Muller, F. and Millen, J. 2001. Cryptographic protocol generation from CAPSL. Tech. Rep. SRI--CSL--01--07, SRI.
 
30
Nadalin, A., Griffin, P., Kaler, C., Hallam-Baker, P., and Monzillo, R. 2004a. Web Services Security: UsernameToken Profile 1.0. OASIS Standard.
 
31
Nadalin, A., Kaler, C., Hallam-Baker, P., and Monzillo, R. 2004b. Web Services Security: SOAP Message Security 1.0 (WS-Security 2004). OASIS Standard.
 
32
Nadalin, A., Kaler, C., Hallam-Baker, P., and Monzillo, R. 2006. Web Services Security: SOAP Message Security 1.1 (WS-Security 2004). OASIS Standard.
 
33
Nadalin, A., Goodner, M., Gudgin, M., Barbir, A., and Granqvist, H. 2007. WS-SecurityPolicy 1.2. OASIS Standard.
34
 
35
 
36
 
37
 
38
W3C. 1999. XML Path Language (XPath) Version 1.0. W3C. W3C Recommendation.
 
39
W3C. 2003. SOAP Version 1.2. W3C. W3C Recommendation.
 
40
 
41

Collaborative Colleagues:
Karthikeyan Bhargavan: colleagues
Cédric Fournet: colleagues
Andrew D. Gordon: colleagues