<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://rogergoudarzi.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Roger Goudarzi</title>
 <link>http://rogergoudarzi.sys-con.com/</link>
 <description>Latest News from Roger Goudarzi</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Fri, 11 Dec 2009 01:57:51 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Best Practices for Securing Your SOA: A Holistic Approach</title>
 <link>http://rogergoudarzi.sys-con.com/node/232071</link>
 <description>Service-Oriented Architectures offer a number of potential benefits: They can provide new opportunities to connect enterprises with customers, partners, and suppliers; improve efficiency through greater reuse of services across the enterprise; and offer greater flexibility by breaking down IT silos. But these benefits make security more critical than ever. Why? Services are highly distributed, multi-owner, deployed to heterogeneous platforms, and often accessible across departments and enterprises - and this creates major security issues for developers, architects, and security and operations professionals. Fortunately, there are ways to make your SOA more secure. If you&#039;re building applications to SOA using J2EE, BPEL, or XML, you can build security into an SOA by addressing security throughout the entire application lifecycle - not just at deployment time.&lt;p&gt;&lt;a href=&quot;http://rogergoudarzi.sys-con.com/node/232071&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 20 Jun 2006 08:30:00 EDT</pubDate>
 <guid isPermaLink="true">http://rogergoudarzi.sys-con.com/node/232071</guid>
 <comments>http://rogergoudarzi.sys-con.com/node/232071#feedback</comments>
</item>
</channel>
</rss>
