Microsoft Updates Vulnerability Disclosure Policies

The software company clarifies its vulnerability-handling guidelines and begins issuing security bulletins for third-party products.

Strategic Security Survey: Global Threat, Local Pain (click image for larger view and for full slideshow)
Microsoft wants to sell you on coordinated vulnerability disclosures.
The company released new vulnerability disclosure policies on Tuesday. In particular, Microsoft updated its
coordinated vulnerability disclosure
(CVD) document, which details how it works with vulnerability researchers. The document was first introduced in July 2010.
The new CVD procedures delineate very carefully what all parties can expect from Microsoft in the vulnerability disclosure process, said Andrew Storms, director of security operations for nCircle, in an email interview. Its the first time a vendor has defined the various roles in a vulnerability disclosure and management process and created a set of deliverables for each role.
In addition, Microsoft has revised its staff guidelines. While employees were formerly encouraged to report any vulnerabilities they find in external products to the companys Microsoft Security Resource Center (MSRC), its now mandatory. Weve also made sure that theres a team that can help them, and thats the Microsoft Vulnerability Research team--aka MSVR--said Mike Reavey, director of the MSRC, in an interview. MSVR is the group at Microsoft that, as detailed in the CVD, works with external security researchers who report vulnerabilities to Microsoft.
For the first time, Microsoft has also begun to release public advisories for third-party products, and when possible coordinating the release of that information after the vendor has crafted a fix. On Tuesday, the company detailed one bug affecting Google Chrome and Opera, and another that just affected Chrome. Both have been patched.
All of these moves by Microsoft are aimed at bolstering uptake of coordinated vulnerability disclosures, in which vulnerability researchers share information about bugs theyve discovered with the relevant vendor, then wait to disclose the vulnerability publicly until a patch has been released. This approach was formerly dubbed responsible disclosure, but Microsoft gave it a makeover. The main reason for that shift was because the word responsible evoked a lot of emotional responses for people, said Reavey.
As that suggests, theres some debate amongst vulnerability researchers about the best way to
disclose vulnerabilities
. Proponents of rapid disclosure--aka not waiting for vendors--often claim that it leads to bugs being fixed more quickly. They also note that if theyve found it, attackers may already have found and been exploiting the vulnerability too. According to Microsoft, however, drawing upon our years of experience, we have seen that disclosing vulnerability details and/or exploits before a vendor has a chance to address the issue amplifies the risk of attacks.
Interestingly, while Microsofts new CVD commits the organization to the path of coordinated disclosures, Microsoft said it will publicly detail vulnerabilities in cases where the vendor is unresponsive and related attacks are already underway.
But one component lacking from Microsofts revised CVD, said some security experts, is a concrete
timeframe for fixes
.
Another criticism, at least historically, has been the difficulty of connecting with Microsoft vulnerability remediation staff. But security experts said that Microsoft has been improving. For the past two years or so, Ive seen a great improvement in the way Microsoft handles vulnerabilities. Still, sometimes the time to fix is high, since there are too many bug reports and it is very hard to prioritize, said Rodrigo Branco, vulnerability and malware research director at Qualys, in an email interview.
Another route for making contact with Microsoft, furthermore, is through a computer emergency readiness team (CERT), said Branco. He said this is an excellent approach--in general--if a vulnerability researcher is having difficult getting their vulnerabilities accepted by vendors, especially if both researcher and vendor have had little prior exposure to the process. Using a third party such as a CERT helps both with notification and influencing a vendor to tackle the problem.
Overall, many security experts said Microsoft is doing a relatively good job of improving the security of its products, both through
secure software development practices
, as well as mitigating bugs in its products relatively quickly. If you take into consideration that Microsoft doesnt pay for bugs like Google Chrome, then from my viewpoint, it looks like they are doing a pretty good job, said nCircles Storms.
He also recommends that security executives take a cue from how Microsoft has detailed its security vulnerability policies, to likewise set their own clear expectations and enforceable guidelines for their companys employees should disclose bugs.

Last News
▸ 7 arrested, 3 more charged in StubHub cyber fraud ring. ◂ Discovered: 23/12/2024 Category: security	▸ Nigerian scammers now turning into mediocre malware pushers. ◂ Discovered: 23/12/2024 Category: security	▸ Beware EMV may not fully protect against skilled thieves. ◂ Discovered: 23/12/2024 Category: security

**Cyber Security Categories**
Google Dorks Database	Exploits Vulnerability	Exploit Shellcodes

CVE List

Tools/Apps

News/Aarticles

Phishing Database

Deepfake Detection

Trends/Statistics & Live Infos

Tags:
Microsoft Updates Vulnerability Disclosure Policies