Topics will vary from year to year, but will focus mainly on network perimeter protection, host-level protection, authentication technologies, intellectual property protection, formal analysis techniques, intrusion detection and similarly advanced subjects. Emphasis in this course is on understanding how security issues impact real systems, while maintaining an appreciation for grounding the work in fundamental science. The course will consist of in-class workshops and interactive discussions. There will be programming assignments and a course project. Students will also be expected to read assigned papers and to present at least one research paper and lead a discussion on it.
MW 10:00 - 11:15 a.m.
Location: Wyman Park 4th floor conference room.
The course project assignment is available here.
David Brumley, Pongsin Poosankam, Dawn Song, and Jiang Zheng
Automatic Patch-Based Exploit Generation is Possible: Techniques and Implications.
Students: Neal Walfield
Chris Karlof, Umesh Shankar, J. D. Tygar and David Wagner
Dynamic pharming attacks and the locked same-origin policies for web browsers
Students: Paul Stanton
Karsten Nohl, David Evans, Starbug, and Henryk Plotz
Reverse-Engineering a Cryptographic RFID Tag
Students: Paul Frank
D. Halperin, T.S. Heydt-Benjamin, B. Ransford, S.S. Clark, B. Defend, W. Morgan, K. Fu, T. Kohno, and W.H. Maisel
Pacemakers and Implantable Cardiac Defibrillators: Software Radio Attacks and Zero-Power Defenses
Students: Hariram Balasundaram
Survey paper due
Paper presented
C. Reis, S. Gribble, T. Kohno, and N. Weaver
Detecting In-Flight Page Changes with Web Tripwires
Students: Neal Walfield
Paper presentations
J. Franklin, V. Paxson, A. Perrig, and S. Savage
An Inquiry into the Nature and Causes of the Wealth of Internet Miscreants
Students: Alliosn Mankin
David Dagon, Niels Provos, Chris Lee, and Wenke Lee
Corrupted DNS Resolution Paths: The Rise of a Malicious Resolution Authority
Students: Rajat Kheria
E-voting reports
California: Source code and red team reports.
Ohio: academic report
Students: Allison Mankin & Hariram Balasundaram
Project Status Report Due
Paper discussion
Patrick Traynor, Patrick McDaniel, and Tom La Porta
On Attack Causality in Internet-Connected Cellular Networks
Students: Paul Stanton
T. Ristenpart, G. Maganis, A. Krishnamurthy, and T. Kohno
Privacy-preserving Location Tracking of Lost or Stolen Devices: Cryptographic Techniques and Replacing Trusted Third Parties with DHTs
Students: Rajat Kheria & Paul Frank
Project presentations
Cheating is wrong. Cheating hurts our community by undermining academic integrity, creating mistrust, and fostering unfair competition. The university will punish cheaters with failure on an assignment, failure in a course, permanent transcript notation, suspension, and/or expulsion. Offenses may be reported to medical, law or other professional or graduate schools when a cheater applies.
Violations can include cheating on exams, plagiarism, reuse of assignments without permission, improper use of the Internet and electronic devices, unauthorized collaboration, alteration of graded assignments, forgery and falsification, lying, facilitating academic dishonesty, and unfair competition. Ignorance of these rules is not an excuse.
Academic honesty is required in all work you submit to be graded. Except where the instructor specifies group work, you must solve all homework and programming assignments without the help of others. For example, you must not look at anyone else’s solutions (including program code) to your homework problems. However, you may discuss assignment specifications (not solutions) with others to be sure you understand what is required by the assignment.
If your instructor permits using fragments of source code from outside sources, such as your textbook or on-line resources, you must properly cite the source. Not citing it constitutes plagiarism. Similarly, your group projects must list everyone who participated.
Falsifying program output or results is prohibited.
Your instructor is free to override parts of this policy for particular assignments. To protect yourself: (1) Ask the instructor if you are not sure what is permissible. (2) Seek help from the instructor, TA or CAs, as you are always encouraged to do, rather than from other students. (3) Cite any questionable sources of help you may have received.
On every exam, you will sign the following pledge: "I agree to complete this exam without unauthorized assistance from any person, materials or device. [Signed and dated]". Your course instructors will let you know where to find copies of old exams, if they are available.
For more information, see the guide on "Academic Ethics for Undergraduates" and the Ethics Board web site (http://ethics.jhu.edu).