|
|||||||||||
|
RE: Intrusion Risk Assessment
From: Fengmin Gong <fengmin(at)intruvert.com>
Date: Tue Jan 14 2003 - 14:02:36 EST
It's good to see that you are putting effort into this topic. Although there is a recognized need for a framework linking vulnerability assessment and countermeasures systematically from the research community for a while, the IDS data model and the IDMEF from IDWG represent the only widely supported standard effort, as Herve and others have pointed out. I want to mainly add on to one issue that has barely been brought up in the discussion. From a VA or IDS tool perspective, the impact severity rating can only take into account the "inherent" damaging effect, much like what you have started with. It can only reasonably account for the "direct" impact. For example, you may be able to determine if an vulnerability/attack leads to unprivileged remote access versus privileged access. This is only a direct impact in the sense anything could happen after a root compromise.
This impact is inherent in the sense that you have not accounted for
the "asset value" of the target being compromised. This information
may not generally be available to anyone outside the owning
organization. What it means is that the general framework must recognize
this and make provisions for the ultimate users to factor in their
asset value in the severity rating of such events. There are papers
on applying battlefield intelligence process to intrusion detection
that discusses asset value along with many other factors, see
Jim Yuill's page at:
To give you a more concrete example of how it can be done, IntruVert's IntruShield system has an underlying Threat and Countermeasure language that links exploits/attack conditions, affected systems and software, multiple detection methods/mechanisms, on-trigger response actions including packet logging, and other relevant info, all together on a per vulnerability basis. This lanaguage is very similar to IDWG model regarding intrusion event characterization but with many extensions to make it a complete Threat and Countermeasure language (I am a believer of the IDWG work, being involved in the Requirements Specification).
In IntruShield, the inherent impact severity of an attack is rated
from 0 to 9, while the confidence
The user, upon deployment, can then modify the severity ratings for any attacks to reflect their valuation of the asset under protection through customized policies. The new severity rating is then used in all the alert handling and reporting. FYI, I am also including an example list of the high-level impact categories used in IntruShield along with the severity rating guidelines. Informational
Reconnaissance
Exploits
DOS (including ddos)
Regards,
-- Dr. Fengmin Gong Director, Intrusion Detection Technologies IntruVert Networks, Inc. Email: fengmin@intruvert.com Voice: (408) 434-8306Received on Mon Jan 20 20:01:17 2003 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:01:05 EDT |
||||||||||
|
|||||||||||