Dartmouth College Computer Science
Technical Report series
TR search TR listserv
|By author:||A B C D E F G H I J K L M N O P Q R S T U V W X Y Z|
|By number:||2017, 2016, 2015, 2014, 2013, 2012, 2011, 2010, 2009, 2008, 2007, 2006, 2005, 2004, 2003, 2002, 2001, 2000, 1999, 1998, 1997, 1996, 1995, 1994, 1993, 1992, 1991, 1990, 1989, 1988, 1987, 1986|
Kernel rootkits are a special category of malware that are deployed directly in the
kernel and hence have unmitigated reign over the functionalities of the kernel itself.
We seek to detect such rootkits that are deployed in the real world by first observing
how the majority of kernel rootkits operate. To this end, comparable to how rootkits
function in the real world, we write our own kernel rootkit that manipulates the network
driver, thus giving us control over all packets sent into the network.
We then implement a mechanism to thwart the attacks of such rootkits by noticing
that a large number of the rootkits deployed today rely heavily on the redirection of
function pointers within the kernel. By overwriting the desired function pointer to its
own function, a rootkit can perform a proverbial man-in-the-middle attack.
Our goal is not just the detection of kernel rootkits, but also to levy as little an
impact on system performance as possible. Hence our technique is to leverage existing
kernel functionalities (in the case of Linux) such as kprobes to identify potential attack
scenarios from within the sytem rather than from outside it (such as a VMM). We hope
to introduce real-world security in devices where performance and resource constraints
are tantamount to security considerations.
M.S. Thesis Proposal. Advisor: Sean W. Smith
Bibliographic citation for this report: [plain text] [BIB] [BibTeX] [Refer]
Or copy and paste:
Ashwin Ramaswamy, "Detecting kernel rootkits." Dartmouth Computer Science Technical Report TR2008-627, September 2008.
Notify me about new tech reports.
Search the technical reports.
To receive paper copy of a report, by mail, send your address and the TR number to reports AT cs.dartmouth.edu
Copyright notice: The documents contained in this server are included by the contributing authors as a means to ensure timely dissemination of scholarly and technical work on a non-commercial basis. Copyright and all rights therein are maintained by the authors or by other copyright holders, notwithstanding that they have offered their works here electronically. It is understood that all persons copying this information will adhere to the terms and constraints invoked by each author's copyright. These works may not be reposted without the explicit permission of the copyright holder.
Technical reports collection maintained by David Kotz.