<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Mastering PCI Section 6.6 &#8211; OWASP AppSec NYC 2008</title>
	<atom:link href="http://www.webadminblog.com/index.php/2008/09/24/mastering-pci-section-66-owasp-appsec-nyc-2008/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webadminblog.com/index.php/2008/09/24/mastering-pci-section-66-owasp-appsec-nyc-2008/</link>
	<description>Real Web Admins.  Real World Experience.</description>
	<lastBuildDate>Mon, 23 Aug 2010 03:12:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Josh</title>
		<link>http://www.webadminblog.com/index.php/2008/09/24/mastering-pci-section-66-owasp-appsec-nyc-2008/comment-page-1/#comment-182</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Thu, 25 Sep 2008 12:24:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.webadminblog.com/?p=100#comment-182</guid>
		<description>The method laid out by Jacob and Taylor in this presentation for comparing source code analysis to penetration testing to application firewalls is a pretty good way to compare different things in an organized and even manner.  NI actually does something fairly similar when comparing different vendors with similar tools and we call it a &quot;Supplier Selection Matrix (SSM)&quot; or a &quot;Vendor Report Card&quot;.  This is just an Excel spreadsheet with the rows being your evaluation criteria and columns being the vendors you want to compare.  We break the evaluation criteria into administration, management, market position, usability, architecture, extensability categories and will add additional categories for additional functionality that we want to evaluate based on the specific type of vendor we are evaluating.  For example, if we are evaluating a vulnerability detection tool, we probably want an additional category for &quot;vulnerability detection&quot; features that accounts for the number of vulnerabilities detected, quality of vulnerabilities detected, and accuracy of vulnerabilities detected.  The last step is to provide a 1-10 weight for each evaluation criteria category for how important it is to you.  Then, give each tool a 1-5 rating in each category and calculate the weighted average (cat1 rating x weight1 + cat2 rating + weight2 + ...)/(weight1 + weight2 + ...) for each tool.  The number that you come out with is the grade for that tool.  0-0.999=F, 1-1.999=D, 2-2.999=C, 3-3.999=B, 4-5=A.</description>
		<content:encoded><![CDATA[<p>The method laid out by Jacob and Taylor in this presentation for comparing source code analysis to penetration testing to application firewalls is a pretty good way to compare different things in an organized and even manner.  NI actually does something fairly similar when comparing different vendors with similar tools and we call it a &#8220;Supplier Selection Matrix (SSM)&#8221; or a &#8220;Vendor Report Card&#8221;.  This is just an Excel spreadsheet with the rows being your evaluation criteria and columns being the vendors you want to compare.  We break the evaluation criteria into administration, management, market position, usability, architecture, extensability categories and will add additional categories for additional functionality that we want to evaluate based on the specific type of vendor we are evaluating.  For example, if we are evaluating a vulnerability detection tool, we probably want an additional category for &#8220;vulnerability detection&#8221; features that accounts for the number of vulnerabilities detected, quality of vulnerabilities detected, and accuracy of vulnerabilities detected.  The last step is to provide a 1-10 weight for each evaluation criteria category for how important it is to you.  Then, give each tool a 1-5 rating in each category and calculate the weighted average (cat1 rating x weight1 + cat2 rating + weight2 + &#8230;)/(weight1 + weight2 + &#8230;) for each tool.  The number that you come out with is the grade for that tool.  0-0.999=F, 1-1.999=D, 2-2.999=C, 3-3.999=B, 4-5=A.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
