<?xml version="1.0" encoding="UTF-8"?>
<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/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>insanesecurity &#187; ASP</title>
	<atom:link href="http://insanesecurity.info/blog/tag/asp/feed" rel="self" type="application/rss+xml" />
	<link>http://insanesecurity.info/blog</link>
	<description>security through a distorted eye</description>
	<lastBuildDate>Thu, 25 Feb 2010 22:31:12 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>OWASP Code Review Guide</title>
		<link>http://insanesecurity.info/blog/owasp-code-review-guide</link>
		<comments>http://insanesecurity.info/blog/owasp-code-review-guide#comments</comments>
		<pubDate>Wed, 24 Jun 2009 16:25:00 +0000</pubDate>
		<dc:creator>dblackshell</dc:creator>
				<category><![CDATA[Books]]></category>
		<category><![CDATA[ASP]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Javascript]]></category>
		<category><![CDATA[PHP]]></category>

		<guid isPermaLink="false">http://insanesecurity.info/blog/?p=50</guid>
		<description><![CDATA[Code review is probably the single-most effective technique for identifying security flaws. When used together with automated tools and manual penetration testing, code review can significantly increase the cost effectiveness of an application security verification effort. (Introduction) The first section (Methodology) walks you through the: introduction to code review, preparation for code review, security code [...]]]></description>
			<content:encoded><![CDATA[<p>Code review is probably the single-most effective technique for identifying security flaws. When used together with automated tools and manual penetration testing, code review can significantly increase the cost effectiveness of an application security verification effort. (<a href="http://www.owasp.org/index.php/Code_Review_Introduction" target="_blank">Introduction</a>)<br />
<span id="more-50"></span><br />
<img src="http://insanesecurity.info/wp-content/uploads//owasp-code-review-guide.jpg" style="float:right;margin: 0 0 0 4px" width="200" />The first section (Methodology) walks you through the: introduction to code review, preparation for code review, security code review in software development life cycle (waterfall and agile), security code review coverage, application threat modeling and code review metrics. From this first section I&#8217;ve found very interesting the &#8220;application threat modeling&#8221; page, because I never did know how to classify (evaluate) the risk of a vulnerability and it really made me understand a lot about it.</p>
<p>The next section of the guide is about crawling code, what to look for in JAVA/ASP/JavaSript.</p>
<p>I&#8217;ll skip the rest (I&#8217;ll let you discover it) and only mention the &#8220;example by technical control&#8221;, section which I would recommend to any web developer (regardless of language) because It points out every aspect for the following technical controls: authentication, authorization, session management, input/data validation, error handling, secure deployment, cryptographic controls.</p>
<p>That being said, you can read the guide on-line at <a href="http://www.owasp.org/index.php/OWASP_Code_Review_Guide_Table_of_Contents" target="_blank">owasp.org</a>, or download the pdf version from <a href="http://www.lulu.com/content/5678680" target="_blank">lulu.com</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://insanesecurity.info/blog/owasp-code-review-guide/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
