Is a full vulnerability disclosure strategy a responsible approach?

Is a full vulnerability disclosure strategy a responsible approach?

Do you think campaigns like Abyssec security's "Month of Bugs" actually work to improve information security, or do they end up being more for show?

    Requires Free Membership to View

    SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!

    Michael S. Mimoso, Editorial Director

    By submitting your registration information to SearchSecurity.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSecurity.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

Abyssec Security Research's "Month of Bugs" has the potential to improve information security, as long as the researchers closely work with the companies and developers in whose software they find bugs . At this point, the research firm's goals appear to be to put additional pressure on software developers to create secure software, to release more technical details on vulnerabilities and to promote the company's research.

Abyssec is following a full vulnerability disclosure strategy. Since 1993 and the formation of the Bugtraq mailing list, there has been a significant disagreement regarding how vulnerabilities should be disclosed; the list was formed to discuss vulnerabilities regardless of the vendor response in order to pressure vendors into patching their software. One of Abyssec's goals in using full disclosure is to pressure software developers to fix their code faster than exploit writers can develop exploits, but, given the current speed exploits are developed, this is probably a losing battle for software developers. Abyssec is planning on releasing more details than are commonly released in order to assist security professionals with determining the amount of risk these vulnerabilities pose to their organizations, as well as with developing effective mitigation strategies. Promoting their company, however, is the most likely long-term result of the "Month of Bugs" campaign.

While some may question Abyssec's motivation, the fact that they are openly sharing the results of their findings -- rather than selling the vulnerabilities to the highest bidder on the black market -- will help improve information security, since all enterprises can freely use the information to make informed decisions. The stakes of employing such vulnerability disclosure tactics are high; however, until the vulnerabilities are patched, they're left wide open to exploitation by malicious attackers . If the researchers worked with software developers prior to announcing a vulnerability, they could help minimize these high costs to end users and also satisfy their goals.

This was first published in September 2010

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.