| Javascript Feeds RSS Feed Security Dashboard | SearchSecurity.com |
|
Vulnerability Risk Mitigation - Patching the Microsoft Windows Environment This manuscript discusses procedures for regularly patching a Microsoft Windows environment, beginning with a discussion what vulnerabilities are, how they find their way into developers' code, and why they have become such an issue. The balance of the paper presents a number of options for patching the vulnerabilities, using either freely available tools or products that require purchasing licenses.
03/28/2004
|
|
A Practical Methodology for Implementing a Patch Management Process The time between the discovery of an operating system or application vulnerability and the emergence of an exploit is getting shorter, sometimes only a matter of hours. This imposes pressures on IT managers to rapidly patch production systems which directly conflicts with configuration management best practices of quality assurance testing. Many organizations are struggling to keep current with the constant release of new patches and updates. At the same time, they are under pressure to provide near 100% availability of key business systems. IT organizations must develop a process to ensure the availability of resources, install required security patches and not break existing systems in the process. This paper presents one methodology for identifying, evaluating and applying security patches in a real world environment along with descriptions of some useful tools that can be used to automate the process.
03/26/2004
|
|
Methodologically Upgrading A Production System Patching and upgrading systems has been and still is a revolving task. System administrators receive security alerts, messages, and notifications of available software updates countless times on an irregular basis. We perform the patch, the upgrade, and the fix. A day later, we are informed of another security patch. What happens intermittently, when you receive the notification of a patch and when the patch is successfully applied to your production system? Simply applying the security patch to the production system(s) without executing a set of trial runs of the patch increases the risk of downtime to the user community of your system(s).
03/24/2004
|
|
Patching It Up I wonder what goes through Jay. F.'s head when I send another patch update with a few dozen servers to patch. Patch Management can be a headache, especially in a large network environment. It can also be disastrous if someone doesn't read the documentation that comes with patches or types the wrong command to upgrade a software package. Consequently, knowing how to back out of a botched patch job is just as important as knowing how to apply the patch.
03/02/2004
|
|
NIST - Procedures for Handling Security Patches To help address this growing problem, we recommend that organizations have an explicit and documented patching and vulnerability policy and a systematic, accountable, and documented process for handling patches. This document provides principles and methodologies for accomplishing this. One of several possible techniques is through the creation of a patch and vulnerability group (PVG). This group would facilitate the identification and distribution of patches within the organization.
By Peter Mell and Miles C. Tracy, 03/01/2004
|
|
A Patch in Time Victor Barra simply didn't have the staff to keep the more than 1,000 Windows servers at Siemens Medical patched. More than once, malware attacks brought down systems and cost the company hundreds of thousands of dollars. Last summer's Blaster worm was the last straw.
02/23/2004
|
|
Patch ROI Spreadsheet This is a free ROI calculator in a form of Excel spreadsheet that you can plug your numbers and see the patching cost is relevant to your enterprise.
02/23/2004
|
|
Automating Windows Patch Mngt: Part II In this segment of the Windows Patch Management series, you'll learn what happens on the client computers when SUS is active, how to monitor the client's patching activities, and how to fix or work around some common problems.
02/21/2004
|
|
Patch Management of Microsoft Products Using HFNetChkPro Shavlik Technologies Network Security Hotfix Checker Professional HFNetChkPro is the commercial, more full-featured version of the HFNetChk product distributed by Microsoft that allows administrators
02/18/2004
|
|
Windows patch management tools Patch management tools should identify accurately which patches are missing on each system, provide an easy means to deploy patches and provide administrative reports tracking patch status across multiple machines. The products we tested (see How we did it) attack the problem in two ways - with or without agent software. Agent-based products - such as those from PatchLink and BigFix - can greatly reduce network traffic by offloading processing and analysis to the target system, saving data until it needs to report to the central server. But they also force an administrator to manage software on all systems the product analyzes.
02/18/2004
|
|
Page: 1 2 3 |
