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

Course Location and Time

• Lecture: MWF 10:30-11:20am, CSE2 G20
• Sections:
• Section AD: Th 12:30-1:20pm, CSE2 G10
• Section AA: Th 1:30-2:20pm, CSE2 G10
• Section AB: Th 2:30-3:20pm, SAV 166
• Section AC: Th 3:30-4:20pm, SAV 166

Course Staff

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

Teaching Assistants:

• Shikang Gao, TA - gaos23@cs
• Christine Geeng, TA - cgeeng@cs
• Robby Marver, TA - ram16@uw
• Ming-Jing Tsay, TA - mtsay@uw
• Yang Wang, TA - yangw97@uw
• Kyle Yan, TA - kyleyan@uw
• Eric Zeng, TA - ericzeng@cs
• Jeff Zhao, TA - zhaox27@uw

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

Discussion Board

Google Group

Office Hours

• Franzi: Thursdays 9:00a - 10:00a, CSE2 (Gates Center) 314
  • Exception: Thursday, April 25: 11:00a - 12:00p instead
  • Exception: Thursday, May 9: 9:30a - 10:30a instead
  • Exception: Thursday, June 6: No office hours; on Wednesday, June 5 @ 9am instead


• TA Office Hours:
• Robby and Yang: Mondays 1:30p - 2:30p, CSE2 152
• Christine and Chris: Tuesdays 9:30a - 10:30a, CSE2 152
• Eric and Jinny: Wednesdays 11:30a - 12:30p, CSE2 150
• Jeff and Kyle: Fridays 3:30p - 4:30p, CSE2 131

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!