|
Secure Programming
Writing Secure code Dec 27 2002 12:46PM Rahul Chander Kashyap (rahul nsecure net) (6 replies) Re: Writing Secure code Dec 27 2002 06:03PM Valdis Kletnieks vt edu (2 replies) RE: Writing Secure code Dec 27 2002 08:51PM Roger Alexander (rta cs colostate edu) (1 replies) RE: Writing Secure code Dec 30 2002 12:41PM Matt McClellan (mmcclellan nfr com) (2 replies) Re: Writing Secure code[update] Dec 31 2002 10:20AM Rahul Chander Kashyap (rahul nsecure net) (2 replies) Re: Writing Secure code Dec 27 2002 05:43PM John Viega (viega list org) (2 replies) |
|
Privacy Statement |
From here, version 2.1 of the CC is available.
On Wed, 1 Jan 2003 17:51:20 +0530
"K K Mookhey" <cto (at) nii.co (dot) in [email concealed]> wrote:
> This is pretty good, and needs not much introduction
> The Common Criteria for Information Technology Security Evaluation:
> Download at: http://csrc.nist.gov/cc/ccv20/ccv2list.htm
> The CC is also an ISO standard 15408:1999.
> This is what we attempt to follow as much as possible when evaluating
> software.
> There are also accredited agencies certified to do CC evals.
>
> K. K. Mookhey
> Chief Technology Officer
> Network Intelligence India Pvt. Ltd.
> Email: cto (at) nii.co (dot) in [email concealed]
> Web: www.nii.co.in
> Tel: 91-22-22001530/22006019
> =============================
> The Unix Auditor's Practical Handbook
> http://www.nii.co.in/tuaph.html
> =============================
>
>
> > So, how about directing our focus with a aim at reaching a
> > methodology/conclusion as to what can be done (by us + others) to say
> bring
> > up some ideas of some kind of a standard/practice which aims at following
> > certain guidelines to be taken at the design stage of any software
> > development process that could help us prevent the code getting
> > exploited.(If something like this already exists please do let me
> know..this
> > shall save a lot of time!).
>
>
>
[ reply ]