Spring 2022 CS 458/658 (Computer Security and Privacy) Syllabus

Instructors Ian Goldberg Diogo Barradas
Office Hours
(online)
Mondays 3:30–4:30 pm
or by appointment
Thursdays 2:00–3:00 pm
or by appointment
Email iang@uwaterloo.ca diogo.barradas@uwaterloo.ca
Lectures Section 1: Mon,Wed 10:00–11:20 am, MC 2034
Section 2: Mon,Wed 1:00–2:20 pm, MC 1056
LEARN Course site on LEARN
Piazza Course page on Piazza

This syllabus is a guideline for the course and not a contract. As such, its terms may be altered when doing so is, in the opinion of the instructor(s), in the best interests of the class.

Special note for Spring 2022

Because we cannot predict what COVID will do and how the university will react, we are committing to making the course definitely available remotely the whole term no matter what. You will not be required to be in any particular place for this course; there will be no in-person exams, and lecture content will be both livestreamed and recorded so as to not encourage anyone to come to class while potentially sick.

If we're in a place where courses are offered remotely again, then that will be the only delivery mechanism; otherwise, we'll be livestreaming the course in Bongo from the classroom, so if you really really want to watch the instructors sit in front of a computer streaming the lecture, you are technically allowed to do so. We expect most students will participate online, and we encourage you to participate synchronously (joining the Bongo room live, as opposed to watching the recordings later).

Office hours will also be held online.

Overview

This course provides an introduction to security and privacy issues in various aspects of computing, including programs, operating systems, networks, databases, and Internet applications. It examines causes of security and privacy breaches, and gives methods to help prevent them.

Students completing this course should be better able to produce programs that can defend against active attacks, and not just against random bugs.

Intended audience

Third or fourth year CS students (CS 458), or first year CS graduate students (CS 658)

Prerequisites

CS 350 (Operating Systems). Familiarity with C.

Outline

Introduction to Computer Security and Privacy
The meaning of computer security; comparing security with privacy; types of threats and attacks; methods of defense
Program Security
Secure programs; nonmalicious program errors; malicious code; controls against program threats
Operating System Security
Methods of protection; access control; user authentication
Network Security
Network threats; firewalls, intrusion detection systems
Internet Application Security and Privacy
Basics of cryptography; security and privacy for Internet applications (email, instant messaging, web browsing); privacy-enhancing technologies
Database Security and Privacy
Security and privacy requirements; reliability, integrity, and privacy; inference; data mining; k-anonymity
Non-technical Aspects
Administration of security systems; policies; physical security; economics of security; legal and ethical issues

Grading Scheme

Grades will be calculated as follows for undergraduate students:

For graduate students, 80% of your grade will be computed through the above distribution. The research survey paper will account for the remaining 20% of your overall mark, as discussed below. Please consult LEARN for the assessment deadlines.

Assignments: The three assignments contain both written and programming exercises and cover the new material in the course since the previous assignment.

Please start working on the assignments in advance of the deadlines. To motivate you to do so, we may require you to submit milestones for some or all of them.

Late submissions for Assignments 1, 2, or 3 will be accepted only up to 48 hours after the original due date. There is no penalty for accepted late submissions. Assignments can be submitted multiple times, and the last one will be used for marking. Course personnel will not normally give assistance for assignments after their original due dates.

The 48 hours grace period does not apply to the due dates for the self-tests, blog task (sign-up, publishing, comments), the final assessment, or the CS 658 proposal and research survey paper; no lates will be accepted for them.

You must notify your instructor(s) well before the due date of any severe, long-lasting problems that prevent you from completing an assignment on time.

Assignments 1, 2, and 3 are due at 3:00 pm Eastern Time on their respective due dates. These assignments are to be submitted electronically with the "submit" command, see the 'Course Mechanics' section below. Assignments submitted by other means will not be accepted. Assignment 1, 2, and 3 comments and marks will be returned using infodist. Again, see the 'course mechanics' section below.

The final assessment will be available from 8 am on Aug 2, until 5 pm on Aug 3, on Crowdmark. You must submit your responses within 2.5 hours of accessing the assessment, but not later than 5 pm on Aug 3. The final assessment is written-only (no programming) but covers material from the whole term. There will be no assistance from course staff for the final assessment. If your score in the final assessment is below 50%, you cannot pass the course.

Self-tests: Self-tests are meant to help you keep up with the material, that is, to assess and improve your understanding of basic concepts. You can attempt each self-test as often as you like during its availability period; your last grade on each self-test will be the one recorded (although course personnel can see every attempt). The availability and deadline information will be posted on LEARN. Late self-tests cannot be made up for any reason, including students signing up for the class late. (Students who join the class on or after the due date of the first self-test will instead be excused from that particular self-test.) Again, the 48 hours grace period does not apply to the due dates for the self-tests.

