| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <AANLkTi=xX9de8T9nZrY39zMcApp+aeZm3nati2qsqtEb@mail.gmail.com> Date: Sat, 28 Aug 2010 20:38:48 -0400 From: Jeffrey Walton <noloader@...il.com> To: Saad Bin Saleem <sbin.saleem@...glemail.com> Cc: full-disclosure@...ts.grok.org.uk, bugtraq@...urityfocus.com Subject: Re: Security coding sequence In the Microsoft world, see "The Security Development Life Cycle" (http://www.microsoft.com/learning/en/us/book.aspx?ID=8753) and "Threat Modeling" (http://www.microsoft.com/learning/en/us/book.aspx?ID=6892). Outside the Windows world, names line McGraw, Howard, LeBlanc, and Viega occur frequently. There's lots of other quality authors - just follow the references. On Thu, Aug 26, 2010 at 12:43 PM, Saad Bin Saleem <sbin.saleem@...glemail.com> wrote: > > Hello > > I am interested to know the development process or sequence of coding that > developers usually follow to develop functional and corresponding security > mechanism. I will highly appreciate, if anybody can share or send a link to > document containing specifications of security needs to fulfil. > > -- > Regards, > Saad > > _______________________________________________ > Full-Disclosure - We believe in it. > Charter: http://lists.grok.org.uk/full-disclosure-charter.html > Hosted and sponsored by Secunia - http://secunia.com/ > _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
Powered by blists - more mailing lists