<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/">
	<channel>
		<title>DevTools</title>
		<link>http://bluekatana.bigforumpro.com/feed/?</link>
		<description>Latest topics</description>
		<lastBuildDate>Sun, 10 Feb 2008 06:19:58 GMT</lastBuildDate>
		<ttl>10</ttl>
		<image>
			<title>DevTools</title>
			<url>http://www.bluekatana.com/images/BKForumLogo-Small.gif</url>
			<link>http://bluekatana.bigforumpro.com/feed/?</link>
		</image>
		<item>
			<title>Preventing SQL Server Injection</title>
			<link>http://bluekatana.bigforumpro.com/sql-server-service-f6/preventing-sql-server-injection-t14.htm</link>
			<dc:creator>dsamuilov</dc:creator>
			<description>I was asked in my blog (bluekatana.com/diego) how SQL injection can be prevented. Here's my take on this issue:



SQL injection is an attack to a website in which malicious code is inserted into fields that are later passed to an instance of SQL Server for execution. Any webpage that takes such SQL statements should be reviewed for injection vulnerabilities because SQL Server can execute all the queries that it receives. Some recommend that parametrized queries be used, but they can also be  ...</description>
			<category>SQL Server (service)</category>
			<pubDate>Sun, 10 Feb 2008 06:19:58 GMT</pubDate>
			<comments>http://bluekatana.bigforumpro.com/sql-server-service-f6/preventing-sql-server-injection-t14.htm#14</comments>
			<guid>http://bluekatana.bigforumpro.com/sql-server-service-f6/preventing-sql-server-injection-t14.htm</guid>
		</item>
	</channel>
</rss>