Collaboration in a Secure Development Process, Part 1
by Gunnar Peterson - Wednesday, 4 August 2004.
Bookmark and Share
You have to ask yourself: why is there so much bad code? How many times have you heard the statement to the effect of: "if only the developers had built these applications with security in mind, we wouldn't have these security problems?" At the same time, the developers may say: "We built to spec, give us security specifications and we will make it happen!"

The purpose of this article is to examine specific ways that the security and development teams can collaborate while software is being designed and developed as opposed to only patching software once it has been deployed. Software is extremely malleable in the design and development phase, once the architectural layers, tiers, and distribution models are set and the application is deployed, then the cost and complexity of making changes rises dramatically.


Download the paper in PDF format here.

Spotlight

The CSO perspective on healthcare security and compliance

Posted on 20 May 2013.  |  Randall Gamby is the CSO of the Medicaid Information Service Center of New York. In this interview he discusses healthcare security and compliance challenges and offers a variety of tips.


Daily digest

By subscribing to our early morning news update, you will receive a daily digest of the latest security news published on Help Net Security.
  

Weekly newsletter

With over 500 issues so far, reading our newsletter every Monday morning will keep you up-to-date with security risks out there.
  

 
DON'T
MISS

Tue, May 21st
    COPYRIGHT 1998-2013 BY HELP NET SECURITY.   // READ OUR PRIVACY POLICY // ABOUT US // ADVERTISE //