Overview | Schedule | Readings | Attack Presentations | Course Project
|Professor:||J. Alex Halderman|
|Credits:||4. This course counts towards meeting software quals requirements.|
|Prereqs:||EECS 482 or EECS 489 or grad standing. Understanding projects and papers will require some operating systems and networking background.|
|Lectures:||TuTh 1:30-3:30, 1690 CSE|
|Office Hours:||TuTh 3:30-4:30, 4717 CSE, or by appointment|
|GSI:||Eric Wustrow (4828 CSE, meetings by appointment)|
|Forum:||Available on CTools|
|Free Lunch:||Security Reading Group|
This course covers foundational work and current topics in computer systems security. We will read research papers and discuss attacks and defenses against operating systems, client-side software, web applications, and IP networks. Students will be prepared for research in computer security and for security-related research in other subfields, and they will gain hands-on experience designing and evaluating secure systems.
There will be many opportunities to tailor the course to your backgrounds and interests. The tentative list of topics below should give you an idea of what to expect. Email me if you have questions or suggestions.
The security mindset, thinking like an attacker, reasoning about risk, research ethics
Symmetric ciphers, hash functions, message authentication codes, pseudorandom generators
Key exchange, public-key cryptography, key management, the SSL protocol
Exploitable bugs: buffer overflows and other common vulnerabilities – attacks and defenses
Malware: viruses, spyware, rootkits – operation and detection
Automated security testing and tools for writing secure code
Virtualization, sandboxing, and OS-level defenses
The browser security model
Web site attacks and defenses: cross-site scripting, SQL injection, cross-site reference forgery
Internet crime: spam, phishing, botnets – technical and nontechnical responses
Network protocols security: TCP and DNS – attacks and defenses
Policing packets: Firewalls, VPNs, intrusion detection
Denial of service attacks and defenses
Wireless and mobile device security
Data privacy, anonymity, censorship, surveillance
Hardware security – attacks and defenses
Trusted computing and digital rights management
Electronic voting – vulnerabilities, cryptographic voting protocols
Physical security – locks and safes
Class Participation (5%) — I will assign one or two research papers as required reading for each class. Come prepared to discuss them.
Paper Responses (15%) — Unless otherwise noted on the reading list, you are required to write a short reaction to each paper. I will be looking for evidence that you read the paper and thought carefully about the topic. Responses are due at the start of each class.
Attack Presentation (30%) — Working with a partner, you will choose an attack from a provided list and implement a demonstration exploit. You will give a 20 minute presentation were you (1) describe the attack, (2) talk about how you implemented it and give a demo, and (3) discuss possible defenses. Presentations will take place throughout the semester, as indicated on the course schedule.
Group Project (50%) — There will be an extended group project over the course of the semester. It may be done in a group appropriate to the size of your project. Generally, the projects will involve analyzing the security of a system or implementing a new defense mechanism.
To defend a system you need to be able to think like an attacker, and that includes understanding techniques that can be used to compromise security. However, using those techniques in the real world may violate the law and the university's computing practices, or may be unethical. You must respect the privacy and property rights of others at all times, or else you will fail the course. Under some circumstances, even probing for weaknesses may result in severe penalties, up to and including civil fines, expulsion, and jail time.
Carefully read the Computer Fraud and Abuse Act (CFAA), a federal statute that broadly criminalizes computer intrusions. This is just one of several laws that govern hacking. Understand what the law prohibits — you don't want to end up like this guy. The EFF provides helpful advice on vulnerability reporting and other legal matters. If in doubt, I can refer you to an attorney.
Please review CAEN's policy document on rights and responsibilities for guidelines concerning use of technology resources at U-M, as well as the Engineering Honor Code. As members of the university, you are required to adhere to these policies.