Ads by TechWords

See your link here
Receive the latest technology news and information.
Security
Computerworld Daily News (First Look and Wrap-Up)
Computerworld Blogs Newsletter
The Weekly Top 10
Cloud Computing
View all newsletters




Privacy Policy
 

Opinion: Make vendors pay for security flaws

November 1, 2004 12:00 PM ET

Computerworld - Information insecurity is costing us billions. We pay for it in theft -- information and financial theft. We pay for it in productivity loss, both when networks stop working and in the dozens of minor security inconveniences we all have to endure. We pay for it when we have to buy security products and services to reduce those other two losses. We pay for security, year after year.
Unfortunately, all the money we're spending isn't fixing the problem. We're paying, but we still end up with insecurities. The problem is insecure software.
It's bad design, poorly implemented features, inadequate testing, and security vulnerabilities from software bugs. The money we spend on security goes toward dealing with the effects of insecure software.
And that's the problem. We're not paying to improve the security of the underlying software. We're paying to deal with the vulnerabilities rather than eliminating them.
The only way to improve the situation is for the vendors to fix their software, and they won't do that until it's in their financial best interest to do so.
Today, the costs of insecure software aren't borne by the vendors that produce it. In economics, this is known as an externality: the cost of a decision that's borne by people other than those who are making the decision.
There are no real consequences to the vendors for having bad security or for having low-quality software. Even worse, the marketplace often rewards low quality. More precisely, it rewards additional features and timely release dates, even if they come at the expense of quality.
If we expect software vendors to reduce the number of features in their products, lengthen development cycles and invest in secure software development processes, it needs to be in their financial best interest to do so. If we expect corporations to spend significant resources on their own network security -- especially the security of their customers -- it needs to be in their financial best interest to do so.
Liability law is one way to make improving security in the best interests of those organizations.
The risk of liability raises the costs of doing it wrong and therefore increases the amount of money a CEO is willing to spend to do it right. Security is risk management; liability fiddles with the risk equation.
Basically, we have to tweak the risk equation so a vendor's CEO cares about actually fixing the problem. And putting pressure on his balance sheet is the best way to do that.
Clearly, this isn't all or



Jump to comments

Security

Additional Resources

Xerox
By using solid ink technology only from Xerox, you could save up to 65% by printing color for the cost of black and white. Enter for a chance to WIN a PhaserTM 8860 network color printer!
Microsoft
Save time and mitigate security risk. Deploy it now.
Sybase
In this white paper, IDC analyzes the role of next-generation mobile enterprise platforms as organizations seek a more strategic deployment of mobile solutions.

Learn the important issues you must consider before starting your next mobility initiative. Get your mobility white paper from IDC now, compliments of Sybase.

White Papers & Webcasts

Share our Strength
Download Now  

Managing Secure File Transfer to Save Time, Money and IT Resources
Learn how companies are using innovative technology to overcome these challenges and improve user productivity by offloading e-mail attachments and replacing FTP with...

Security Convergence Equals Network Security Cost Savings
Listen to IBM Internet Security Systems' take on network security convergence.

Disaster Recovery 2008: Reduced Costs and Improved Performance
How long can your Enterprise afford to be without your data? With an accelerated disaster recovery program, you never have to answer this...