SOA Security Model For EAI


Published on

The project work explores in detail, the security issues in a SOA environment and also describes the various approaches to these issues. The different approaches to SOA security (i.e. message level security, security as a service and policy driven security) are not standalone solutions, but can be deployed as mix and match solutions. A SOA security solution can make use of all the approaches to address specific security concerns. Finally the project work describes a generic SOA security model which acts as a reference model to identify security vulnerabilities in enterprise application integration (EAI). These vulnerabilities can then be addressed by the different approaches to security.

Published in: Technology
1 Comment
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

SOA Security Model For EAI

  1. 1. SOA Security Model for Enterprise Systems Integration Vivek Jonnaganti
  2. 2. Agenda <ul><li>Introduction </li></ul><ul><li>Security requirements of SOA </li></ul><ul><li>Approaches to security </li></ul><ul><li>Unified Web services security </li></ul><ul><li>SOA security model </li></ul><ul><li>Case-study at Agresso </li></ul><ul><li>Conclusion </li></ul>
  3. 3. Introduction These three domains form together a so-called Service-based Business Environment [2]
  4. 4. SOA Example 1: LIBRIS BYGGDOK GU Bibliotek KTH Bibliotek Chalmers Bibliotek Kungl Bibliotek LIBRIS environment (Broker)
  5. 5. SOA Example 2: Google search Google-search environment (Broker + Provider)
  6. 6. Model delineation <ul><li>High flexibility (allows redundancy) </li></ul><ul><li>Low reusability </li></ul><ul><li>Low flexibility (redundancy not allowed) </li></ul><ul><li>High reusability </li></ul>
  7. 7. SOA Enterprise Environment Elements of a SOA, adapted from the CBDI Service Oriented Architecture Practice Portal Web services architecture
  8. 8. Security requirements of SOA: Functional <ul><li>Confidentiality </li></ul><ul><ul><li>Prevent disclosure of information to unauthorized individuals or systems </li></ul></ul><ul><li>Integrity and non-repudiation </li></ul><ul><ul><li>Implies that data cannot be manipulated without authorization </li></ul></ul><ul><li>Authentication </li></ul><ul><ul><li>Process of verifying the identity of users </li></ul></ul><ul><li>Authorization </li></ul><ul><ul><li>Permission to use a resource </li></ul></ul><ul><li>Protection against attacks </li></ul><ul><ul><li>Ensures that attackers do not gain control over applications </li></ul></ul>
  9. 9. Security requirements of SOA: Non-functional <ul><li>Interoperability </li></ul><ul><ul><li>Security solutions must not break compatibility of services </li></ul></ul><ul><li>Manageability </li></ul><ul><ul><li>Refers to the ease with which a security a security solution can be managed </li></ul></ul><ul><li>Ease of development </li></ul><ul><ul><li>Complexity reduces adoption of any security solution </li></ul></ul>
  10. 10. Message level security Trust models depicting the point-to-point and end-to-end configurations [4]
  11. 11. Message level security: WS-Security <ul><li>An OASIS standard which allows message-level security to be implemented with SOAP </li></ul><ul><li>Specifications include; </li></ul><ul><ul><li>How to attach signature and encryption headers to SOAP messages? </li></ul></ul><ul><ul><li>How to attach security tokens such as X.509 certificates and Kerberos tickets to messages? </li></ul></ul>
  12. 12. Message level security: WS-Security Security token service model [4]
  13. 13. Security as a service Security implemented as an infrastructure service, for e.g. offered by the ESB
  14. 14. Security as a service: SAML <ul><li>Security Assertion Markup Language (SAML) </li></ul><ul><ul><li>Framework for exchange of security related information between trusting parties </li></ul></ul><ul><ul><li>Key standard for federated identity systems </li></ul></ul><ul><ul><li>Cross domain Single-Sign On (SSO) </li></ul></ul><ul><li>Three components of the SAML specification are; </li></ul><ul><ul><li>Assertions (authentication, attribute and authorization) </li></ul></ul><ul><ul><li>Protocol </li></ul></ul><ul><ul><li>Binding </li></ul></ul><ul><li>Assertions are exchanged among sites and services using the protocol and binding </li></ul>
  15. 15. Security as a service: SAML SAML Implementation
  16. 16. Security as a service: AON <ul><li>Application-oriented networking (AON) involves network devices designed to aid computer-to-computer application integration </li></ul><ul><li>Salient features of AON include; </li></ul><ul><ul><li>Enhances XML processing capabilities </li></ul></ul><ul><ul><li>Provides secure and fast movement of XML and non-XML messages </li></ul></ul><ul><ul><li>Provides consistent policy enforcement for security, transaction routing, etc. </li></ul></ul><ul><ul><li>Fosters XML-based technologies and SOA </li></ul></ul>
  17. 17. Policy driven security <ul><li>Security policy decisions separate security logic from business logic </li></ul><ul><li>Easier to ensure consistency of security enforcement across multiple applications </li></ul><ul><li>Challenges to be addressed; </li></ul><ul><ul><li>Ease of development and administration </li></ul></ul><ul><ul><li>Consistency of security checks </li></ul></ul><ul><ul><li>Interoperability of security solutions </li></ul></ul>
  18. 18. Policy driven security: Declarative programming <ul><li>Used as a mechanism to separate a concern from the rest of the solution </li></ul><ul><li>Different degrees to which declarative security can be employed; </li></ul><ul><ul><li>Internal use within an enterprise to ensure consistency </li></ul></ul><ul><ul><li>Use at design time to ensure interoperability </li></ul></ul><ul><ul><li>Use at runtime to ensure interoperability </li></ul></ul><ul><li>Machine-readable expression of what is required in a message exchange from a WS-Standards perspective </li></ul><ul><li>WS-Policy is an emerging standard that makes this approach possible </li></ul>
  19. 19. Policy driven security: WS-Policy <ul><li>WS-Policy framework specifies; </li></ul><ul><ul><li>Syntax for writing policies </li></ul></ul><ul><ul><li>Algorithm for comparing policies </li></ul></ul>Policy-based approach to ensuring interoperability between two parties in a web service message exchange <ul><li>Sign the body of the request </li></ul><ul><li>Encrypt the body of the request </li></ul><ul><li>Encrypt the signature of the body </li></ul><ul><li>Include a timestamp as the last entry in WS-Security header </li></ul>
  20. 20. Policy driven security: WS-Policy Query via WS-MetadataExchange or look up policies attached to WSDL/UDDI entities as described in WS-PolicyAttachment.
  21. 21. Unified Web services security Enterprise Application Security Integration (EASI) solution Firewalls and access control Internal security Policies, procedures and tools in place <ul><li>Enterprise security architectures must support end-to-end security across many application components </li></ul>
  22. 22. SOA Security Model Holistic security model with a breakdown of security services
  23. 23. SOA Security Model <ul><li>Authorization services </li></ul><ul><ul><li>Controls access to services based on a set of policies </li></ul></ul><ul><li>Authentication services </li></ul><ul><ul><li>Security token service that can help issue and validate authentication credentials </li></ul></ul><ul><li>Identity services </li></ul><ul><ul><li>Managing, sharing, federating and accessing of identity information from a variety of authoritative identity sources </li></ul></ul>
  24. 24. SOA Security Model <ul><li>Confidentiality services </li></ul><ul><ul><li>Provide the capabilities to protect sensitive information from disclosure and to detect unauthorized modification of data </li></ul></ul><ul><li>Audit services </li></ul><ul><ul><li>Provides mechanisms to submit, store and report on audit data submitted as system events </li></ul></ul>
  25. 25. Case-study at Agresso - Background <ul><li>Agresso Integration Hub is a middleware, deployed as a SOA infrastructure </li></ul><ul><li>Provides fundamental functions for services exposure and adaptable business process </li></ul><ul><li>Provides a wide set of capabilities to manage and integrate services and events across applications </li></ul>
  26. 26. Case-study at Agresso – Integration workflow
  27. 27. Case-study at Agresso - Solution <ul><li>Identity Management (IdM) system which can access identity information from different authorized sources </li></ul><ul><li>Confidentiality of the messages can be protected by making use of WS-Security </li></ul><ul><li>ESB has to be implemented as a policy-enforcement point </li></ul><ul><li>Web-services can advertize their local policies and specify their policy requirements by making use of WS-Policy </li></ul><ul><li>SOA governance module can be used to deploy auditing services which store the logs of all XML traffic </li></ul>
  28. 28. Conclusion <ul><li>Context of security changes with respect to SOA </li></ul><ul><li>Security approaches to SOA include; </li></ul><ul><ul><li>Message level security </li></ul></ul><ul><ul><li>Security as a service </li></ul></ul><ul><ul><li>Policy driven security </li></ul></ul><ul><li>Security approaches can be unified into a single framework e.g. EASI model </li></ul><ul><li>SOA security model provides a holistic approach to secure the environment </li></ul><ul><li>Case study to evaluate the security model and solve security vulnerabilities of Agresso Integration Hub </li></ul>
  29. 29.
  30. 30. References <ul><li>How to Identify, Specify and Realize Services for your SOA (Part I), by Ali Arsanjani IBM, 2005 </li></ul><ul><li>An integrated model for SOA Governance by Kingkarn Kanchanavipu, August 2008. </li></ul><ul><li>SOA Security by Ramarao Kanneganti and Prasad Chodavarapu, 2008 Manning Publication Co. </li></ul><ul><li>Security in a Web Services World: A Proposed Architecture and Roadmap, A joint security whitepaper from IBM Corporation and Microsoft Corporation, April 2002, Version 1.0 </li></ul><ul><li>How SAML works? A newsletter by Preston Gralla, April 2002. </li></ul><ul><li>The Network's New Role by Taf Anthias and Krishna Sankar, ACM Queue vol. 4, no. 4 - May 2006 </li></ul><ul><li>Does Application-Oriented Networking Impact SOA and Web Services? by Bijoy Majumdar, Vikas Kumar and Vivek Raut, Dec 2005 </li></ul><ul><li>Understanding Web Services Policy, by Asir S Vedamuthu and Daniel Roth, Microsoft Corporation, July 2006 </li></ul><ul><li>Mastering Web Services Security by Bret Hartman, Donald J. Flinn, Konstantin Beznosov, and Shirley Kawamoto, 2003 Wiley Publishing Inc. </li></ul><ul><li>Enterprise Application Security Integration for Application Servers and Portals, by Randy Heffner, June 2001. </li></ul><ul><li>Agresso Integration Hub Roadmap, Agresso Whitepaper (Draft) </li></ul><ul><li>Service-oriented agility: Methods for successful Service-Oriented Architecture, by Pal Krogdahl, Gottrried Luef and Christoph Steindl, July 2005 </li></ul><ul><li>MSDN .NET Framework Developer Centre - What's New in Web Services Enhancements (WSE) 3.0. </li></ul><ul><li>SOA in Practice – The Art of Distributed System Design by Nicolai M. Josuttis, August 2007 </li></ul><ul><li>Broker Architecture for Web-services – Tech Republic Whitepaper, May 2002. </li></ul><ul><li>SAML Service - Sun ONE Identity Server Customization and API Guide, section 8.1. </li></ul>