Course Number: CSE 545 (21469)
Instructor: Prof. Adam Doupé
Office: BYENG 472
Office Hours: Wednesday 10am–11am
Meeting Times: Monday and Wednesday, 4:35pm–5:50pm (PSH 152)
Course Mailing List: email@example.com
Course TA: Connor Nelson
Office: BYENG 423
Office Hours: Tuesday 2pm–3pm, Thursday 10:30am–11:30am
Course TA: Adam Oest
Office: BYENG 423
Office Hours: Monday 3pm–4pm, Friday 12pm–1pm
Professor/TA Communication: firstname.lastname@example.org
This course will provide students with a good understanding of the theories and tools used for secure software design, threat analysis, secure coding, and vulnerability analysis. Students will study, in-depth, vulnerability classes to understand how to protect software and how to secure software.
We will also cover various analysis and design techniques for improving software security, as well as how to use these techniques and tools to improve and verify software designs and security. Finally, we will also discuss the technical trends affecting software security1.
This course will be very challenging, and students are expected to learn the necessary technologies on their own time.
This course requires very good programming/development skills (C/C++ and a scripting language, such as Python, Ruby, or PHP), a solid background in operating systems (especially Linux or UNIX variants), and knowledge of networking (IP, TCP, and socket programming). If you do not have these skills, or do not plan on acquiring them, then I suggest you do not take this class.
All material for the course will be provided in lecture, however here are some books that can help reinforce the concepts discussed in class.
Hacking: The Art of Exploitation.
The Web Application Hacker’s Handbook: Finding and Exploiting Security Flaws. Dafydd Stuttard and Marcus Pinto ISBN: 1118026470
All announcements and communications for the class will take place
through the class mailing list. Students are required to subscribe to
the class mailing list:
Student may use the class mailing list to ask questions or clarifications, and the TA, Instructor, or other students can answer. Note that sharing solutions or answers is expressly prohibited.
Questions meant for the professor and/or TA should be addressed to the following email address: email@example.com. This email address is sent to the professor and TAs, and this will ensure that your email is addressed in a timely manner (faster than just sending an email to one of our addresses).
Topics may include:
- Current state of software security
- Common software vulnerabilities
- Secure software design and coding
- Software assurance
- Software security standards and tools
- Secure software engineering lifecycle
- Risk management in software development
- Software security testing
- x86 Assembly
- Scripting languages
Students will be evaluated on their performance on homework, exams, and project.
There will be anywhere from three to five homework assignments in the course, covering the material presented in the lectures. Expect significant programming assignments, and assignments that test exploiting hands-on security vulnerabilities.
There will be a midterm exam. The exam will cover the material discussed from the lectures and the assignments. No notes or outside material/devices will be allowed.
There will be a project for the course. The project will entail creating a security library that defends against a common vulnerability class. Students will be able to choose from a list of projects.
There will be a final exam that will cover all material presented throughout the course, with an emphasis on material from the second half of the class. No notes or outside material/devices will be allowed.
Homework Due Dates and Exam Dates
Homework due dates and exam dates will be posted well in advance on the class website and announced in class.
For each day an assignment is late, a 20% deduction will be assessed. Exams will be given in class and are closed book, closed note, unless otherwise stated. Makeup exams are typically not given unless under extenuating circumstances. Laptops, phones, calculators, and other smart devices are not allowed during exams.
Plagiarism or any form of cheating in assignments, projects, or exams is subject to serious academic penalty. To understand your responsibilities as a student read: ASU Student Code of Conduct and ASU Student Academic Integrity Policy.
You are allowed to use code snippets that you find online (StackOverflow or otherwise) provided that you provide, as part of a comment in your source code, the source of the code. This snippets should not constitute a significant part of your code. Using another students’ code, past or present, even with a citation is a violation of the academic integrity policy.
There is a zero tolerance policy in this class: any violation of the academic integrity policy will result in a zero on the assignment and the violation will be reported to the Dean’s office. Plagiarism is taken very seriously in this course. To date, the professor has issued 27 academic integrity policy violations.
Examples of academic integrity violations include (but are not limited to):
Sharing code with a fellow student (even if it’s only a few lines).
Collaborating on code with a fellow student.
Submitting another students code as your own.
Submitting a prior student’s code as your own.
Posting your projects online is expressly forbidden, and will be considered a violation of the academic integrity policy. Note that this includes working out of a public Github repo. The Github Student Developer Pack provides unlimited private repositories while you are a student. If you want to impress employers with your coding abilities, create an open-source project that is done outside of class.
Information in the syllabus, may be subject to change with reasonable advance notice.
© Copyright 2018 Adam Doupé as to this syllabus, all lectures, and course-related written materials. During this course students are prohibited from making audio, video, digital, or other recordings during class, or selling notes to or being paid for taking notes by any person or commercial firm without the express written permission of the faculty member teaching this course.↩