- Related Stories
-
Oracle wants to rein in database admins
April 25, 2006 -
Attack code out for Oracle database
April 20, 2006 -
When security researchers become the problem
July 27, 2005 -
Oracle dragging heels on unfixed flaws, researcher says
July 19, 2005
Chief Security Officer Mary Ann Davidson has hit out at an industry in which "most software people are not trained to think in terms of safety, security and reliability." Instead, they are wedded to a culture of "patch, patch, patch," at a cost to businesses of $59 billion, she said.
"What if civil engineers built bridges the way developers write code?" she asked. "What would happen is that you would get the blue bridge of death appearing on your highway in the morning."
Speaking at the WWW2006 conference in Edinburgh, Scotland, on Thursday, Davidson also touched on the wider subject of the state of the software and security industries.
The pressure to deal with the problem of unreliable and insecure software is building, and the industry has reached a "tipping point," she said.
It is now "chief executives who are complaining that what they are getting from their vendor is not acceptable, in terms of software assurance," Davidson said.
Things are so bad in the software business that it has become "a national security issue," with regulation of the industry currently on the agenda, she said. "I did an informal poll recently of chief security officers on the CSO Council, and a lot of them said they really thought the industry should be regulated," she said, referring to the security think tank.
But if regulation is coming, the industry has only itself to blame, she said.
"Industries don't want to be regulated, but if you don't want to be regulated, the burden is on you to do a better job."
Davidson also hit out at the "hacking mentality," and the incidence of exploits that could cause "a million dollars worth of damage...passed around freely at conferences." She said there was a major difference between people working in the software business and engineers who "are trained to think in terms of safety, security and reliability first."
She claimed that the British are particularly good at hacking as they have "the perfect temperament to be hackers--technically skilled, slightly disrespectful of authority, and just a touch of criminal behavior."
Colin Barker and Jonathan Bennett of UK.Builder.com reported from London.
See more CNET content tagged:
mentality, chief security officer, Oracle Corp., reliability, hacking






