<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss 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/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>VendorRisk Blog</title>
	
	<link>http://blog.vendorrisk.com</link>
	<description>Vendor Management Software</description>
	<lastBuildDate>Tue, 06 Jul 2010 18:59:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/VendorriskBlog" /><feedburner:info uri="vendorriskblog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>Trust Guard, Apache &amp; Rails</title>
		<link>http://feedproxy.google.com/~r/VendorriskBlog/~3/zrghdFVVSQk/</link>
		<comments>http://blog.vendorrisk.com/2010/07/trust-guard-apache-rails/#comments</comments>
		<pubDate>Tue, 06 Jul 2010 18:59:34 +0000</pubDate>
		<dc:creator>vr_admin</dc:creator>
				<category><![CDATA[Behind the Scenes]]></category>

		<guid isPermaLink="false">http://blog.vendorrisk.com/?p=60</guid>
		<description>We recently added the Trust Guard service to VendorRisk.com.  As part of the package we purchased, Trust Guard scans our server each day looking for vulnerabilities.  On the first scan, it found 4 &amp;#8220;medium risk&amp;#8221; issues that had to be resolved in order to pass PCI compliance.  Here are the issues and what we did ...&lt;img src="http://feeds.feedburner.com/~r/VendorriskBlog/~4/zrghdFVVSQk" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blog.vendorrisk.com/2010/07/trust-guard-apache-rails/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.vendorrisk.com/2010/07/trust-guard-apache-rails/</feedburner:origLink></item>
		<item>
		<title>New pricing plans</title>
		<link>http://feedproxy.google.com/~r/VendorriskBlog/~3/yYDCQmoX58g/</link>
		<comments>http://blog.vendorrisk.com/2010/05/new-pricing-plans/#comments</comments>
		<pubDate>Mon, 03 May 2010 14:18:46 +0000</pubDate>
		<dc:creator>vr_admin</dc:creator>
				<category><![CDATA[In the News]]></category>

		<guid isPermaLink="false">http://blog.vendorrisk.com/?p=55</guid>
		<description>Over the weekend we released a new version of vendorrisk.com, our vendor management software.  Along with a new look-and-feel to the brochure site, we also revised the pricing plans.  Originally we had three monthly plans &amp;#8212; Bronze, Silver and Gold &amp;#8212; that differed by the number of vendors and the disk space allocated to file ...&lt;img src="http://feeds.feedburner.com/~r/VendorriskBlog/~4/yYDCQmoX58g" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blog.vendorrisk.com/2010/05/new-pricing-plans/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.vendorrisk.com/2010/05/new-pricing-plans/</feedburner:origLink></item>
		<item>
		<title>Round-up of new features</title>
		<link>http://feedproxy.google.com/~r/VendorriskBlog/~3/B0I1WcRpva8/</link>
		<comments>http://blog.vendorrisk.com/2010/02/round-up-of-new-features/#comments</comments>
		<pubDate>Wed, 24 Feb 2010 20:56:19 +0000</pubDate>
		<dc:creator>vr_admin</dc:creator>
				<category><![CDATA[New Features]]></category>

		<guid isPermaLink="false">http://blog.vendorrisk.com/?p=49</guid>
		<description>We&amp;#8217;ve been pushing out new versions of vendorrisk.com several times a week since we launched in early December.  The following are some of the highlights:

Charts tab &amp;#8212; over 30 charts have been added.  Each chart is available in both pie and column formats and generated in real-time.
Import contacts from Outlook &amp;#8211; to expedite data input, ...&lt;img src="http://feeds.feedburner.com/~r/VendorriskBlog/~4/B0I1WcRpva8" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blog.vendorrisk.com/2010/02/round-up-of-new-features/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.vendorrisk.com/2010/02/round-up-of-new-features/</feedburner:origLink></item>
		<item>
		<title>Highrise integration added</title>
		<link>http://feedproxy.google.com/~r/VendorriskBlog/~3/tfR52xBSZO8/</link>
		<comments>http://blog.vendorrisk.com/2010/02/highrise-integration-added/#comments</comments>
		<pubDate>Tue, 02 Feb 2010 19:32:09 +0000</pubDate>
		<dc:creator>vr_admin</dc:creator>
				<category><![CDATA[New Features]]></category>

		<guid isPermaLink="false">http://blog.vendorrisk.com/?p=47</guid>
		<description>We pushed a new version of VendorRisk.com live today that includes integration with Highrise, the popular CRM app from 37signals.
