<?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: 5 Benefits of Automating Patch Management</title>
	<atom:link href="http://www.gfi.com/blog/5-benefits-automating-patch-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gfi.com/blog/5-benefits-automating-patch-management/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=5-benefits-automating-patch-management</link>
	<description>Brought to you by GFI Software</description>
	<lastBuildDate>Fri, 13 Sep 2013 13:27:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Cristian Florian</title>
		<link>http://www.gfi.com/blog/5-benefits-automating-patch-management/comment-page-1/#comment-18034</link>
		<dc:creator>Cristian Florian</dc:creator>
		<pubDate>Thu, 13 Jan 2011 10:23:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=3037#comment-18034</guid>
		<description><![CDATA[Thank you all for your comments. I&#039;m glad if this helps you and if you can see additional benefits feel free to increase the list with items that I have missed.]]></description>
		<content:encoded><![CDATA[<p>Thank you all for your comments. I&#8217;m glad if this helps you and if you can see additional benefits feel free to increase the list with items that I have missed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: keith</title>
		<link>http://www.gfi.com/blog/5-benefits-automating-patch-management/comment-page-1/#comment-17411</link>
		<dc:creator>keith</dc:creator>
		<pubDate>Mon, 03 Jan 2011 00:33:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=3037#comment-17411</guid>
		<description><![CDATA[To be completely honest, I don’t believe that there’s anything wrong with auto patching per say, but rather, there are key concerns with the current system of auto patching in our industry today. 

Though there are many pitfalls to auto patching, this article accurately highlights it’s undeniable benefits. I think, in due time, future iterations of auto patching systems will be able to incorporate the security and versatility of non-auto patching systems with the convenience of current auto patching systems.]]></description>
		<content:encoded><![CDATA[<p>To be completely honest, I don’t believe that there’s anything wrong with auto patching per say, but rather, there are key concerns with the current system of auto patching in our industry today. </p>
<p>Though there are many pitfalls to auto patching, this article accurately highlights it’s undeniable benefits. I think, in due time, future iterations of auto patching systems will be able to incorporate the security and versatility of non-auto patching systems with the convenience of current auto patching systems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris</title>
		<link>http://www.gfi.com/blog/5-benefits-automating-patch-management/comment-page-1/#comment-17211</link>
		<dc:creator>Kris</dc:creator>
		<pubDate>Thu, 30 Dec 2010 15:50:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=3037#comment-17211</guid>
		<description><![CDATA[Our company has actually reached an impasse on whether to adopt an automated patch management system or not. A good number of points have been raised both for and against an automated patch management system; and most (if not all) those points were raised in the two articles posted here at the GFI blog. We’re currently working without one, but I’m wondering if it may be time to make the switch based on the points raised in this article.]]></description>
		<content:encoded><![CDATA[<p>Our company has actually reached an impasse on whether to adopt an automated patch management system or not. A good number of points have been raised both for and against an automated patch management system; and most (if not all) those points were raised in the two articles posted here at the GFI blog. We’re currently working without one, but I’m wondering if it may be time to make the switch based on the points raised in this article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Natasha Edwards</title>
		<link>http://www.gfi.com/blog/5-benefits-automating-patch-management/comment-page-1/#comment-17059</link>
		<dc:creator>Natasha Edwards</dc:creator>
		<pubDate>Tue, 28 Dec 2010 05:35:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=3037#comment-17059</guid>
		<description><![CDATA[We currently have to do without our auto-patching management system, especially after a recent patch development screw up set us back a full week. Because of pressure from the coming holidays, a patch was pushed out way too early before it could go through the normal barrage of tests. The patch eventually went live, but we later discovered critical functionality problems. We eventually had to force all our systems to rollback, which took far more time than we could afford.]]></description>
		<content:encoded><![CDATA[<p>We currently have to do without our auto-patching management system, especially after a recent patch development screw up set us back a full week. Because of pressure from the coming holidays, a patch was pushed out way too early before it could go through the normal barrage of tests. The patch eventually went live, but we later discovered critical functionality problems. We eventually had to force all our systems to rollback, which took far more time than we could afford.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charlie</title>
		<link>http://www.gfi.com/blog/5-benefits-automating-patch-management/comment-page-1/#comment-15315</link>
		<dc:creator>Charlie</dc:creator>
		<pubDate>Fri, 10 Dec 2010 03:19:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.gfi.com/blog/?p=3037#comment-15315</guid>
		<description><![CDATA[I&#039;ve also read your previous article on the pitfalls of auto updating systems. They were very solid points all around but it&#039;s good to see that you guys are also doing articles on the other side of the coin. 

Personally, our company has been on an auto updating system for quite some time. But since we&#039;ve been suffering from the same problems you outlined in your last article, we&#039;ve been trying to devise ways on how to get around it. However, it&#039;s still true that auto updating does afford you an amount of convenience making it worth the effort.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve also read your previous article on the pitfalls of auto updating systems. They were very solid points all around but it&#8217;s good to see that you guys are also doing articles on the other side of the coin. </p>
<p>Personally, our company has been on an auto updating system for quite some time. But since we&#8217;ve been suffering from the same problems you outlined in your last article, we&#8217;ve been trying to devise ways on how to get around it. However, it&#8217;s still true that auto updating does afford you an amount of convenience making it worth the effort.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

 Served from: www.gfi.com @ 2013-09-15 03:18:18 by W3 Total Cache --