Making Software Vendors Pay for Negligence


The U.K. House of Lords is considering transferring the costs of insecurity away from consumers


Email    print   
September 5, 2007 —  (Page 1 of 2)
The Chevrolet Corvair was recalled after consumer advocates claimed that it was unsafe at any speed; there was a clear commercial incentive for General Motors to manufacture safe products. But what incentive does the software industry have to produce secure software? The upper house of the British Parliament may not have much power, but it has the software business in its sights.

The Science and Technology Committee of the House of Lords published a report in August on personal Internet security, which concludes that it is all too easy for vendors to “dump risks” onto consumers through licensing agreements to avoid paying the costs of insecurity.

The report stated that efforts to promote best practices have been hampered by a lack of commercial incentives to make products secure. The committee’s solution is to propose transferring the cost of insecurity onto demonstrably negligent hardware and software manufacturers, with the long-term goal of establishing a framework for vendor liability across Europe.

The report makes detailed recommendations about the form of the proposed law. It also details short-term goals such as enacting data breach notification laws, providing guidance to the courts, researching IT security, and suggesting best practices for the software industry.

Graham Titterington, a principal analyst at Ovum specializing in IT security and business continuity, believes that the committee’s proposals are impractical. “The complexity of all of the issues is too great to legislate in a universal fashion. In the event that defects are known and reported and not fixed in a reasonable manner, there are areas where negligence would be appropriate. Automatic liability for all errors is not realistic.”

Titterington added that the industry simply does not have the knowledge and technology to produce totally secure software. Indeterminate factors such as whether the consumer has taken steps to mitigate vulnerabilities, the extent to which the software is being used, and the class and value of the software are the gray area of the law.




Pages 1 2 


Share this link: http://sdt.bz/31110
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
New York City to open Academy for Software Engineering
High school would give foundational education in technology Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb