CSE 484 / CSE M 584: Computer Security (Spring 2020)

Course Location and Time

• Lecture: MWF 10:30-11:20am, via Zoom (access via the Zoom tab on the course Canvas page)
• Sections:
• Section AD: Th 12:30-1:20pm, via Zoom
• Section AA: Th 1:30-2:20pm, via Zoom
• Section AB: Th 2:30-3:20pm, via Zoom
• Section AC: Th 3:30-4:20pm, via Zoom

Course Staff

Instructor: Prof. Franziska (Franzi) Roesner (franzi@cs)

Teaching Assistants:

• Zetian Chen, TA - zetiac@cs
• Wenqing Lan, TA - lanw3@cs
• Patricia Popp, TA - ppopp20@cs
• Yue (Alex) Teng, TA - tengyued@cs
• Erika Wolfe, TA - eywolfe@cs
• Samuel Wolfson, TA - wolfson@cs
• Bowen Xu, TA - bwx074@cs
• Xinghan (Jeff) Zhao, TA - zhaox27@cs

Email everyone (preferred method to reach staff): cse484-tas@cs.washington.edu

Discussion Board

Ed Discussion Board

Office Hours

• Franzi: Mondays, 11:30am-12:30pm, via Zoom
  (Exception: No office hours on May 25, Memorial Day)


• TA Office Hours:
• Bowen, Erika, Patty: Tuesdays, 11:30am-12:30pm, via Zoom
• Alex, Jeff, Wenqing: Wednesdays, 3:30-4:30pm, via Zoom
• Alex, Erika, Sam: Fridays, 12:30-1:30pm, via Zoom
• Jeff, Sam, Zetian: Fridays, 1:30-2:30pm, via Zoom



Optional Textbook

Foundations of Security: What Every Programmer Needs to Know, Daswani, Kern, and Kesavan, ISBN 1-59059-784-2

You can find it online through the UW Libraries here.




Topics

In this course, we will cover topics including: the "security mindset", threat modeling, software security, cryptography, malware, web security, web privacy, smartphone security, authentication, usable security, anonymity, physical security, and security for emerging technologies.

For more details, see the course schedule.




Prerequisites

CSE 332 and CSE 351

You should have maturity in both the mathematics of computer science and in the engineering of computer systems. This means that you should: have a good understanding of data structures and algorithms; be comfortable writing programs from scratch in C and Java; be comfortable writing and debugging assembly code; and be comfortable in a command-line Unix development environment (gdb, gcc, etc). You should also have a good understanding of computer architecture, operating systems, and computer networks. Most importantly, you should be eager to challenge yourself and learn more!