If you have an account on Highrise, you can go to the &amp;#8220;Highrise integration&amp;#8221; link in your VendorRisk admin section and enter your Highrise domain and API key.  Once saved, you can use the subsequent link ...&lt;img src="http://feeds.feedburner.com/~r/VendorriskBlog/~4/tfR52xBSZO8" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blog.vendorrisk.com/2010/02/highrise-integration-added/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.vendorrisk.com/2010/02/highrise-integration-added/</feedburner:origLink></item>
		<item>
		<title>Vendor Management Interview with IT Director of a Bank</title>
		<link>http://feedproxy.google.com/~r/VendorriskBlog/~3/NB-UFap5i08/</link>
		<comments>http://blog.vendorrisk.com/2010/01/vendor-management-interview-director/#comments</comments>
		<pubDate>Tue, 26 Jan 2010 22:19:58 +0000</pubDate>
		<dc:creator>vr_admin</dc:creator>
				<category><![CDATA[Vendor Management]]></category>

		<guid isPermaLink="false">http://blog.vendorrisk.com/?p=44</guid>
		<description>Bill Kane is the Director of IT at Boston Private Bank &amp;#38; Trust Company.  A few years ago, we developed a vendor management application for the bank&amp;#8217;s use, which later became the basis for VendorRisk.  We asked him a few questions about their rationale for establishing a vendor management strategy and how the application has ...&lt;img src="http://feeds.feedburner.com/~r/VendorriskBlog/~4/NB-UFap5i08" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blog.vendorrisk.com/2010/01/vendor-management-interview-director/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.vendorrisk.com/2010/01/vendor-management-interview-director/</feedburner:origLink></item>
		<item>
		<title>Rails, authlogic and password history</title>
		<link>http://feedproxy.google.com/~r/VendorriskBlog/~3/oru_DOfEQt4/</link>
		<comments>http://blog.vendorrisk.com/2009/12/rails-authlogic-password-history/#comments</comments>
		<pubDate>Mon, 28 Dec 2009 21:25:07 +0000</pubDate>
		<dc:creator>vr_admin</dc:creator>
				<category><![CDATA[Behind the Scenes]]></category>

		<guid isPermaLink="false">http://blog.vendorrisk.com/?p=35</guid>
		<description>vendorrisk.com client sites use the excellent Authlogic gem to handle user sessions. As we mentioned in the previous blog article, we recently added the ability for site admins to declare that users cannot use a password they've used in the past.

After a bit of Googling, I didn't see any solutions out there for dealing with this issue, so we rolled our own.  Here's how we went about it...&lt;img src="http://feeds.feedburner.com/~r/VendorriskBlog/~4/oru_DOfEQt4" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blog.vendorrisk.com/2009/12/rails-authlogic-password-history/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://blog.vendorrisk.com/2009/12/rails-authlogic-password-history/</feedburner:origLink></item>
		<item>
		<title>New password enhancements</title>
		<link>http://feedproxy.google.com/~r/VendorriskBlog/~3/rhmR7ujPDqI/</link>
		<comments>http://blog.vendorrisk.com/2009/12/new-password-enhancements/#comments</comments>
		<pubDate>Sat, 26 Dec 2009 18:52:31 +0000</pubDate>
		<dc:creator>vr_admin</dc:creator>
				<category><![CDATA[New Features]]></category>

		<guid isPermaLink="false">http://blog.vendorrisk.com/?p=32</guid>
		<description>In his article entitled "How to use Software as a Service securely", author Phil Cox describes how SaaS providers need to better enforce password restrictions to aid in preventing unauthorized access to the application.

