Follow GFI:
Find us on Facebook Follow us on Twitter Find us on Linkedin Subscribe to our RSS Feed Find us on YouTube Find us on Google+
 

Patch Deployment in 3 Easy Steps

on November 19, 2010

Picture a scenario of a network on 1000 hosts. On performing a network audit, it is found that 10 machines (servers and workstations) are un-patched. Although this might not seem like a large percentage (1%), one must keep in mind that it only takes one unprotected machine to infect and/or completely bring down an entire network.

Here are some of the potential repercussions of simply having 1 un-patched machine on the network:

  • Downtime and loss of productivity due to reinstallation
  • Questionable data integrity due to a successful exploit
  • Negative public relations due to systems unavailable for your customers
  • Legal problems should your patch management process go under a judicial microscope

Here are the simple three steps to successfully manage the patch deployment process using GFI LANguard:

  1. Scanning for vulnerabilities and building an application inventoryThe first step would be to establish an inventory of your organization’s network and the software deployed on it. Without a proper inventory, patching becomes a very daunting task. In addition to this, machines should also be prioritized by creating a risk profile based on their necessity to the organization. GFI LANguard ships with an applications inventory which provides a list of all applications detected during past scans.For the inventory discussed above to be populated automatically, an initial scan of all machines must be done. You can choose to run a scheduled custom scan to simply detect for missing patches and service packs. This would scan the machines to list the software installed on each one. The scan results would then save the applications detected in the scans in the applications inventory.With each new scan, any new applications which may have been installed would also be detected by the scan and added to the applications inventory. GFI LANguard would then automatically download any patches and service packs for the applications that need patching.
  2. Analyzing the resultsThe most important task following a network security scan is identifying which areas and systems require your immediate attention. This is achieved by analyzing and correctly interpreting the information collected and generated during a network security scan. Upon completing a scan, GFI LANguard immediately displays a scan summary that graphically displays the vulnerability level of the scanned computer or a combined interpretation of the scan results obtained following a network scan.The scan results also show a vulnerability level. A vulnerability level is a rating given by GFI LANguard to each computer after it has been scanned. This rating indicates the vulnerability level of a computer/network, depending on the number and type of vulnerabilities and/or missing patches found. See a complete list of software products supported by GFI LANguard. Once a scan has been performed, and its results analyzed, the final step would be to remediate the vulnerabilities.
  3. Remediating the vulnerabilitiesOnce you have performed a scan and analyzed the results, you can now configure GFI LANguard to automatically fix some of the issues identified during your network audit. This is achieved through the built-in tools that ship with the product. Available remediation actions include:
  • Auto-patch management – This remediation feature automatically downloads missing updates and deploys them network-wide.
  • Applications auto-uninstall – This remediation action enables the auto-uninstall of applications that support silent uninstall. This remediation action auto-uninstalls the applications of your choice from the application inventory outlined above. The process involves a test phase (called validation) during which an application is uninstalled automatically to identify if silent uninstall is supported by target application. If it is, all the other instances on the network will be automatically uninstalled during scheduled scans.

Sometimes drastic action may be necessary to protect your organization’s network. You can always disable the machine’s account and immediately start the patch management process on this infected/un-patched machine.

If this doesn’t work, then disable the switch port that the workstation connects to or move the machine to a quarantined network. This will allow you to remediate the vulnerabilities on this machine in a confined environment, without increasing the risk of the entire network getting infected.

 
Comments
taylor December 10, 20108:07 am

Patch deployment is never actually simple, but it’s great how this article pretty much distills the process down to its elements. A lot of time and effort goes into making sure that patch deployment goes as quickly and easily as possible, and when it doesn’t, that’s immediately countless hours down the drain with countless hour more to go. Not necessarily a situation that any company wants to experience first hand.

Jeremy Stenton December 10, 20108:14 am

I’ve actually had to work in scenarios where a network audit had turned up unpatched servers of less than 1% (more like .5 actually). And having been pressed for time on a particular project, had to run with the system in hopes that the majority of servers would make up for the unpatched ones. Unfortunately, we had the whole system crashing down on us in a matter of minutes and found ourselves worse of than when we first started.

philip c. January 5, 20114:42 am

Although there has been a lot of discussion on the implementation of either automated or non-automated patch management, I agree that the deployment of the actual patches themselves still have a lot of bearing on making sure a company’s workflow isn’t disrupted in the process. The steps and recommendations highlighted by this article are definitely good foundations to effectively rolling out a patch, whether it’s for an internal or external system.

Ben Vincenti January 11, 201112:40 pm

Hi everybody,

Thank you for your comments. Indeed patch deployment is never an easy task however, luckily, GFI LANguard simplifies this process. Furthermore, with the introduction of version 9.6, it is now possible to patch a plethora of software platforms. You can visit http://kbase.gfi.com/showarticle.asp?id=KBID003469 for more information.

Kind regards,

Ben Vincenti