<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://dotnet.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Articles by Robert Hurlbut</title>
 <link>http://dotnet.sys-con.com/</link>
 <description>Latest articles from Robert Hurlbut</description>
 <language>en</language>
 <copyright>Copyright 2008 SYS-CON Media</copyright>
 <generator>SYS-CON Media</generator>
 <lastBuildDate>Wed, 08 Oct 2008 04:18:55 EDT</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>SQL Injection</title>
 <link>http://dotnet.sys-con.com/node/86223</link>
 <description>Many applications (Web-based applications and forms-based [&#039;smart client&#039;] applications) typically use data stored in a database. While you may have firewalls and other protections established when running your application, your application can still be open to an attacker gaining direct (or indirect) access to information in your database. The most common and dangerous attack technique is to use SQL injection.&lt;p&gt;&lt;a href=&quot;http://dotnet.sys-con.com/node/86223&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 20 May 2005 11:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://dotnet.sys-con.com/node/86223</guid>
</item>
</channel>
</rss>
