| Javascript Feeds RSS Feed Security Dashboard | SearchSecurity.com |
|
Automating Windows Patch Management: Part III In this final installment of the series, you'll find a mixture of useful information: first, a discussion about two alternative, relatively low cost tools to manage the application of patches on Windows systems. Additionally, I'll cover some details of the upcoming revision to Software Update Services from Microsoft, due out later this year. I'll also talk a bit about the new monthly security update process from the company, how it might affect your organization, and then conclude the series.
By Jonathan Hassell, 07/13/2004
|
|
Patch DoS While we are all aware of the “ship first, patch later” methodology used in most IT projects, we are just starting to feel the ramifications of these methods as they relate to security in a 24x7x365, ecommerce environment.
By Chad Oleary, 07/08/2004
|
|
Securing Internet Explorer Through Patch Management Within this paper I will show you the importance of keeping IE patched throughout your network. I will go into the current state of patch management and demonstrate what could happen to your network if you leave IE unpatched. You will also receive inside information on how to mitigate the risk of IE being attacked through the application of strong security settings. Finally, I will discuss the need of a repeatable methodology for testing and deploying patches and how important it is to establish one at your firm.
By Ben Meader, 07/08/2004
|
|
Patch management with GFI LANguard N.S.S. & Microsoft SUS This white paper provides an overview of how to use GFI LANguard Network Security Scanner (N.S.S.) and Microsoft Software Update Services (SUS) to keep your network automatically updated with the latest security patches.
By GFI Software, 06/23/2004
|
|
Remote Scanning Utilities for Microsoft Hot Fixes and Service Packs The purpose of this paper is to show how security administration can benefit by the use of six utilities for remote scanning for Microsoft hot fixes and service packs on multiple Windows systems (NT, 2000, XP, IIS 4 and 5, SQL Server 7.0 and 2000, Exchange 5.5 and 2000, Windows Terminal Server, and Windows XP Home Edition).
By Larry Nicholl, 04/27/2004
|
|
Case Study:Use Caution When Deploying Microsoft's Software Update Service Recently, my company acquired the responsibility of providing infrastructure and technical support to a small, non-profit organization. Shortly after acquiring this responsibility, I experienced a "major" problem. Several end users had reported application errors after applying the latest Internet Explorer 5.5 update found on the Windows Update website (windowsupdate.microsoft.com). After a lengthy investigation, it was discovered that the update had modified a Windows system file, (gdi.exe) causing a protection fault whenever a user attempted to print from the company's financial software application (Solomon v2.6). In effect, the update acted like a virus, disabling the company's most important application.
By James McVicar, 04/26/2004
|
|
Management of Security Updates in the Windows 2000 Environment While the focus of this paper will be on the enterprise or corporate computing environment, some issues affecting the home or small business user will be highlighted as well. Also, the scope of this paper is limited to the Microsoft Windows 2000 server and Windows 2000/XP desktop operating systems, widely deployed Microsoft server applications such as SQL Server and Internet Information Services (IIS) Server, and key desktop applications such as Internet Explorer and the Office productivity suite. Although non-Microsoft operating systems and applications are not discussed here, proper management of security updates for these products is equally as important to the overall effectiveness of the security program.
By Jim Cebula, 04/26/2004
|
|
Using and Evaluating Windows Software Update Service This paper describes the installation and use of Microsoft's Software Update Service (SUS) for the deployment of Operating System patches. It will feature an in-depth discussion SUS' features, installation, configuration (both client and server side), and built-in security. Additionally, it will provide an analysis of SUS, its potential affect on an environment and any shortcomings found during its evaluation.
By John Ives, 04/25/2004
|
|
Oh Patch How I Hate Thee; Let Me Count the Ways Welcome back to the article series on security management. In this article we will discuss patches, dispel some of the mystery about them, and tell you how they will impact your security. When I first started writing this column I did not intend to talk about patches, but when I asked around, everyone I spoke to said I have to have one column on it. It is such an important topic that I could not ignore it. To that end, this is the patch column. It is a bit longer than what I would normally write because I am hoping I will not have to write another one. Unless something significant changes in the patch management world, I plan not to. Therefore, this is a rather lengthy column. Future columns will likely be shorter. As always, however, this column is for you, not me. If there is something you want me to cover, click the Comments link at the bottom of the page and tell me.
By Jesper M. Johansson, 04/23/2004
|
|
Microsoft Windows Security Patches This paper is for those who have a Microsoft Windows computer attached to the Internet, and haven't installed the latest Microsoft security patches. The first section is where to get these patches and how to install them. The second is why. Many people don't think it is important enough to keep current on the latest security patches released by Microsoft, at least not important enough to actually do it. Those are two main reasons I have come across for people to no t keep current on the latest MS Security patches. The first being how, and the second being expressed by "Do I really care?" A prudent person would also have a firewall (or two) between their MS Windows computer and the Internet as well, so hopefully I can convince the reader to do this as well.
03/28/2004
|
|
Page: 1 23 |
