Process, Best Practices Are Best Defense


Government task force recommends ways to improve software security


Email    print   
January 15, 2005 —  (Page 1 of 2)
Education and training of software developers, as well as creating and sharing best practices for improving quality, are among recommendations made last month by the U.S. government-sponsored Security Across the Software Development Lifecycle task force for creating more secure applications.

The task force split into subgroups that reflect the issues involved, according to co-chair Ron Moritz of Computer Associates. In its executive summary, the task force said security is a research and education issue for universities, and involves skills, processes and testing for developers, requirements for software customers, and a patching issue for IT administrators.

“One of the key recommendations is to look at how we train engineers, and re-educating longtime practitioners,” Moritz said.

According to the summary, the education subgroup recommends that “software become a core component of software development programs at the university level with sufficient resources to build the academic capacity to improve secure software development.”

The group also recommends a certificate program for security professionals and supports creating software centers of excellence. Moritz added that one of the goals would be the funding of academic chairs at select universities in the area of secure software development.

Moritz said the group also advocates academic research into language design.

“The last major language introduced was Java,” said Moritz; the language was officially announced in May 1995. “It was an improvement over C++ in terms of security issues. But now, no faculty is researching software languages. Could a language be written that would ensure secure code?”

One subgroup urges the establishment of a security verification and validation program to evaluate different software development processes and practices for effectiveness in producing secure software.

A patching subgroup worked to define ways to make the process of patching simple and reliable, Moritz said. It developed guiding principles for patch management and recommended the adoption of a “top ten list” of best practices.

Another important area, according to Moritz, was finding ways to motivate developers to create more secure software, as well as disincentives for criminal and malicious behavior. “Problems come from executives pushing things into the market to provide a new service or product to stay ahead of the competition,” Moritz said. The incentives subgroup recommended making the security of software one measure of a developer’s job performance.




Pages 1 2 


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

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Zeichick’s Take: Looking for the best of the best of the best
It's time once again for readers to send in nominees for the SD Times 100 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