Towards securing XML Web services

Ernesto Damiani, Sabrina De Capitani di Vimercati, Pierangela SamaratiXml Security 2002 · DOI

TL;DR

This paper explores the critical security challenges facing XML Web services, which lack inherent security in their foundational specifications. It reviews existing approaches like SSL and firewalls, but argues for more integrated solutions using XML-specific standards like XML Signature and Encryption, and leveraging SOAP headers for credential transfer and access control.

What Problem Does This Paper Address?

XML Web services, built on technologies like XML, SOAP, WSDL, and HTTP, have become a powerful paradigm for developing complex web applications. However, their underlying specifications were designed without security in mind. This leaves a significant gap in protecting these services from unauthorized access and ensuring the integrity and confidentiality of the XML messages exchanged. The paper highlights two main security concerns: restricting access to authorized users and safeguarding the confidentiality and integrity of XML messages during transit. While traditional security measures like SSL and firewalls offer some protection, they are often considered insufficient or not optimally suited for the unique characteristics of XML-based web services and the SOAP protocol.

Methods

The paper delves into several approaches for securing XML Web services:

  • W3C XML Signature Syntax and Processing: This standard allows for digitally signing portions of an XML document, including entire subtrees or individual elements. It provides mechanisms for creating and verifying digital signatures and embedding them within XML documents. This ensures message integrity and authenticity.
  • W3C XML Encryption Syntax and Processing: This standard enables the encryption of XML message contents, allowing for granular control over which parts of a document are protected. This ensures message confidentiality.
  • Leveraging SOAP Headers: The paper emphasizes the role of SOAP headers in carrying security-related metadata. This includes:
  • Credential Transfer: Proposals like the one by Damiani et al. [9] suggest using custom SOAP headers to carry user credentials (like hashed passwords) and role information, along with certificates. Microsoft's Web Services Security Language (WS-Security) [2] also utilizes headers for X.509 certificates and Kerberos tickets.
  • Access Control: By placing credentials and authorization information in headers, these can be used by a SOAP gateway to enforce access control policies. This allows for fine-grained control over who can access what services and with what permissions.
  • Integration with Policy Languages: The paper touches upon the need for policy languages like Security Assertion Markup Language (SAML) [1] and eXtensible Access Control Markup Language (XACML) [10] to define and evaluate access control rules based on the information present in SOAP headers.

Datasets

Not discussed in the paper.

Key Insights and Ideas

  • XML-native security is crucial: Traditional security mechanisms (SSL, firewalls) are not sufficient for the nuanced security needs of XML Web services. A more integrated, XML-aware approach is necessary.
  • SOAP headers are a powerful tool: SOAP headers provide a flexible and standardized mechanism for carrying security credentials, authorization information, and other metadata, enabling more sophisticated access control and authentication.
  • Granular security is achievable: Both XML Signature and XML Encryption allow for fine-grained security application, meaning specific parts of an XML document can be signed or encrypted, offering flexibility in how security is applied.
  • The need for a unified infrastructure: While individual standards like XML Signature, XML Encryption, SAML, and XACML are promising, a cohesive security infrastructure for XML Web services requires addressing how these standards can coexist and interoperate effectively.

Key Results

The paper doesn't present quantitative results from experiments. Instead, it provides a conceptual overview and comparison of different approaches to securing XML Web services. The key "results" are the identification of the limitations of existing security methods and the proposal of a more integrated approach using XML-specific standards and SOAP headers. The paper highlights the potential of these methods to provide:

  • Message Integrity: Through digital signatures.
  • Message Confidentiality: Through encryption.
  • Authentication and Access Control: Through the use of credentials and policies carried in SOAP headers.

Limitations and Future Work

The authors acknowledge that while standards like XML Signature and Encryption are valuable, establishing a global security infrastructure for XML Web services still faces challenges. These include:

  • Coexistence and Interoperability: The need to effectively integrate and manage the relationships between various, sometimes overlapping, security standards and proposals.
  • Policy Administration and Evaluation: Developing robust mechanisms for defining and evaluating security policies that leverage the information available in SOAP headers and other environmental metadata.
  • Completeness of Standards: Many of the discussed standards are still in development or not fully realized, requiring further work to become fully adopted and operational.

The paper suggests that future work should focus on building a comprehensive security infrastructure that effectively combines these emerging standards to provide a secure environment for XML Web services.

Summary updated

BibTeX
@inproceedings{damiani2002towards,
  author = {Ernesto Damiani and Sabrina De Capitani di Vimercati and Pierangela Samarati},
  title = {{Towards securing XML Web services}},
  booktitle = {Xml Security},
  year = {2002},
  doi = {10.1145/764792.764806},
}
Figure