微软素材库合集(超级绝版)(表格篇)

Deploy the patch within six months
Low
Depending on expected availability, wait for next service pack or patch rollup that includes the patch, or deploy the patch within one year
Reduced patch-related reboots
Developing consistent tools
Developing more capable tools
Choosing A Patch Management Solution
Customer type
Consumer
Байду номын сангаас
Scenario
Severity rating
Recommended patching time frame
Critical Within 24 hours Important Within one month
Recommended maximum
patching time frame
Within two weeks
Exploitation is extremely difficult or impact is minimal
Security Bulletin List: http://www.Microsoft.com/TechNet/Security/Current.asp
Patching Time Frames
Exploitation is serious, but is mitigated to a significant degree by default configuration, auditing, need for user action, or difficulty of exploitation
All patches, service packs,
Security and security rollup patches, critical updates, and service packs for the above operating systems
All scenarios
Small organization
Medium-sized or large enterprise
Has no Windows servers
Has one to three Windows 2000 or newer servers and one IT administrator
Solution
Windows Update
Windows Update
MBSA and SUS
MBSA and SUS
SMS
Patch Management Solution For MediumSized And Large Organizations
Capability
SUS 1.0
SMS 2003
第二篇 表格篇
Microsoft Patch Severity Ratings
Rating Critical Important
Moderate Low
Definition
Exploitation could allow the propagation of an Internet worm
Exploitation could result in compromise of user data or the availability of processing resources
Windows 2000
Supported Windows XP Platforms for Windows Server 2003 Content
Windows NT 4.0 Windows 98 Windows 2000 Windows XP Windows Server 2003
Supported Content Types
Wants a patch management solution with basic level of control that updates Windows 2000 and newer versions of Windows
Wants a single flexible patch management solution with extended level of control to patch, update, and distribute all software
Deploy the patch within one year, or choose not to deploy at all
Improving The Patching Experience
Your need
Reduce patch frequency
Reduce patching complexity Reduce risk of patch deployment
Reduce patch size
Reduce downtime Improve tool consistency Improve tool capabilities
Microsoft’s response Reduced frequency of non-emergency patch releases from once per week to once per month Reduced number of patch installer technologies Improved patch quality and introduced patch rollback capability Developed “delta patching” technology to reduce patch size
Within two months
Moderate
Depending on expected availability, wait for next service pack or patch rollup that includes the patch, or deploy the patch within four months