AND-302-No Interop No Security How to Build Interoperable Web Service Security.pdfVIP

下载本文档

24
0
约1.7万字
约 41页
2017-04-06 发布于江苏
举报
版权申诉

AND-302-No Interop No Security How to Build Interoperable Web Service Security.pdf

1、原创力文档（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。。
2、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
4、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
5、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
6、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
7、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

AND-302-No Interop No Security How to Build Interoperable Web Service Security

No Interop, No Security: How to Build Interoperable W b S ie erv ce Security Pyounguk Cho Oracle 04/23/09 | Session ID:AND-302 Session Classification: Intermediate Agenda Web Service Under Attack Web Service Security As Defense Measures W b S i I t bilit S ite erv ce n eropera y vs. ecur y Building Interoperable Secure Web Services 2 Web Service U dn er Attack Web Service : What is it? ? Evolution of previous distributed programming frameworks – Process Centric – Platform agnostic ? Web Service core – XML : Highly structured universal message exchange format – WSDL : Describes service interfaces – SOAP :XML-based Transport layer independent protocol for b iwe serv ce messages – UDDI : Naming service for web services ? “WS-etc” : other high-level services found in middleware systems are still evolving – WS-Policy – WS-SX/TX/RX – WS-Eventing Where is Web Service today? ? Adoption E b d d t d h t it i– very o y un ers an s w a s – Ubiquitously adopted and deployed – Popular for connecting platforms and applications – Starting to go beyond basics ? What are the pain points? – Security(interoperability-induced pain) – Performance – Complexity (interoperability-induced pain) Web Service Components Points to d i tiUDDI WSDL escr p on Registry Describes Service Finds Service Points to service Web Service (JEE SOA Web Service SOAP , , PL/SQL, .NET,C/C++, Legacy …) Client (JEE,SOA,.NET, PL/SQL …) Invokes with XML Messages Attack Against Web Service ? Why bother to attack web services? – Business data : Potentially more rewarding to attackers – Numerous targets due to high adoption ? Integration(intranet) ? B2Bi(public) ? Web 2.0(AJAX endpoints) – Bypassing front-end tiers ? What makes web services vulnerable? – Open architecture ? Protocol ? Service contract/blueprint – Human readable messages – Tools ? Client generation ? Message monitoring ? Automated fuzzing Attack Vectors ? Traditional threat model – Unauthorized service invocation Mal