<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://java.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Articles by Frank Nimphius</title>
 <link>http://java.sys-con.com/</link>
 <description>Latest articles from Frank Nimphius</description>
 <language>en</language>
 <copyright>Copyright 2008 SYS-CON Media</copyright>
 <generator>SYS-CON Media</generator>
 <lastBuildDate>Thu, 28 Aug 2008 20:16:26 EDT</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>Application Security in AJAX</title>
 <link>http://java.sys-con.com/node/436281</link>
 <description>If you have evaluated AJAX (Asynchronous JavaScript and XML) for your next Web application development project, then you probably have read or heard a great deal about AJAX security concerns and the claim that AJAX increases the attack surface for hackers. If you are a skilled security developer, you might wonder whether the AJAX security problem originates in the technologies involved or whether lack of security in AJAX is a misconception. Security threats like SQL injection, cross-site scripting (XSS), message spoofing, and failed input validation existed before in Web applications and have been solved many times since then.&lt;p&gt;&lt;a href=&quot;http://java.sys-con.com/node/436281&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sun, 07 Oct 2007 09:30:00 EDT</pubDate>
 <guid isPermaLink="true">http://java.sys-con.com/node/436281</guid>
</item>
<item>
 <title>Application Security in AJAX</title>
 <link>http://java.sys-con.com/node/430930</link>
 <description>If you have evaluated AJAX for your next Web application development project, then you probably have read or heard a great deal about AJAX security concerns and the claim that AJAX increases the attack surface for hackers. If you are a skilled security developer, you might wonder whether the AJAX security problem originates in the technologies involved or whether lack of security in AJAX is a misconception.&lt;p&gt;&lt;a href=&quot;http://java.sys-con.com/node/430930&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 21 Sep 2007 18:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://java.sys-con.com/node/430930</guid>
</item>
<item>
 <title>Effective Page Authorization In JavaServer Faces</title>
 <link>http://java.sys-con.com/node/250254</link>
 <description>Application security - the art of applications defending themselves - represents an important line of defence in an overall in-depth security strategy. Web applications that follow the Model-View-Controller (MVC) architecture can, and should, have security implemented on all three layers. Normally it&#039;s the controller component that handles page authorization in MVC, the view layer that hides controls and information based on user authorization, and the model that enforces the business rules and input validation. However, it&#039;s up to the developer, based on an individual security policy and the programming technology used, to decide where to put security. Using pluggable validator components in JavaServer Faces (JSF), for example, developers may decide to verify user input on the view layer as well as on the model layer.&lt;p&gt;&lt;a href=&quot;http://java.sys-con.com/node/250254&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 10 Aug 2006 17:15:00 EDT</pubDate>
 <guid isPermaLink="true">http://java.sys-con.com/node/250254</guid>
</item>
</channel>
</rss>
