, SecurityFocus 2001-11-09
Five computer security firms join Microsoft to set an official standard for limiting disclosure of software security holes
Expand all |
Post comment
Shocking developments
2001-11-09
H Carvey <keydet89 (at) yahoo (dot) com [email concealed]> (2 replies)
H Carvey <keydet89 (at) yahoo (dot) com [email concealed]> (2 replies)
Such a policy for disclosure already exists
2001-11-09
Dumky (1 replies)
Dumky (1 replies)
Such a policy for disclosure already exists
2001-11-10
H Carvey <keydet89 (at) yahoo (dot) com [email concealed]>
H Carvey <keydet89 (at) yahoo (dot) com [email concealed]>
So what would force Microsoft to patch these holes if exploits are not published?
2001-11-10
Rafal Sybilla-Leszczynski (1 replies)
Rafal Sybilla-Leszczynski (1 replies)
So what would force Microsoft to patch these holes if exploits are not published?
2001-11-12
Anonymous
Anonymous
Microsoft have no server monopoly: this may reduce their share
2001-11-12
Kirsten Bayes (kirruth@hushmail)
Kirsten Bayes (kirruth@hushmail)

Anyone of these companies could have decided separately or amongst themselves, without Microsoft, to establish and adhere to a standard for disclosure. After all, each of the companies mentioned is made up of really smart guys. But by signing up with Microsoft, they can offer enhanced services to their customers. Scanner products will be far ahead of the others, across the board. Penetration testing and vulnerability assessment (throw incident response and forensics in there, too) will be second to none. Why? B/c these guys have the latest and greatest information, and also have a document to support their reasons for not disclosing their findings publicly.
Excellent move, really! No one can fault them for making a decision that's going to lead to their making much more money. And that's even if they don't share the vulnerabilities amongst themselves, within their coalition.
What remains to be seen is what other organizations will do. RFP, eEye, NMRC, Xato, etc...what will they do? Other organizations that base their products and services on vulnerability information are going to be at least...what...30 days behind the coalition? And that's assuming that (a) enough information is released to fully describe the vulnerability or if it isn't (b) the licensing agreement for the patch doesn't include a stipulation against reverse engineering it.
And how does NMRC fit into all this? Didn't hellNbak just call for Information Anarchy? And does Simple Nomad agree with his employer on this?
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/articles/281/8694#8694