Affiliations: [a] Department of Information Systems, University of Maryland, Baltimore County, Baltimore, MD 21250, USA. E-mail: [email protected] | [b] The MITRE Corporation, McLean, VA 22102-3481, USA. E-mail: [email protected], [email protected] | [c] Center for Secure Information Systems and Department of Information and Software Engineering, George Mason University, Fairfax, VA 22030-4444, USA. E-mail: [email protected]
Abstract: System protection mechanisms such as access controls can be fooled by authorized but malicious users, masqueraders, and misfeasors. Intrusion detection techniques are therefore used to supplement them. However, damage could have occurred before an intrusion is detected. In many computing systems the requirement for a high degree of soundness of intrusion reporting can yield poor performance in detecting intrusions and cause long detection latency. As a result, serious damage can be caused either because many intrusions are never detected or the average detection latency is too long. The process of bounding the damage caused by intrusions during intrusion detection is referred to as intrusion confinement. We justify the necessity for intrusion confinement during detection by using a probabilistic analysis model, and propose a general solution to achieve intrusion confinement. The key idea of the solution is to isolate likely suspicious actions before a definite determination of intrusion is reported. We also present two concrete isolation protocols in the database and file system contexts, respectively, to evaluate the feasibility of the general solution, which can be applied to many types of information systems.
