What Can Be Done About Software Security?


Good project management, enterprisewide commitment, ongiong training seen as crucial


Email    print   
July 1, 2007 —  (Page 1 of 7)
Security flaws darken the sky over every company that encounters them. The consequences can be so severe that it is remarkable flaws continue to persist after years of stakeholders enduring the expense, pain and risks associated with insecurity. But just as a spate of failures of cast-iron bridges in the early years of Victoria’s reign caused the British government to regulate railroad construction, so too may failures in software security lead to future government controls on how code is written.

Gunter Ollmann, director of security strategy for IBM’s Internet Security Systems division, reported in May 2007 that ISS researchers had analyzed more than 7,000 publicly disclosed bugs in 2006. Strikingly, Ollmann estimated that the number of new code vulnerabilities could exceed 139,362 per year, increasing the perceived risk of zero-day vulnerabilities exponentially.

Software has transformed into a critical part of our infrastructure, yet its architectural standards are not on par with physical structures such as bridges. Although every situation is different, the experts SD Times interviewed for this story reached consensus on some of the most common underlying factors that beget flaws: Fundamental project management, organizational commitment and training were the most frequently discussed topics among those interviewed.

John Heimann, Oracle’s program director in the global security product group, observed that most companies have not defined standards for secure coding. But management must define standards, explain what they mean to developers, and measure developers on their achievement, he said.

Tight schedules may also lead to lax software security. Rex Black, president and principal consultant of Rex Black Consulting Services, said that schedule pressures drive out a lot of things required to produce quality software. “[Management believes] that pressure is part of getting peak performance out of an organization. There is frustration at the contributor level about constant pressure to meet dates. You can’t be surprised when [developers] don’t deliver fully functional or secure code.”

SPI Dynamics co-founder Caleb Sima remarked that even if management conveyed requirements precisely, another problem is that the person who created those requirements needs to know security. “Product managers deal with customers, not security. There must be a dedicated guy helping the product manager.”




Pages 1 2 3 4 5 6 7 


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

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Cigital Develops Ready-to-Use Tools for Securing the Smart Grid
Cigital Inc. announced the release of the Guide to Developing a Cyber Security and Risk Mitigation Plan 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