Syllabus

Course Info

Course Number: CSE 365 (70710)
Instructor: Prof. Adam Doupé
Email: doupe@asu.edu
Office: BYENG 472
Office Hours: Wednesdays, 11:30am–12:30pm, and by appointment
Meeting Times: Tuesday and Thursday, 12:00pm–1:15pm (COOR L1-74)
Course Mailing List: Piazza

Course TA: Faris Bugra Kokulu
Email: fkokulu@asu.edu
Office: BYENG 423
Office Hours: Mondays 10:00am–11:00am, Friday 3:00pm–4:00pm, and by appointment

Course Description

This course will provide students with a basic and comprehensive understanding of the problems of information assurance (IA) and the solutions to these problems, especially the security of information on computers and networks. This course will focus on the IA technology as well as IA policy, management, legal, and ethical aspects¹.

Prerequisites

Computer Information Systems BS major, Computer Systems Engineering BSE major, Computer Science BS major, or Industrial Engineering BSE major; CIS 235, CSE 220, or CSE 240 with C or better.

Recommended Textbook

All material for the course will be provided in lecture, however we will use an excellent textbook to supplement lecture.

Introduction to Computer Security.
Matt Bishop
ISBN: 0321247442

Course Communication

All announcements and communications for the class will take place through the class piazza.

Student may use the class piazza to ask questions or clarifications, and the TA, Instructor, or other students can answer. Note that the advice in “How to Ask Questions the Smart Way” will increase the chances of getting your question answered. While I highly encourage students to help each other on the mailing list, please do not go overboard and send your fellow student code (this will be considered cheating). It is better to point out their mistake or direct them to a resource that can help solve their problem, rather than giving them the answer. Note that sharing solutions or answers is expressly prohibited and will result in academic sanctions.

Questions meant for the professor and/or TA should be addressed as a private post on the class piazza.

Note that if you email us directly, and we deem it necessary and helpful, we will clas Piazza the class mailing list when replying to direct emails.

Course Topics

• Security Objectives
• Security Mechanisms
• Security Attacks and Threats
• Access Control
• Cryptography
• Authentication
• Network Security
• Web Security
• System Security
• IA Policy and Management
• Risk Assessment and Risk Management
• Assurance
• Privacy and Anonymity
• Legal and Ethical Issues

Assessment

Students will be evaluated on their performance on homework and exams.

Homework Assignments

There will be three–six homework assignments in the course, covering the material presented in the lectures.

Midterm Exam

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.

Final Exam

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.

Grading

The preliminary thresholds for assigning a letter grade are the following:

I reserve the right to curve the grades (by lowering the thresholds), depending on the circumstances.

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.

If an exam date conflicts with a religious holiday (in accordance with ACD 304-04) or other university sanctioned activities (in accordance with ACD 304-02) you should let me know at least two weeks before the exam date to schedule a makeup exam.

Special Accommodations

Students requesting disability accommodations should register with the Disability Resource Center (DRC) and present the instructor with appropriate documentation from the DRC.

Plagiarism and Cheating

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. The 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 assignment code 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.

Syllabus Update

Information in the syllabus, may be subject to change with reasonable advance notice.