<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://marcchanliau.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Marc Chanliau</title>
 <link>http://marcchanliau.sys-con.com/</link>
 <description>Latest News from Marc Chanliau</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Wed, 09 Dec 2009 00:39:42 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Identity Propagation in a SOA</title>
 <link>http://marcchanliau.sys-con.com/node/218996</link>
 <description>One of the challenges IT organizations face is how to propagate identities in complex business processes that are commonly found in Service Oriented Architectures (SOAs). Identities, which are passed from one service invocation to the next in a business process, give the process a user context. Identities can be used to determine access rights to SOA services and for audit and compliance purposes.&lt;p&gt;&lt;a href=&quot;http://marcchanliau.sys-con.com/node/218996&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 11 May 2006 10:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://marcchanliau.sys-con.com/node/218996</guid>
 <comments>http://marcchanliau.sys-con.com/node/218996#feedback</comments>
</item>
<item>
 <title>Enterprise Web Services Security: A Reference Architecture, part II</title>
 <link>http://marcchanliau.sys-con.com/node/43970</link>
 <description>Last month (WSJ, Vol. 4, issue 2), we looked at how Web services should not depend on specific security environments and rules but should be managed as part of all of an enterprise&#039;s corporate data assets such as Web applications, ERP systems, and in-house applications.&lt;p&gt;&lt;a href=&quot;http://marcchanliau.sys-con.com/node/43970&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 08 Mar 2004 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://marcchanliau.sys-con.com/node/43970</guid>
 <comments>http://marcchanliau.sys-con.com/node/43970#feedback</comments>
</item>
<item>
 <title>Enterprise Web Services Security: A Reference Architecture</title>
 <link>http://marcchanliau.sys-con.com/node/43569</link>
 <description>Web services are past the initial marketing hype. Early Web services were part of experimental one-off projects within a single enterprise department. Now, larger Web services deployments are moving outside of the enterprise firewall to better leverage existing business partnerships and value chains.&lt;p&gt;&lt;a href=&quot;http://marcchanliau.sys-con.com/node/43569&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 05 Feb 2004 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://marcchanliau.sys-con.com/node/43569</guid>
 <comments>http://marcchanliau.sys-con.com/node/43569#feedback</comments>
</item>
<item>
 <title>The Security Challenge</title>
 <link>http://marcchanliau.sys-con.com/node/39702</link>
 <description>This article focuses on the value of Web services security. It is important to understand what Web services are and their challenges, particularly related to security. Traditionally, companies have relied on conventional, transport-level security but this approach has its limitations. The market now offers complementary XML-based solutions designed to secure documents used in Web services requests and responses. We will explore these solutions and outline &#039;typical case scenarios&#039; to provide a comprehensive landscape on the current offering of Web services security solutions.&lt;p&gt;&lt;a href=&quot;http://marcchanliau.sys-con.com/node/39702&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 24 Feb 2003 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://marcchanliau.sys-con.com/node/39702</guid>
 <comments>http://marcchanliau.sys-con.com/node/39702#feedback</comments>
</item>
</channel>
</rss>
