So, how can we edit current basic programming college books to present
secure code, a couple of words of the correct way of doing things, and a
whole new chapter on secure coding (which may be redudndent?)
How do we start?
Some Whiley book for introduction to CS?
Any volunteers to get this on the road?
Gadi.
On Wed, 11 Oct 2006, Kenneth Van Wyk wrote:
> So here's a lovely statistic for the software community to hang its
> hat on:
>
> http://news.zdnet.com/2100-1009_22-6124541.html?tag=zdfd.newsfeed
>
> Among other things, the article says, "Atlanta-based ISS, which is
> being acquired by IBM, predicts there will be a 41 percent increase
> in confirmed security faults in software compared with 2005. That
> year, in its own turn, saw a 37 percent rise over 2004."
>
> Of course, the real losers in this are the software users, who have
> to deal with the never ending onslaught of bugs and patches from
> their vendors. We've just _got_ to do better, IMHO, and automating
> the patch process is not the answer.
>
> Cheers,
>
> Ken
> -----
> Kenneth R. van Wyk
> KRvW Associates, LLC
> http://www.KRvW.com
>
>
>
>
>
_______________________________________________
Secure Coding mailing list (SC-L)
SC-L@securecoding.org
List information, subscriptions, etc - http://krvw.com/mailman/listinfo/sc-l
List charter available at - http://www.securecoding.org/list/charter.php
