Download presentation
Presentation is loading. Please wait.
Published byKevin Fields Modified over 8 years ago
1
Dr. Rebhi S. Baraka rbaraka@iugaza.edu Advanced Topics in Information Technology (SICT 4310) Department of Computer Science Faculty of Information Technology The Islamic University of Gaza
2
The coupling of Web services has an inherent security risk such as: ◦ Allowing interception of data that flows between services, to provide information about servers, usernames, passwords, or personal, financial, medical or other sensitive information ◦ Allowing alteration of data that flows between services, to return incorrect results or redirect the flow to other services. ◦ Simply shutting down the service itself, so that other dependent services can no longer function, disrupting multiple users from multiple access points.
3
At a minimum, there are at least seven different types of security measures that may need to be enforced at each individual application Web- services: ◦ Stringent service provider/service requester authentication between the application and each Web service it invokes ◦ Access control, possibly at both ends, to determine the functions that may be requested—per invocation, based on the authentication instance ◦ Digital signatures to ensure the validity of contents ◦ Nonrepudiation to preclude either side from disowning a transaction once it has been executed
4
◦ XML application firewall, such as IBM’s Web Services Gateway, to decouple the end-to-end communications connection at the enterprise network boundary ◦ Proven data encryption end to end—most likely with the industry standard SSL or its successor TLS ◦ Denial-of-service/replay attack detection and diversion mechanisms—which typically come with powerful traffic pattern sampling, analyzing, profiling, and reporting tools that will continually monitor the network interface to spot any unusual trends.
5
Some of the XML specifications ◦ encryption, ◦ digital signatures, and ◦ key management services. Other standards-based organizations, such as OASIS and WS-I, are working on additional specifications related to SOAP security, including ◦ Extensible Access Control Markup Language (XACML) and ◦ Security Assertion Markup Language (SAML). These standards provide the security foundation for SOAP and other XML-based messaging paradigms.
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.