Network Security: Vulnerabilities and Disclosure Policy
Software security is a major concern for vendors, consumers, and regulators since attackers that exploit vulnerabilities can cause substantial damages. When vulnerabilities are discovered after the software has been sold to consumers, the firms face a dilemma. A policy of disclosing vulnerabilities and issuing updates protects only the consumers who install updates, while the disclosure itself facilitates reverse engineering of the vulnerability by hackers. The paper develops a setting that examines the economic incentives facing software vendors and users when software is subject to vulnerabilities. We consider a firm that sells software which is subject to potential security breaches. The firm needs to set the price of the software and state whether it intends to disclose vulnerabilities and issue updates. Consumers differ in their value of the software and the potential damage that hackers may inflict and need to decide whether to purchase the software as well as whether to install updates. Prices, market shares, and profits depend on the disclosure policy of the firm. The paper analyzes the market outcome and derives the conditions under which a firm would disclose vulnerabilities. It then examines the effect of a regulatory policy that requires mandatory disclosure of vulnerabilities. The paper discusses the incentives to invest in product security by investigating how a decline in the number of vulnerabilities and an increase in the probability that the firm will identify vulnerabilities ex-post (before hackers) affect disclosure policy, price and profits.
|Date of creation:||Feb 2007|
|Date of revision:|
|Contact details of provider:|| Postal: Centre for Economic Policy Research, 77 Bastwick Street, London EC1V 3PZ.|
Phone: 44 - 20 - 7183 8801
Fax: 44 - 20 - 7183 8820
|Order Information:|| Email: |
When requesting a correction, please mention this item's handle: RePEc:cpr:ceprdp:6134. See general information about how to correct material in RePEc.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: ()The email address of this maintainer does not seem to be valid anymore. Please ask to update the entry or send us the correct email address
If references are entirely missing, you can add them using this form.