ACM Home Page
Please provide us with feedback. Feedback
Backtracking intrusions
Full text PdfPdf (647 KB)
Source ACM Transactions on Computer Systems (TOCS) archive
Volume 23 ,  Issue 1  (February 2005) table of contents
Pages: 51 - 76  
Year of Publication: 2005
ISSN:0734-2071
Authors
Samuel T. King  University of Michigan, Ann Arbor, MI
Peter M. Chen  University of Michigan, Ann Arbor, MI
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 30,   Downloads (12 Months): 232,   Citation Count: 10
Additional Information:

abstract   references   cited by   index terms   review   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1047915.1047918
What is a DOI?

ABSTRACT

Analyzing intrusions today is an arduous, largely manual task because system administrators lack the information and tools needed to understand easily the sequence of steps that occurred in an attack. The goal of BackTracker is to identify automatically potential sequences of steps that occurred in an intrusion. Starting with a single detection point (e.g., a suspicious file), BackTracker identifies files and processes that could have affected that detection point and displays chains of events in a dependency graph. We use BackTracker to analyze several real attacks against computers that we set up as honeypots. In each case, BackTracker is able to highlight effectively the entry point used to gain access to the system and the sequence of steps from that entry point to the point at which we noticed the intrusion. The logging required to support BackTracker added 9&percent; overhead in running time and generated 1.2 GB per day of log data for an operating-system intensive workload.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
 
3
 
4
CERT. 2000. Steps for recovering from a UNIX or NT system compromise. Tech. rep. CERT Coordination Center. Available online at http://www.cert.org/tech_tips/win-UNIX-system_compromise.html.
 
5
CERT. 2001. Detecting signs of intrusion. Tech. rep. CMU/SEI-SIM-009. CERT Coordination Center. Available online at http://www.cert.org/security-improvement/modules/m09.html.
 
6
CERT. 2002a. CERT/CC overview incident and vulnerability trends. Tech. rep. CERT Coordination Center. Available online at http://www.cert.org/present/cert-overview-trends/.
 
7
CERT. 2002b. Multiple vulnerabilities In OpenSSL. Tech. rep. CERT Advisory CA-2002-23. CERT Coordination Center. Available online at http://www.cert.org/advisories/CA-2002-23.html.
 
8
Cheswick, B. 1992. An evening with Berferd in which a cracker is lured, endured, and studied. In Proceedings of the Winter 1992 USENIX Technical Conference. 163--174.
 
9
Christie, A. M. 2002. The Incident Detection, Analysis, and Response (IDAR) Project. Tech. rep. CERT Coordination Center. Available online at http://www.cert.org/idar.
 
10
CIAC. 2001. L-133: Sendmail debugger arbitrary code execution vulnerability. Tech. rep. Computer Incident Advisory Capability. Available online at http://www.ciac.org/ciac/bulletins/l-133.shtml.
11
12
 
13
Farmer, D. 2000. What are MACtimes? Dr. Dobb's J. 25, 10 (Oct.), 68, 70--74.
 
14
Farmer, D. 2001. Bring out your dead. Dr. Dobb's J. 26, 1 (Jan.), 104--105, 107--108.
 
15
Farmer, D. and Venema, W. 2000. Forensic computer analysis: an introduction. Dr. Dobb's J. 25, 9 (Sept.), 70, 72--75.
 
16
 
17
Garfinkel, T. and Rosenblum, M. 2003. A virtual machine introspection based architecture for intrusion detection. In Proceedings of the 2003 Network and Distributed System Security Symposium (NDSS).
 
18
Goel, A., Shea, M., Ahuja, S., and Chang Feng, W. 2003. Forensix: A robust, high-performance reconstruction system. In Proceedings of the 2003 Symposium on Operating Systems Principles (poster session).
 
19
Goldberg, I., Wagner, D., Thomas, R., and Brewer, E. A. 1996. A secure environment for untrusted helper applications. In Proceedings of the 1996 USENIX Security Symposium. 1--13.
 
20
Huagang, X. 2000. Build a secure system with LIDS. Available online at http://www.lids.org/document/build_lids-0.2.html.
21
 
22
King, S. T., Dunlap, G. W., and Chen, P. M. 2003. Operating system support for virtual machines. In Proceedings of the 2003 USENIX Technical Conference. 71--84.
 
23
24
25
 
26
The Honeynet Project. 2001. Know Your Enemy: Revealing the Security Tools, Tactics, and Motives of the Blackhat Community. Addison Wesley, Reading, MA.
 
27
Tip, F. 1995. A survey of program slicing techniques. J. Programm. Lang. 3, 3.
 
28
Tyson, W. M. 2001. DERBI: Diagnosis, explanation and recovery from computer break-ins. Tech. rep. DARPA Project F30602-96-C-0295 Final Report. SRI International, Menlo Task, CA. Artificial Intelligence Center. Available online at http://www.dougmoran.com/dmoran/publications.html.
 
29
 
30
Zhu, N. and Chiueh, T. 2003. Design, implementation, and evaluation of repairable file service. In Proceedings of the 2003 International Conference on Dependable Systems and Networks (DSN). 217--226.

CITED BY  10


REVIEW

"Stefano Zanero : Reviewer"

BackTracker, a tool developed to help system administrators track intrusions, is described in this paper. The tool creates a graph of the interactions between system objects, helping in the forensic analysis of a compromised machine. The tool has   more...

Collaborative Colleagues:
Samuel T. King: colleagues
Peter M. Chen: colleagues