-
Microsoft security servicing criteria
There’s some good info buried in here. Microsoft Security Servicing Criteria for Windows.
One of our goals in the Microsoft Security Response Center (MSRC) is to be more transparent with security researchers and our customers on the criteria we use for determining when we intend to address a reported vulnerability through a security update. Our belief is that improving transparency on this topic helps provide clarity on how we assess risk, sets expectations for the types of vulnerabilities that we intend to service, and facilitates constructive dialogue as the threat landscape evolves over time. Ultimately, we believe this enables us all to work together to better protect Microsoft’s customers.
There are links to two supporting documents, a lengthy report on how Microsoft identifies security problems (it’s by no means trivial), and how Microsoft assigns severity levels (“Critical,” “Important,” “Moderate,” “Low”) to a specific vulnerability. For example, in order for a security hole to rate a “Critical” rating for a regular ol’ Windows machine (not a server) it must meet this criteria:
Network Worms, or unavoidable common browsing/use scenarios where client is compromised without warnings or prompts.
- Elevation of Privilege (Remote) – The ability to either execute arbitrary code OR obtain more privilege than intended. Examples:
o Unauthorized File System Access – Writing to file system
o Execution of Arbitrary code – without extensive user action
o Exploitable memory corruption issues in remotely callable code (without extensive user action)
- Guest virtual machine
o In a virtualized environment, a vulnerability allows the guest VM to cause arbitrary code execution in the host
machine, effectively defeating the virtual machine boundary.The structure of the explanation leaves much to be desired, but the underlying intent seems sound to me.
What would you add? (Or remove?)