« Responsible Product Management | Main | Boeing Paying Hackers to Break into Their Systems »



Feed You can follow this conversation by subscribing to the comment feed for this post.

Pierre Rasmussen

Great article and inspiring!

I personally don't work with secure software with purpose to stop
intruders. It's more keeping it up 24/7. But I can easy apply your framework on our development process.

My experience is that even if the design rules, tools and so on exists, how do I motivate the developers to read and use it? Or even better, seek new information.? I am a developer myself and I can't always blame the managers because they don't want to pay for the time. Some times there are developer that just do the minimum.

Bob Jones

Nice read, thanks!

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment

Comments are moderated, and will not appear until the author has approved them.

Your Information

(Name and email address are required. Email address will not be displayed with the comment.)

Sign Up for Alerts

Follow Us

Our Newsletter

Subscribe to our quarterly newsletter, The Application Security Report..

Other Featured Blogs

Dinis Cruz Blog, by Dinis Cruz

WhoIsJoe, by Joe Basirico