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

Course Location and Time

• Lecture: MWF 10:30-11:20am PT, in SMI 120 and on Zoom
• Sections:
• Section AA: Th 12:30-1:20pm, ECE 037 and on Zoom
• Section AB: Th 1:30-2:20pm, CSE2 G10 and on Zoom
• Section AC: Th 2:30-3:20pm, MOR 221 and on Zoom
• Section AD: Th 3:30-4:20pm, SMI 307 and on Zoom

Course Staff

Instructor: Tadayoshi (Yoshi) Kohno - yoshi@cs

Teaching Assistants:

• Jeter Arellano, TA - jeter@cs
• David Chen, TA - hanfec@cs
• Theo Gregersen, TA - theoag@cs
• Wenqing Lan, TA - lanw3@cs
• Harmony Peng, TA - yuepeng@cs
• Lucy Simko, TA - simkol@cs
• Edan Sneh, TA - esneh@cs
• Jeffery Tian, TA - jefftian@cs
• Miranda Wei, TA - weimf@cs
• Bowen Xu, TA - bwx074@cs

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

Discussion Board

TBD

Office Hours

• Yoshi:
  Thursday, 9-9:50am, Zoom (see Canvas for link) (none on March 3)


• TA Office Hours:
• Monday, 2-3pm, Zoom for Week 2
• Tuesday, 5-6pm, Zoom for Week 2
• Wednesday, 4-5pm, Zoom for Week 2
• Thursday, 5-6pm, Zoom for Week 2
• Friday, 5-6pm, Zoom for Week 2

No Textbook

In previous quarters we've used "Foundations of Security: What Every Programmer Needs to Know", Daswani, Kern, and Kesavan, ISBN 1-59059-784-2. Although it is still a good source for learning many key aspects of security, it was published a long time ago. It is not a required text.

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!