Category talk:Threat Agent

Revision as of 03:58, 27 May 2009 by Deleted user (talk | contribs)

Jump to: navigation, search

auto california charitable donation links [ countryroad australia ] [ african american migrations from south to north ] africa symbol [ asia asian cream cute girl pure ] [ asia cheap hotel singapore ] [ dr solomons antivirus toolkit ] [ koigokoro fantasia ] [ uk australia travel visa ] [ west african kingdoms ghana ] [ africas capitals and countries ] [ education gazette australia ] [ global stewardship foundation africa ] asian twinks video [ norton antivirus 2005 cracked ] [ asian import model picture ] sitemap site [ automatic back scratcher ] [ australia veterans affairs ] [ accident auto chipley florida lawyer ] [ asian lion habitat ] [ australia australian hotel ] [ david wilson automotive group ] [ antivirus for worms ] [ computer associates antivirus download ] [ escan antivirus software ] automotive suspension types index [ dodge auto parts ] url [ mitsubishi autos ] [ migrated to australia ] auto automobile body car paint tattoo [ islam spread africa ] [ avg free antivirus download ] [ asianow ] [ australia goverment immigration ] [ australia festival in market victoria ] [ africana conceito da familia ] [ australian open tennis results mens final ] [ how to uninstall norton antivirus 2003 ] [ asian moon festival 2005 ] [ manually uninstall symantec antivirus corporate edition ] [ avg+antivirus+software ] antivirus software server [ rental accommodation melbourne australia ] I can appreciate the attempt made to clarify threats with respect to risk, but a redirection on the wiki from threat to threat agent does not, in my opinion, clarify the most basic concept of threat. The definition of 'threat agent' is distinct from the definition of 'threat'. Agent implies a causative entity and, in the case of the wiki entry, I think has been roughly sketched. What has not been done yet is to define the types of events (the threat) the causative entity (threat agent) brings about. Perhaps a rough workflow of a standard security event (a system compromise) will serve to identify the necessary components that need definition. This may also provide the context needed to keep the definitions from shifting. Here is my previous comment on threat: Category_talk:Threat

Thanks for the comments. You're absolutely right. The intent was not to indicate that 'threat' and 'threat agent' are the same thing. We simply moved the page and it left a redirect behind automatically. I like the idea of creating a model for the 'workflow' or attack-flow or risk-flow or whatever. Can you help us put an article together?