CSE 484 / CSE M 584: Computer Security (Autumn 2022)

Course Location and Time

• Lecture: MWF 10:30-11:20am, in CSE2 G20
• Sections:
• Section AD: Th 12:30-1:20pm, in JHN 111
• Section AA: Th 1:30-2:20pm, in MOR 220
• Section AB: Th 2:30-3:20pm, in SIG 224
• Section AC: Th 3:30-4:20pm, in SIG 224

Course Staff

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

Teaching Assistants:

• David Chen, TA - hanfec3@cs
• Theo Gregersen, TA - theoag@cs
• Aroosh Kumar, TA - arkumar@cs
• Wenqing Lan, TA - lanw3@cs
• Tim Mandzyuk, TA - timmandz@cs
• Noah Ponto, TA - ponton@cs
• Basia Radka, TA - basia@cs
• William Travis, TA - wibrotra@cs
• Julia Wang, TA - julialwa@cs

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

Discussion Board

Ed Discussion Board

Office Hours

• Franzi: Mondays 11:30-12:20am, CSE2 (Gates) 314


• TA Office Hours:
• Tuesdays 3:30-4:30pm, CSE (Allen) 218 - Aroosh and Basia
• Wednesdays 3:30-4:30pm, Zoom (see Canvas for link) - David, Tim, and Wenqing
• Thursdays 10:30-11:30am, CSE (Allen) 218 - Noah and William
• Fridays 2:00-3:00pm, CSE2 (Gates) 152 - Julia and Theo

No Textbook

We do not have a required textbook in this course. We will share links to recommended readings on the course schedule page. If you would like information about additional readings to supplement the course material, please ask the course staff!

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!