1 / 16

WS Security Roadmap: Enhancing Web Services Security with IBM and Microsoft

Learn about the WS Security Roadmap proposed by IBM and Microsoft to establish secure and interoperable Web services, including specifications, policies, trust models, and privacy mechanisms.

janinelong
Télécharger la présentation

WS Security Roadmap: Enhancing Web Services Security with IBM and Microsoft

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. WS Security Roadmap Dave Tran CSCI5931 Web Security WS Security Roadmap Proposed by IBM and Microsoft

  2. WS Security Roadmap • What is a Web Service? “… application components whose functionality and interfaces are exposed to potential users through the application of existing and emerging Web technology standards including XML, SOAP, WSDL, and HTTP.” • Why? • Loosely-coupled • Language-neutral • Platform-independent

  3. WS Security Roadmap • Bottlenecks? security • SSL/TLS not enough? • Point-to-point (2 parties involve) • WS is end-to-end (more than 3 parties involve)

  4. WS Security Roadmap

  5. WS Security Roadmap

  6. WS Security Roadmap • Initial Specifications • provide the foundation to establish secure interoperable Web services across trust domains. • Message Layer • WS-Security - message security model • Policy Layer • WS-Policy - Web service endpoint policy • WS-Trust - a trust model • WS-Privacy - privacy model

  7. WS Security Roadmap • Follow-on Specifications • Federation Layer • WS-SecureConversation – secure conversations • WS-Federation – federated trust • WS-Authorization - authorization

  8. WS Security Roadmap • WS-Security • Enhance SOAP messaging by providing quality of protection through message integrity and message confidentiality. • Authentication with Security tokens – username and passwords, Kerberos tickets, X.509 certificate • Message integrity – XML Signature with security tokens • Message confidentiality – XML Encryption with security tokens

  9. WS Security Roadmap • WS-Policy • Defines the policy rules on how services interact • Includes 4 specs • A Policy Framework(WS-Policy) - defines a grammar for expressing WS policies • A Policy Attachment (WS-Policy-Attachment) - defines how to attach these policies to WS • A set of general policy assertions (WS-Policy-Assertions) • A set of security policy assertions (WS-Security Policy)

  10. WS Security Roadmap • WS-Trust • The trust between a service requester and a service provider is established through the exchange of information between the two parties in an expected and understood manner • WS-Security already defines the basic mechanisms to securely exchange messages using security tokens • Builds on top of WS-Security and defines how the security tokens are issued and exchanged • Defines a set of interfaces that a secure token service may provide for the issuance, exchange, and validation of security tokens

  11. WS Security Roadmap • WS-Privacy defines how privacy of information is maintained

  12. WS Security Roadmap • WS-SecureConversation • Builds on the concept of trust based on security tokens • Defines how to establish a secured session between services for exchanging data using the rules defined in WS-Policy, WS-Trust, and WS-Privacy • Defines how to create a context for a particular conversation with a Web Service and how to create keys that can be used in that context

  13. WS Security Roadmap • WS-Federation • Describes how to manage and broker trust relationships (trust of identities, attributes, and authentication) in a heterogeneous federated environment (among Web Services) leading Single Sign-On. • Comprise of the following: • WS-Federation: Active Requestor Profile - defines mechanisms for requesting, exchanging, and issuing security tokens within the context of active requestors (an application capable of issuing WS messages). • WS-Federation (Language) - defines how federation works in the WS-Security stack. • WS-Federation: Passive Requestor Profile (HTTP browser) - defines a system for passive mechanisms to work seamlessly with a single or simplified sign-on to the WS-Federation system.

  14. WS Security Roadmap • WS-Authorization • Describes how access policies for a Web Service are specified and managed. • Describes how claims may be specified within security tokens and how these claims will be interpreted at the endpoint.

  15. WS Security Roadmap • July 2003VeriSign/IBM/Microsoft/RSA/BEA WS-Federation Specification VeriSign/IBM/Microsoft/RSA/BEA WS-Federation Active Client ProfileVeriSign/IBM/Microsoft/RSA/BEA WS-Federation Passive Client Profile December 2002VeriSign/IBM/Microsoft/RSA WS-SecurityPolicy SpecificationVeriSign/IBM/Microsoft/RSA WS-Trust SpecificationVeriSign/IBM/Microsoft/RSA WS-SecureConversation SpecificationRelated SpecificationsIBM/Microsoft/BEA/SAP WS-PolicyIBM/Microsoft/BEA/SAP WS-PolicyAttachmentIBM/Microsoft/BEA/SAP WS-PolicyAssertionsAugust 2002VeriSign/IBM/Microsoft WS-Security AddendumApril 2002VeriSign/IBM/Microsoft WS-Security SpecificationIBM-Microsoft Web Services Roadmap

  16. WS Security Roadmap • References www.verisign.com/wss http://www-106.ibm.com/developerworks/library/ws-secmap/ http://www-106.ibm.com/developerworks/library/ws-secroad/

More Related