Comments on: The Problem with Patching Is – Not Patching! http://www.gfi.com/blog/the-problem-with-patching-is-not-patching/?utm_source=rss&utm_medium=rss&utm_campaign=the-problem-with-patching-is-not-patching Brought to you by GFI Software Tue, 06 Aug 2013 14:24:30 +0000 hourly 1 By: Jackie Wake http://www.gfi.com/blog/the-problem-with-patching-is-not-patching/comment-page-1/#comment-55428 Jackie Wake Tue, 06 Aug 2013 10:14:04 +0000 http://www.gfi.com/blog/?p=10753#comment-55428 You raise some good points Craig…

In terms of best practice, we recommend checking for missing patches once per day, with deployment scheduled once per week, unless a patch is critical.

Of course, it always pays to be on the lookout for the most popular applications, as these are the ones most exploited – Microsoft patches, Java, Adobe Flash Player and Reader and major web browsers.

This is the best practice our tool, GFI Cloud supports :-)

]]> By: Craig Kelly http://www.gfi.com/blog/the-problem-with-patching-is-not-patching/comment-page-1/#comment-55344 Craig Kelly Fri, 02 Aug 2013 16:45:05 +0000 http://www.gfi.com/blog/?p=10753#comment-55344 Great article,

With patching I find the question is where do you draw the line? As you suggest new patches come out daily for some software components. Do you patch daily, monthly, 6 monthly? The answer I think is dependent on the infrastructure component / software itself, however it can be hard to get agreement for what these timescales should be. Particularly if a major issue is caused by a bug that would have been solved with the latest patch.

Thanks for the post, enjoyed reading it.

]]>