Blog task: The blog task is intended to acquaint students with the latest developments in computer security and privacy. You will need to sign up on infodist (see 'Course mechanics' below) for a week to publish your blog post, by the blog task scheduling deadline (see LEARN). Late blog post submissions will not be awarded any marks. Please go through the link above for the blog task description and grading rubric.

Research Survey Paper (CS 658)

Students registered in CS 658 must write a research survey paper on a topic related to computer security or privacy. You should read Keshav's How to Read a Paper to efficiently read a paper and conduct a literature survey. In writing your paper, you must become familiar with the research literature relevant to your topic. Your focus should be on academic venues, such as the USENIX Security Symposium , ACM CCS, IEEE Symposium on Security and Privacy, Privacy Enhancing Technologies Symposium (PETS) or the NDSS Symposium. You should email your topic, proposal, and paper to the instructors.

Reappraisal Policy

If you have an assignment that you would like to have reappraised, please follow the instructions given on Piazza to submit your request. Include a clear justification for your claims. The appeals deadline is one week after the respective graded item is first made available. Note that for the final assessment, the entire assessment will be remarked, and the assigned grade may go up or down as a result. If your appeal is concerned with a simple calculation error, please see the TA(s) during their office hours.

Textbooks

Additional readings will be assigned, and will appear on the course website; readings marked as mandatory contain required material for the course. You must read these mandatory readings; those marked before class must be read before the date of the corresponding lecture.

Communication

It is your responsibility to keep up with all course-related information posted to LEARN, the course Piazza site, and the course website.

Piazza: Please direct all communication to the discussion forums in Piazza. This includes questions on materials in lectures, assignments, and general logistics.

Etiquette:

Email: Important course information will generally be posted to LEARN, but may also be sent to your uwaterloo.ca email address. For personal matters, such as an illness, please email the instructors directly. We will only reply back to email from your uwaterloo.ca email address, for privacy rules.

Course mechanics:

Teaching Assistants

Other Resources

Security Information

In this course, you will be exposed to information about security problems and vulnerabilities with computing systems and networks. To be clear, you are not to use this or any other similar information to test the security of, break into, compromise, or otherwise attack, any system or network without the express consent of the owner. In particular, you will comply with all applicable laws and UW policies, including, but not limited to, the following:

Violations will be treated severely, and with zero tolerance.

Academic Integrity

Students are encouraged to talk to one another, to the TAs, to the instructor(s), or to anyone else about any of the assignments. Any assistance, though, must be limited to discussion of the problem and sketching general approaches to a solution. Each student must write his or her own solutions, including code and documentation if appropriate, for the assignments. Consulting another student's solution is prohibited, and submitted solutions may not be copied from any source. In particular, submitting assignments copied in whole or in part from assignment submissions to a previous offering of this course, or from any offering of any other course, is forbidden, even if a student is resubmitting his or her own work. These and any other forms of collaboration on assignments constitute cheating. If you have any questions about whether some activity constitutes cheating, please ask the instructor(s).

Avoiding Academic Offenses: Most students are unaware of the line between acceptable and unacceptable academic behaviour, especially when discussing assignments with classmates and using the work of other students. For information on commonly misunderstood academic offenses and how to avoid them, students should refer to the Faculty of Mathematics Academic Integrity site.

The general University policy:

Diversity

It is our intent that students from all diverse backgrounds and perspectives be well served by this course, and that students’ learning needs be addressed both in and out of class. We recognize the immense value of the diversity in identities, perspectives, and contributions that students bring, and the benefit it has on our educational environment. Your suggestions are encouraged and appreciated. Please let us know ways to improve the effectiveness of the course for you personally or for other students or student groups. In particular:

Note for Students with Disabilities

AccessAbility Services, located in Needles Hall North, Room 1401, collaborates with all academic departments to arrange appropriate accommodations for students with disabilities without compromising the academic integrity of the curriculum. If you require academic accommodations to lessen the impact of your disability, please register with AccessAbility at the beginning of each academic term.

Mental Health Support

The Faculty of Math encourages students to seek out mental health support if needed.

On-campus Resources:

Off-campus Resources:

COVID-19 Information and Resources

Online classes during the COVID-19 pandemic has been taxing and stressful for all of us. Here are some useful resources and guidance from the university.

Territorial Acknowledgement

We acknowledge that we live and work on the traditional territory of the Attawandaron (Neutral), Anishinaabeg, and Haudenosaunee peoples. The University of Waterloo is situated on the Haldimand Tract, the land promised to the Six Nations that includes ten kilometres on each side of the Grand River.