
<?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: 3 Reasons Against Patch Tuesday</title>
	<atom:link href="http://www.savidtech.com/blog/network-security/3-reasons-against-patch-tuesday/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.savidtech.com/blog/network-security/3-reasons-against-patch-tuesday/</link>
	<description>Savid Technologies thoughts on technology, IT, information security, and business</description>
	<lastBuildDate>Sat, 15 May 2010 02:01:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: RickSheikh</title>
		<link>http://www.savidtech.com/blog/network-security/3-reasons-against-patch-tuesday/comment-page-1/#comment-62</link>
		<dc:creator>RickSheikh</dc:creator>
		<pubDate>Tue, 01 Sep 2009 15:13:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.whatevercompliance.com/?p=196#comment-62</guid>
		<description>It has not ceased to amaze me how much confusion there seems to be within an Internal Security Team at a firm regarding finding the right &quot;patch cycle&quot;. I have heard suggestions from &quot;patch every 3 days&quot; to &quot;quarterly patching&quot; and with latter the vulnerability threshold exceeding up to 3 Patch Tuesdays, and with a reasonable guess based on the trend, that vulnerability amounts to being 25 critical patches behind on your business critical systems. 

Regarding the point # 2 raised in your post. I usually take care of that by using Patch Management Solution that pre-stage the patches internally (such as WSUS) on the Patch Tuesday, so the down-level streaming to the clients happen internally thus consuming no external bandwidth.

-Rick</description>
		<content:encoded><![CDATA[<p>It has not ceased to amaze me how much confusion there seems to be within an Internal Security Team at a firm regarding finding the right &#8220;patch cycle&#8221;. I have heard suggestions from &#8220;patch every 3 days&#8221; to &#8220;quarterly patching&#8221; and with latter the vulnerability threshold exceeding up to 3 Patch Tuesdays, and with a reasonable guess based on the trend, that vulnerability amounts to being 25 critical patches behind on your business critical systems. </p>
<p>Regarding the point # 2 raised in your post. I usually take care of that by using Patch Management Solution that pre-stage the patches internally (such as WSUS) on the Patch Tuesday, so the down-level streaming to the clients happen internally thus consuming no external bandwidth.</p>
<p>-Rick</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 3 Reasons Against Patch Tuesday &#124; Whatever Compliance &#8211; Michael A &#8230; &#124; Hack In The Box</title>
		<link>http://www.savidtech.com/blog/network-security/3-reasons-against-patch-tuesday/comment-page-1/#comment-56</link>
		<dc:creator>3 Reasons Against Patch Tuesday &#124; Whatever Compliance &#8211; Michael A &#8230; &#124; Hack In The Box</dc:creator>
		<pubDate>Wed, 29 Jul 2009 05:04:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.whatevercompliance.com/?p=196#comment-56</guid>
		<description>[...] the original post: 3 Reasons Against Patch Tuesday &#124; Whatever Compliance &#8211; Michael A &#8230;   Share and [...]</description>
		<content:encoded><![CDATA[<p>[...] the original post: 3 Reasons Against Patch Tuesday | Whatever Compliance &#8211; Michael A &#8230;   Share and [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
