| Meeting Times |
Thursdays & Fridays, 1 - 2:15 pm, Wyman Park Conference rm.
| Description |
This course focuses on selected topics in Computer and Network Forensics. Particular attention is given to new techniques for recovering information from anonymized sources, file system recovery techniques, malware propagation analysis, secure remote logging, traffic classification, among others. We also examine virtualization techniques for process isolation, kernel-level rootkit detection (and subversion), network traceback and its limitations. The course is structured as a research seminar where students present research papers to their peers.
Prerequisites of 600.424 (or equivalent) and Operationg Systems are strongly advised. In addition, familiarity with basic cryptographic primitives will be necessary to understand the details of some of the assigned papers. Familarity with C is highly recommended.
| Course Project |
Your course project will entail submitting (to me) a workshop quality research paper outlining novel ideas. This project can involve application of concepts learned from other research papers, but MUST depict original ideas. As this is an "Applications" course, the project can entain a critical comparison of techniques (some of which may be off-the-shelve) but the analysis taken must be original. There will be some checkpoints throughout the semester and will include a survey paper on work related to your topic. The course project constitutes 50% of your final grade. Although I will provide a few suggestions on projects, students are encouraged to come up with ideas on their own. Students are also strongly encouraged to use LaTeX when preparing many material of this course, including critiques of assigned papers.
| Readings and Presentations |
Students are required to read all papers assigned during the semester and be able to competently discuss the material in class. Each student will be responsible for presenting one lecture (depending on the class size) -- that lecture will be based on the assigned paper for the week including as much relevant related work as necessary to distill the work presented in the paper. The speaker should try to present a comprehensive view of the topic suitable for a 1 hour talk. Additionally, each student is responsible for submitting a summary of the paper, which includes (1) contributions, strengths and weaknesses, (2) at least two thought-provoking questions on the assigned paper (3) two possible directions for extensions on the ideas / topic presented in the paper. Your questions should critically evaluate the paper (eg, questioning the assumptions, questioning whether the experiments are lacking (and why), flaws in the analysis, etc). Examples will be provided. This summary will be turned in to the moderator (and me) on the Thursday session.
The moderator is responsible for recapping the ideas for the previous day (15 mins max) and presenting any supplimentary material not covered by the presenter. The moderator will lead the general discussions on Friday. Notes on the week's discussion must also be compiled by the moderator, and submitted to me no later than 1 week after the lecture. These notes will be made publicly available (via the website) to rest of the class.
| Office Hours |
Tuesday 1 - 3 pm or by appointment.
| Mailing List |
send email to majordomo (at) cs dot jhu dot edu with subscribe cs624 in the message body (its okay that you subscribe to 624, even if this is 625).
| Grading |
This is intended to be an interactive class, and as such, class participation will play a significant role in my grading criteria. Students will be graded on the presentation of their assigned papers, their participation in discussions and questions, and their course project. Weights are as follows:
| Deliverable | Grade |
| Presentations | 30% |
| Project | 50% |
| Class participation | 20% |
| Date |
Topic | Presenter (Thursday) |
Moderator  (Friday) |
Jan. 25th |
Course Introduction, selection of presenters, project discussion.
|
||
Feb 1,2 |
Speculative Execution in a Distributed File System
E. Nightingale, P. Chen, Jason Flinn related readings:
|
Jay
|
Fabian
|
Feb 8,9 |
File System Design with Assured Delete
R. Perlman
Z. Peterson et al. related readings:
|
Kevin |
Fabian
|
Feb. 15,16 |
ReVirt: Enabling Intrusion Analysis through Virtual-Machine Logging and Replay
G. Dunlap, S. King, S. Cinar, A. Basrai, and P. Chen related readings:
|
Kristine
|
Fabian
|
Feb 22,23 |
An Architecture for Specification-Based Detection of Semantic Integrity Violations in Kernel Dynamic Data
N. Petroni, T. Fraser, A. Walters, W. Arbaugh related readings:
|
Chuck |
Fabian
|
March 1/2 |
NO CLASS (I'm away at a conference)
|
||
March 8,9 |
Dan
|
Fabian
| |
March 15,16 |
SPRING BREAK
|
||
March 22,23 |
Ryan |
|
|
March 29,30 |
Prefix-preserving IP address anonymization: measurement-based security analysis and a new cryptography-based scheme
J. Fan, J. Xu, Mostafa. H, S. Moon. related readings:
|
Scott |
Charles
|
April 5,6 |
Cryptographic Support for Secure Logs on Untrusted Machines
B. Schneier and J. Kelsey. related readings:
|
Jay |
Kevin Survey paper due |
April 12,13 |
Kristine
|
Fabian |
|
April 19,20 |
Pioneer: Verifying Integrity and Guaranteeing Execution of code on Legacy Platforms
A. Seshadri et al.
Protecting software codes by guards
H. Chang and J. Atallah related readings:
|
Chuck |
Fabian |
April 26,27 |
|
|
|
| May 3,4th | In-class Presentations | ||
| May 4th | Final Projects due by 10pm. NO EXCEPTIONS |