This course covers advanced techniques for writing exploits and patching vulnerabilities, taught through an intense, hands-on security laboratory. A significant part of this course involves solving Capture-The-Flag (CTF) and discussing strategies for solving such problems. This course covers a variety of topics including (but not limited to) reverse engineering, exploitation, binary analysis, and web.
Operating systems or equivalent (e.g., CS 3210 at GT).
- When: Class opens at 8AM (please visit the Canvas for a detailed schedule)
- Where: Canvas module
Office hours and recitation¶
We have an optional recitation (and office hours) every week. Students can join the online recitation session through Bluejeans (see Bluejeans tab from Canvas).
- Mon 12-01PM
- Tue 09-10PM
- Wed 05-06PM
- Thu 05-06PM
- Fri 03-04PM
We will use Chrome Remote Desktop as the remote desktop tool throughout this semester. If you need debug help, please send a private post on piazza with the following information:
- Access code
- problem(s) description
TA team will hold a remote session during the office hour.
Who should take CS 6265-seclab?¶
CS-6265 is primarily intended for motivated seniors and graduate students who are interested in learning the skill sets necessary to participate in CTF competitions (e.g., DEFCON CTF).
- 100% Lab.
- If you didn’t turn in a single (full) lab, you will get an F.
- No midterm or final exams.
- 40%: A, 30-40%: B, 30-20%: C and below (in each group).
- Three groups: undergraduate, masters and PhD students
- See Game Rules.
Online discussion is strongly encouraged and it will help you a lot in solving lab problems. Please join Piazza and post your questions, ideas and thoughts.
CS6265 provides two weeks of a grace period (50% points after due date) and we strictly follow the cheating policy (read GT’s Academic Misconduct Policy).
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.
Don’t publish or post your work online (e.g., github). Any violation of these rules would result in F in your grade.