This course teaches applications of tools and techniques used in the state-of-the-art computer systems security research projects. In particular, each lecture will be two-folded; one is reading & discussion session for academic papers, and the other is in-class lab sessions with project assignments.
Throughout ten-weeks of lectures and hands-on labs, the course will guide students on how to apply techniques in research papers to practice.
- Computer Architecture and Assembly Language (CS 271 at OSU)
- Linux System Administration (CS 312 at OSU)
- Operating Systems (CS 344 / CS 444 at OSU)
- Programming Languages / Compilers (CS 381 / CS 480 at OSU)
- Computer Networks (CS 372 / CS 476 at OSU)
- Software Engineering (CS 361 / CS 362 at OSU)
- Database Systems (CS 340 / CS 440 at OSU)
- When: Tu&Th 16:00-17:50 (4:00pm-5:50pm, 50 min lecture and 60 min in-class lab)
- Where: Owen 106
Office hours and recitation¶
We will have office hours from 17:00-18:30 at KEC 3079 on Wed, every week (this could be changed at the instructor’s discretion).
Who should take CS 419/579?¶
This course mainly targets graduate students and undergraduate students who would like to conduct academic research in computer systems security.
Students who have started academic research in systems security and who would like to do graduate research in the future are all welcomed, but please be prepared for the commitment that a student should put into this course: we will have one programming assignments (requires you to work 4+ hours) per each lecture.
- 100% Programming Assignments
- No midterm or final exams
CS 419/579 provides a 7 day grace period (50% points after due date) and we strictly follow the plagiarism policy (read OSU’s Student Conduct CODE).
Cheating vs. collaboration
Collaboration is a very good thing. On the other hand, cheating is considered a very serious offense and is vigorously prosecuted. Vigorous prosecution requires that you be advised of the cheating policy of the course before the offending act.
- For this semester, the policy is simple: don’t cheat:
- Never share code or text on the project.
- Never use someone else’s code or text in your solutions.
- Never consult project code or text that might be on the Internet.
- On the other hand, for this class, you are strongly encouraged to:
- Share ideas.
- Explain your code to someone to see if they know why it doesn’t work.
- Help someone else debug if they’ve run into a wall.
If you obtain help of any kind, always write the name(s) of your sources.