web service security n.
Skip this Video
Loading SlideShow in 5 Seconds..
WEB SERVICE SECURITY PowerPoint Presentation
Download Presentation


160 Views Download Presentation
Download Presentation


- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. WEB SERVICE SECURITY Lecturer: TrầnThịQuếNguyệt Students: TrầnTrúcGiang NguyễnThịHòaBình

  2. Outline • Web Service Introduction • XACML • SAML • Shibboleth

  3. Web Service Introduction

  4. Web Service Introduction • Service-Oriented architecture (SOA) • Web service definition • Web Service Description Language (WSDL) • Simple Object Access Protocol (SOAP) • Universal Description, Discovery and Integration (UDDI)

  5. Service-Oriented architecture (SOA) • • SOA is a mechanism that enables organizations to facilitate communication between the systems running on multiple platforms • SOA is a collection of well-defined services, each individual service can be modified independently of other services to help respond to the ever-evolving market conditions of a business • SOA presents the big picture of what you can do with web services

  6. SOA’s Components

  7. What are Web Services? • W3C’s Definition: a software system designed to support interoperable machine-to-machine interaction over a network. • Web services: • application components • communicate using open protocols • self-contained and self-describing • can be discovered using UDDI • can be used by other applications • XML is the basis for Web services

  8. Web services platform elements • SOAP (Simple Object Access Protocol) • UDDI (Universal Description, Discovery and Integration) • WSDL (Web Services Description Language)

  9. SOAP (Simple Object Access Protocol) • SOAP is an XML-based protocol to let applications exchange information over HTTP. • Or more simple: SOAP is a protocol for accessing a Web Service.

  10. WSDL (Web Services Description Language) • WSDL is an XML-based language for locating and describing Web services. • WSDL file: <?xml version="1.0" encoding="utf-8" ?> - <definitions xmlns:s="“ ..... xmlns=""> + <types> + <message name=“addSoapIn"> + <message name=“addSoapOut"> + <portType name=“TestWSSoap"> + <binding name=“TestWSSoap" type=“TestWSSoap"> + <service name="TestWS"> </definitions>

  11. UDDI (Universal Description, Discovery and Integration) • UDDI is a directory service where companies can register and search for Web services

  12. Security Requirements for SOAP-based Web Services

  13. Security Requirements for SOAP-based Web Services

  14. Security Requirements for SOAP-based Web Services

  15. XML Security for Web Services • The XML Signature specification is a joint effort of W3C and IETF. It aims to provide data integrity and authentication (both message and signer authentication) features, wrapped inside XML format. • W3C's XML Encryption specification addresses the issue of data confidentiality using encryption techniques. Encrypted data is wrapped inside XML tags defined by the XML Encryption specification. • WS-Security from OASIS defines the mechanism for including integrity, confidentiality, and single message authentication features within a SOAP message. WS-Security makes use of the XML Signature and XML Encryption specifications and defines how to include digital signatures, message digests, and encrypted data in a SOAP message.

  16. XML Security for Web Services • Security Assertion Markup Language (SAML) • eXtensible Access Control Markup Language (XACML)

  17. Outline • Web Service Introduction • XACML • SAML • Shibboleth

  18. The eXtensible Access Control Markup Language (XACML)

  19. XACML • The eXtensible Access Control Markup Language (XACML) is an XML vocabulary for expressing access control policies. • Access control consists of deciding if a requested resource access should be allowed and enforcing that decision. • Access control policies are the criteria for making access control decisions. • The XACML core specification defines the syntax of the language and the rules for evaluating policies.

  20. Preferred terms

  21. Preferred terms

  22. Preferred terms • Resource: Data, service or system component. • Subject: An actor whose attributes may be referenced by a predicate. • Action • An operation on a resource. • Four kinds of actions: read, write, create, and delete. • Environment: The set of attributes that are relevant to an authorization decision and are independent of a particular subject, resource or action.

  23. Preferred terms • Attribute: Characteristic of a subject, resource, action or environment that may be referenced in a predicate or target. • Context: The canonical representation of a decision request and an authorization decision. • Context handler: The system entity that converts decision requests in the native request format to the XACML canonical form and converts authorization decisions in the XACML canonical form to the native response format.

  24. Data-flow Diagram

  25. Data-flow diagram

  26. Data-flow diagram

  27. Data-flow diagram

  28. Data-flow diagram

  29. Data-flow diagram

  30. Data-flow diagram

  31. Data-flow diagram

  32. Data-flow diagram

  33. Data-flow diagram

  34. Data-flow diagram

  35. Data-flow diagram

  36. Data-flow diagram

  37. Data-flow diagram

  38. Data-flow diagram

  39. XACML - Advantages • According to Sun, XACML has a number of advantages over other access-control policy languages: • One standard access control policy language can replace dozens of application-specific languages • Administrators save time and money because they don't need to rewrite their policies in many different languages • Developers save time and money because they don't have to invent new policy languages and write code to support them. They can reuse existing code

  40. XACML - Advantages • Good tools for writing and managing XACML policies will be developed, since they can be used with many applications • XACML is flexible enough to accommodate most access control policy needs and extensible so that new requirements can be supported. • One XACML policy can cover many resources. This helps avoid inconsistent policies on different resources. • XACML allows one policy to refer to another. This is important for large organizations. For instance, a site-specific policy may refer to a company-wide policy and a country-specific policy.

  41. XACML - Limitations • XACML is verbose and complex in some ways. • Interactions involving PAP, PIP, etc., are not standardized. • Policy administration, policy versioning, etc., are not standardized.

  42. SAML Security Assertions Markup Language

  43. Single Sign-on (SSO) • SSO is a property of access control of multiple, related, but independent software systems. • With this property a user • logs in once • gains access to all systems without being prompted to log in again at each of them.

  44. Why choose single sign-on? • User needs to remember multiple usernames and passwords to access different applications on a network. • This poses a huge cost for the administration and support departments. • Authentication is a horizontal requirement across multiple applications, platforms, and infrastructures.

  45. Why choose single sign-on? • The objective of SSO • Allow users access to all applications from one logon. • Provide a unified mechanism to manage the authentication of users and implement business rules determining user access to applications and data. • Benefits include the following: • Improved user productivity. • Improved developer productivity. • Simplified administration.

  46. Implementing SSO requires • Identity Provider (IdP): The system, or administrative domain, that asserts information about a subject. • Service Provider (SP): The system, or administrative domain, that relies on information supplied to it by the Identity Provider. It is up to the Service Provider as to whether it trusts the assertions provided to it. • Exchanges of authentication and authorization data between an IdP and an SP are effected by means of an XML standard called the Security Assertion Markup Language (SAML).

  47. SAML - Introduction • The Security Assertion Markup Language (SAML) standard defines a framework for exchanging security information between online business partners. • As stated in the SSTC charter, the purpose of the Technical Committee is: • to define, enhance, and maintain a standard XML-based framework • for creating andexchanging authentication and authorization information.

  48. SAML – Use case • There are four “drivers” behind the creation of the SAML standard: • Limitations of Browser cookies • SSO Interoperability • Web Services • Federation