, SecurityFocus 2000-05-01
Security companies can make headlines by using the right jargon, even when it's wrong.
Expand all |
Post comment
A couple of comments
2000-05-01
Anonymous (3 replies)
Anonymous (3 replies)
Re: A couple of comments
2000-05-01
Elias Levy <aleph1 (at) securityfocus (dot) com [email concealed]> (1 replies)
Elias Levy <aleph1 (at) securityfocus (dot) com [email concealed]> (1 replies)
Re: A couple of comments
2000-05-01
Anonymous (1 replies)
Anonymous (1 replies)
Re: A couple of comments
2000-05-01
Elias Levy <aleph1 (at) securityfocus (dot) com [email concealed]> (3 replies)
Elias Levy <aleph1 (at) securityfocus (dot) com [email concealed]> (3 replies)
Re: A couple of comments
2000-05-02
Anonymous (1 replies)
Anonymous (1 replies)
Re: A couple of comments
2000-05-02
Elias Levy <aleph1 (at) securityfocus (dot) com [email concealed]>
Elias Levy <aleph1 (at) securityfocus (dot) com [email concealed]>
Re: A couple of comments
2000-05-02
Anonymous (2 replies)
Anonymous (2 replies)
Re: A couple of comments
2000-05-02
Elias Levy <aleph1 (at) securityfocus (dot) com [email concealed]> (1 replies)
Elias Levy <aleph1 (at) securityfocus (dot) com [email concealed]> (1 replies)
Re: A couple of comments
2000-05-02
Anonymous (1 replies)
Anonymous (1 replies)
Re: A couple of comments
2000-05-02
Elias Levy <aleph1 (at) securityfocus (dot) com [email concealed]>
Elias Levy <aleph1 (at) securityfocus (dot) com [email concealed]>

What we are lacking here is a common lexicon, that could provide clear definitions for these, and other, ITSEC terms. Was there not a bugtraq related project that sought to do just this, provide a common set of definitions for terminology related to vulnerabilities?
Further to this question, I would like to see us derive some more "professional" sounding terms for things like "back doors". If we are going to develop ITSEC into a serious profession, we really need to dispense with the "geek speak", and at least attempt to sound serious about our work!
[ reply ]
Link to this comment: http://www.securityfocus.com/comments/articles/25/1599#1599