CSE 590Y (Security Seminar)

Wednesdays @ 2:30pm in CSE 203

Topic: Test of Time Award papers from USENIX Security and ACM CCS

Schedule:

9/26: Brief intros+organization
10/3: Guest speaker Kirill Nikitin (EPFL)
10/10: Kimberly and Chris: Privacy and security in library RFID: issues, practices, and architectures
10/17: Eric and Cam: Why Johnny Can't Encrypt: A Usability Evaluation of PGP 5.0
10/24: Guest speaker Mathias Lecuyer (Columbia University)
10/31: Anna and Ivan: Design and implementation of the idemix anonymous credential system
11/7: Lucy and Christine: Mimicry Attacks on Host-Based Intrusion Detection Systems
11/14: Likely cancellation (USENIX Security deadline)
11/21: Canceled (Thanksgiving)
11/28: Matt: Dynamic and efficient key management for access hierarchies
12/5: Kiron and Peter: Tor: The Second-Generation Onion Router

Presentation Guidelines:

Your goal is to provide an overview of the paper and foster a discussion around it, including: What problem does the paper try to address and how? How does it fit into the broader context (e.g., related work)? What are the positive and negative aspects of the paper/approach? What new research questions does it raise?
Please be positive! It’s easy to find reasons to criticize papers. While it’s useful to also discuss these weaknesses, you should also focus on why a paper might have been accepted, what we can learn from it, or how you might build on it. Think about how you would like other seminar to discuss *your* work! :)
The use of slides to guide and organize your presentation is preferred. You’re welcome to borrow slides from the paper’s authors if you can find them. USENIX posts videos of conference presentations; they’re great to help you prepare, but please use them sparingly during seminar.
Keep in mind that not everyone is a security expert (yet! :)), so please make sure to explain concepts or context that those newer to the field might not yet know.
Borrowing from USENIX’s code of conduct and speaker guidelines: “Speakers are responsible for the content of their presentations, but USENIX requests that speakers be cognizant of potentially offensive actions, language, or imagery, and that they consider whether it is necessary to convey their message. If they do decide to include it, USENIX asks that they warn the audience, at the beginning of the talk, and provide them with with the opportunity to leave the room to avoid seeing or hearing the material.” Another type of content to avoid is content identified as classified by a government, content that clearly violates a company's intellectual property, and so on. We do have one deviation from the USENIX policy: since this is a class, everyone should be able to attend. This means that you should avoid using the types of material mentioned in this bullet.

Questions?

franzi@cs.washington.edu

yoshi@cs.washington.edu