The Price of Restricting Vulnerability Publications: Difference between revisions

From Cybersecurity Wiki
Jump to navigation Jump to search
(New page: ==The Price of Restricting Vulnerability Publications== Jennifer Stisa Granick, ''The Price of Restricting Vulnerability Publications'' (2007). [http://www.ijclp.net/files/ijclp_web-doc_...)
 
No edit summary
Line 2: Line 2:


Jennifer Stisa Granick, ''The Price of Restricting Vulnerability Publications'' (2007).  [http://www.ijclp.net/files/ijclp_web-doc_10-cy-2004.pdf  ''Web'']  
Jennifer Stisa Granick, ''The Price of Restricting Vulnerability Publications'' (2007).  [http://www.ijclp.net/files/ijclp_web-doc_10-cy-2004.pdf  ''Web'']  
[http://cyber.law.harvard.edu/cybersecurity/?title=Special:Bibliography&action=viewsource&startkey=Granick:2005&f=wikibiblio.bib ''BibTeX'']
[http://cyber.law.harvard.edu/cybersecurity/?title=Special:Bibliography&action=viewsource&startkey=Granick:2005&f=wikibiblio.bib ''BibTeX'']



Revision as of 10:25, 3 June 2010

The Price of Restricting Vulnerability Publications

Jennifer Stisa Granick, The Price of Restricting Vulnerability Publications (2007). Web BibTeX

Categorization

Issues: Disclosure; Information Sharing

Key Words

information security, vulnerability disclosure, disclosure policy, exploit, code as speech

Synopsis

There are calls from some quarters to restrict the publication of information about security vulnerabilities in an effort to limit the number of people with the knowledge and ability to attack computer systems. Scientists in other fields have considered similar proposals and rejected them, or adopted only narrow, voluntary restrictions. As in other fields of science, there is a real danger that publication restrictions will inhibit the advancement of the state of the art in computer security. Proponents of disclosure restrictions argue that computer security information is different from other scientific research because it is often expressed in the form of functioning software code. Code has a dual nature, as both speech and tool. While researchers readily understand the information expressed in code, code enables many more people to do harm more readily than with the non-functional information typical of most research publications. Yet, there are strong reasons to reject the argument that code is different, and that restrictions are therefore good policy. Code's functionality may help security as much as it hurts it and the open distribution of functional code has valuable effects for consumers, including the ability to pressure vendors for more secure products and to counteract monopolistic practices.

Additional Notes and Highlights