General information

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

Course Staff

  • Instructor:David Kohlbrenner
  • TAs:
    • Alexandra Iurco
    • Antonio Ballesteros
    • Kelbin Luong
    • Pranav Gopalkrishnan
    • Rasmus Makiniemi
    • Runlin (Randy) He
    • Sonya Outhred
    • Trisha Bhatawdekar
    • Tiago Ugarte-wright
Email everyone (preferred method to reach staff): cse484-tas@cs.washington.edu

Course Location and Time

Lecture: MWF 10:30-11:20AM PT, in CSE2 G20. Recordings via Panopto.

Section

If you need to regularly attend a section that is not your assigned one, please contact David for permission. You are expected to attend section every week.


  • AD: 12:30-1:20 @ LOW 201
  • AA: 1:30-2:20 @ LOW 205
  • AB: 2:30-3:20 @ LOW 206
  • AC: 3:30-4:20 @ THO 135

Discussion Board

Ed Discussion Board
See the course syllabus for details on our Q+A board policies.

Office Hours

Office hours are currently TBD. Office hours run for one hour, and will stop sharply at the end time.

  • Monday
    • 1:30-2:30pm @ CSE2 150 (Randy + Pranav)
  • Tuesday
    • 1:00-2:00pm @ Allen 3rd floor break out (Antonio + Tiago)
  • Wednesday
    • 12:30-1:30pm @ Allen 2nd floor break out (Alexandra + Rasmus)
    • 4:30-5:30pm @ Allen 2nd floor break out (Antonio + Trisha)
  • Friday
    • 12:30-1:30pm @ Allen 3rd floor break out (Kelbin + Sonya)
    • 2:30-3:30pm @ Gates (CSE2) 310 (David)

Assignments and Handins

All assignments are turned in on Gradescope.

Prerequisites

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 in an imperative language (ideally C or C++); be comfortable writing and debugging assembly code; and be comfortable in a command-line Unix development environment (gdb, gcc, etc). We strongly recommend taking CSE 391 before CSE 484. 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!