| Javascript Feeds RSS Feed Security Dashboard | SearchSecurity.com |
|
The vicious circle of patch management Network administrators spend their days overwhelmed by the task of testing and deploying patches to vulnerable systems. It's not just the volume of patches that gets them down but, once patches have been deployed, they've got to worry that those fixes don't break other applications.
02/18/2004
|
|
Security Essentials: Patch Management as a Necessary Part of Defense In Depth a Case Study The purpose of this policy is to establish standards for the timely and continuous vulnerability scanning and patch management of equipment that is owned and operated by the Institute of Basic Cellular Research (IBCR). Effective implementation of this policy will minimize unauthorized access to Institute of Basic Cellular Research (IBCR) proprietary information and technology.
By Kay A. Cornwell, 02/18/2004
|
|
Patching Windows 2000 Installing Service Packs and hotfixes is an ongoing challenge. Each time you install a file or service from the original installation media, you must re-apply the Service Pack and Hotfixes (in case the original media installation installed a file that was subsequently addressed in a Service Pack or Hotfix). Typically, installation of the Service Pack prompts the user to reboot the host upon completion. Each hotfix also prompts the user to reboot the host. In some cases, this would require rebooting the machine 10+ times! On top of all this, the fixes must sometimes be installed in a particular order. Not many systems administrators have time to do this across the X number of machines in their enterprise.
02/18/2004
|
|
Patch management with GFI LANguard N.S.S. & Microsoft SUS Patch management is an essential network administration task and consists of scanning machines on the network for missing patches and deploying those patches as soon as they become available. This whi
02/18/2004
|
|
How to handle patch management "We see people looking for a tool that will solve all their problems, but what you need is a process; it's not just about the tool," says Felicia Nicastro, senior network systems consultant for International Network Services, a consulting firm that kicked off a patch management service in September. Nicastro says the biggest mistake companies make is leaving out the processes, such as diligent monitoring for new patches coupled with detailed evaluation, testing, deployment and validation that a team or individual manages.
By John Fontana, 02/18/2004
|
|
Beating Hackers to the Patch It’s a good thing the Blaster worm and its variations weren’t really insidious. Had it devastated hard drives, it could have inflicted billions of dollars in lost productivity and other damages global
02/18/2004
|
|
Automating Windows Patch Mngt: Part I Patch management could easily be called the bane of every administrator's existence, the pain in the rear of system management, or that never ceasing headache that pounds at CIOs everywhere. And I use the term "management" loosely. As I write this there are more than 40 updates that need to be applied to a new Dell computer running Windows XP. There were over 20 updates for Windows 2000 Service Pack 3 to apply to new systems before Microsoft released the fourth service pack in the summer of 2003. With this ever-growing hairball of security fixes, bug fixes, critical updates, and patches, might it be easier to disconnect all machines from the Internet and work with stone tablets than deploy new systems?
02/18/2004
|
|
Location Based Windows Patch Management In order to propagate, both these worms used known security vulnerabilities in the Windows operating system, vulnerabilities that at that time were already addressed by Microsoft and fixed by security updates it had released. The huge number of computers that were infected serves to show a lack, both in awareness on the side of users as well as in effective tools for administrators to consistently enforce a Windows patch management policy.
02/18/2004
|
|
Page: 12 3 |