When we first launched VendorRisk.com, we had the following criteria in place...&lt;img src="http://feeds.feedburner.com/~r/VendorriskBlog/~4/rhmR7ujPDqI" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blog.vendorrisk.com/2009/12/new-password-enhancements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.vendorrisk.com/2009/12/new-password-enhancements/</feedburner:origLink></item>
		<item>
		<title>Mobile version now available</title>
		<link>http://feedproxy.google.com/~r/VendorriskBlog/~3/nXZpLBw8VUM/</link>
		<comments>http://blog.vendorrisk.com/2009/12/mobile-version-now-available/#comments</comments>
		<pubDate>Mon, 21 Dec 2009 21:37:21 +0000</pubDate>
		<dc:creator>vr_admin</dc:creator>
				<category><![CDATA[New Features]]></category>

		<guid isPermaLink="false">http://blog.vendorrisk.com/?p=30</guid>
		<description>Over the weekend (blizzard = productivity), we pushed the first iteration of a mobile version of the VendorRisk application.  If you access your site from a mobile device, you&amp;#8217;ll be given a very low-bandwidth version (no JavaScript, no images, little CSS, no color scheme) of your site.  Once you login, you have access to your ...&lt;img src="http://feeds.feedburner.com/~r/VendorriskBlog/~4/nXZpLBw8VUM" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blog.vendorrisk.com/2009/12/mobile-version-now-available/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.vendorrisk.com/2009/12/mobile-version-now-available/</feedburner:origLink></item>
		<item>
		<title>New module: Hardware</title>
		<link>http://feedproxy.google.com/~r/VendorriskBlog/~3/p2m5-omMi1k/</link>
		<comments>http://blog.vendorrisk.com/2009/12/new-hardware-module/#comments</comments>
		<pubDate>Mon, 21 Dec 2009 21:11:40 +0000</pubDate>
		<dc:creator>vr_admin</dc:creator>
				<category><![CDATA[New Features]]></category>

		<guid isPermaLink="false">http://blog.vendorrisk.com/?p=28</guid>
		<description>When we first developed VendorRisk.com, we had modules for Services and Software, as that&amp;#8217;s what the original client required.  When we showed it to several other people, their reaction was &amp;#8220;That&amp;#8217;s great, but where&amp;#8217;s Hardware?&amp;#8221;
Touche.  Over the weekend we added it to the site.  There is now a tab up top for Hardware, which has ...&lt;img src="http://feeds.feedburner.com/~r/VendorriskBlog/~4/p2m5-omMi1k" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blog.vendorrisk.com/2009/12/new-hardware-module/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.vendorrisk.com/2009/12/new-hardware-module/</feedburner:origLink></item>
		<item>
		<title>Fun with Rails A/B testing</title>
		<link>http://feedproxy.google.com/~r/VendorriskBlog/~3/ZlgDVVB9Aeo/</link>
		<comments>http://blog.vendorrisk.com/2009/12/fun-with-rails-ab-testing/#comments</comments>
		<pubDate>Sun, 20 Dec 2009 18:25:29 +0000</pubDate>
		<dc:creator>vr_admin</dc:creator>
				<category><![CDATA[Behind the Scenes]]></category>

		<guid isPermaLink="false">http://blog.vendorrisk.com/?p=22</guid>
		<description>When we launched VendorRisk.com a few weeks back, we added a very simple A/B experiment to test which sign up call to action worked better.  The first two options we chose were &amp;#8220;View plans and pricing&amp;#8221; and &amp;#8220;Try free for 30 days!&amp;#8221;.  We assumed that the latter would perform better because it sounded more enticing ...&lt;img src="http://feeds.feedburner.com/~r/VendorriskBlog/~4/ZlgDVVB9Aeo" height="1" width="1"/&gt;</description>
		<wfw:commentRss>http://blog.vendorrisk.com/2009/12/fun-with-rails-ab-testing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.vendorrisk.com/2009/12/fun-with-rails-ab-testing/</feedburner:origLink></item>
	</channel>
</rss>