http://news.com.com/Flaw+hunters+pick+holes+in+Oracle+patches/2100-1002_3-5916171.html?tag=nl
Oct 27, 2005: Oracle password system comes under fire
http://news.com.com/Oracle+password+system+comes+under+fire/2100-1002_3-5918305.html?tag=st.rn
Nov 1, 2005: Halloween treat for Oracle: A database worm
http://news.com.com/Halloween+treat+for+Oracle+A+database+worm/2100-7349_3-5926641.html
Seems that the pot is calling the kettle black?
Kevin
http://news.com.com/Flaw+hunters+pick+holes+in+Oracle+patches/2100-1002_3-5916171.html?tag=nl
Oct 27, 2005: Oracle password system comes under fire
http://news.com.com/Oracle+password+system+comes+under+fire/2100-1002_3-5918305.html?tag=st.rn
Nov 1, 2005: Halloween treat for Oracle: A database worm
http://news.com.com/Halloween+treat+for+Oracle+A+database+worm/2100-7349_3-5926641.html
Seems that the pot is calling the kettle black?
Kevin
http://news.com.com/2100-7344-6069363.html?tag=tb
Fines and such work well for commercial companies, and they also need to clean up their acts.
On the bright side, if companies are held accountable for the quality of their software, we may see less jobs lost to outsourcing.
Here's the problem: For open source, who gets held accountable? If it's the keeper of the kernel, so to speak, such regulation could effectively kill open source. What company in their right mind would allow unaccountable non-employees to contribute to their code if it could potentially expose them to fines when the bugs inevitably turn up?
The solution to the problem is to look in the mirror and decide that an investment in internal process and Testing/QA is the way to improve the revenue stream by improving the reliability of the software. This along with higher customer satisfaction and renewal of licenses will improve the P&L. But it is a long term solution that a lot of companies do not want to invest in. The majority of software companies do not think this way.
http://news.com.com/2100-7344-6069363.html?tag=tb
Fines and such work well for commercial companies, and they also need to clean up their acts.
On the bright side, if companies are held accountable for the quality of their software, we may see less jobs lost to outsourcing.
Here's the problem: For open source, who gets held accountable? If it's the keeper of the kernel, so to speak, such regulation could effectively kill open source. What company in their right mind would allow unaccountable non-employees to contribute to their code if it could potentially expose them to fines when the bugs inevitably turn up?
The solution to the problem is to look in the mirror and decide that an investment in internal process and Testing/QA is the way to improve the revenue stream by improving the reliability of the software. This along with higher customer satisfaction and renewal of licenses will improve the P&L. But it is a long term solution that a lot of companies do not want to invest in. The majority of software companies do not think this way.
With software - the requirements are always changing by the user.
Of course some bridges don't work completely - they don't stand up to earthquakes, or can't hand an airplane crashing into them, or a boat/barge and they also get destroyed/broken. They also don't last forever and eventually fall apart.
Heck, I could still be happily using it for more than just a BBs platform if I didn't have to interact with other platforms. Well, and if the IP protocol support didn't suck. But then, driver support and game publishing for DOS has follen rather out of fashion.
Mind you, if I'd had access to Unix rather than Dos when I was seven I'd likely have never touched winblows.
Despite this persons employer, the points are valid.
I suspect the complaints are from lazy half-ass developers who don't know 10% of what they think they do abut software security. It is alarming how many professional programmers really don't understand what is going on in hardware, thus don't understand security issues.
If the software industry doesn't start cleaning up its act and take responsibility for its products(through warranties and other guarentees), governemt will step it and that will be to the detriment of everyone.
With software - the requirements are always changing by the user.
Of course some bridges don't work completely - they don't stand up to earthquakes, or can't hand an airplane crashing into them, or a boat/barge and they also get destroyed/broken. They also don't last forever and eventually fall apart.
Heck, I could still be happily using it for more than just a BBs platform if I didn't have to interact with other platforms. Well, and if the IP protocol support didn't suck. But then, driver support and game publishing for DOS has follen rather out of fashion.
Mind you, if I'd had access to Unix rather than Dos when I was seven I'd likely have never touched winblows.
Despite this persons employer, the points are valid.
I suspect the complaints are from lazy half-ass developers who don't know 10% of what they think they do abut software security. It is alarming how many professional programmers really don't understand what is going on in hardware, thus don't understand security issues.
If the software industry doesn't start cleaning up its act and take responsibility for its products(through warranties and other guarentees), governemt will step it and that will be to the detriment of everyone.
1) Software companies don't want to pay for the higher cost of doing software right.
2) Software companies learned from Gates that you need to be first to market to gain market share, then patch.
3) Not enough software engineers to meet companies demand for software.
You get the idea....
But hey! What do I know.
I *am* a software engineer!
1) Software companies don't want to pay for the higher cost of doing software right.
2) Software companies learned from Gates that you need to be first to market to gain market share, then patch.
3) Not enough software engineers to meet companies demand for software.
You get the idea....
But hey! What do I know.
I *am* a software engineer!
Of all the people... Oracle saying this? Surprising!! Not only their server systems, but their patches are also so full of bugs!
Of all the people... Oracle saying this? Surprising!! Not only their server systems, but their patches are also so full of bugs!
It is truly laughable :D
It is truly laughable :D
problem is you have managers who dont understand software quality and how long it takes to program. Less and less time is given to the coding aspect of a lifecycle and more to testing/fixing which if you do the coding right u need less time for testing/fixing, and more pressure is put on developers to rush using quick fixes instead of doing something properly!
Then higher up you have the customer who wants more, for less money in less time, its like forcing a surgeon to do a heart transplant in 5 minutes, you expect perfection in 5 minutes?
It's too easy to blame the developer, so thats what happenes!
problem is you have managers who dont understand software quality and how long it takes to program. Less and less time is given to the coding aspect of a lifecycle and more to testing/fixing which if you do the coding right u need less time for testing/fixing, and more pressure is put on developers to rush using quick fixes instead of doing something properly!
Then higher up you have the customer who wants more, for less money in less time, its like forcing a surgeon to do a heart transplant in 5 minutes, you expect perfection in 5 minutes?
It's too easy to blame the developer, so thats what happenes!
- Come again?
- by noahhoward May 27, 2006 8:52 PM PDT
- Tacoma Narrows bridge anyone? Bet they wished they could have patched that one.
- Like this Reply to this comment
-
Showing 1 of 3 pages (66 Comments)