Collaboration in a Secure Development Process, Part 1
by Gunnar Peterson - Wednesday, 4 August 2004.
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

USBdriveby: Compromising computers with a $20 microcontroller

Posted on 19 December 2014.  |  Security researcher Samy Kamkar has devised a fast and easy way to compromise an unlocked computer and open a backdoor on it: a simple and cheap ($20) pre-programmed Teensy microcontroller.


Weekly newsletter

Reading our newsletter every Monday will keep you up-to-date with security news.
  



Daily digest

Receive a daily digest of the latest security news.
  
DON'T
MISS

Fri, Dec 19th
    COPYRIGHT 1998-2014 BY HELP NET SECURITY.   // READ OUR PRIVACY POLICY // ABOUT US // ADVERTISE //