Usable Privacy and Security (original) (raw)

This course does not use Blackboard.

Readings will be assigned from the following text (available in the CMU bookstore and from all the usual online stores):

Additional readings will be assigned from papers available online or handed out in class. In cases where a subscription is required for access, access should be available for free when you are coming from a CMU IP address (on campus or via CMU VPN).

Note, this is subject to change. The class web site will have the most up-to-date version of this calendar.

Date

Topics

Assignment

To be done before coming to class

Monday, January 11

01. Course overview and introductions (Lujo and Nicolas) [SLIDES]

No readings for this class.

Wednesday, January 13

02. Introduction to security; usable encryption (Lujo) [SLIDES]

Optional reading:

Monday, January 18

No class due to Martin Luther King, Jr. Day

No readings for this class.

Wednesday, January 20

03. Reasoning about the human in the loop (Nicolas) [SLIDES | Privacy Illustrated]

Optional reading:

Monday, January 25

04. Introduction to privacy; the difficulty of measuring privacy (Nicolas) [SLIDES]

Homework 1 due

Optional reading:

Wednesday, January 27

05. Introduction to experimental design: overview of methods, ethics/deception, and ecological validity (Nicolas) [SLIDES]

Optional reading:

Monday, February 1

06. Introduction to crowdsourced studies (Nicolas) [SLIDES]

Homework 2 due

Discuss course projects in class

Optional reading:

Wednesday, February 3

07. Qualitative studies: surveys, interviews, focus groups, and diary studies (Guest lecture by Manya Sleeper) [SLIDES]

Optional reading:

Monday, February 8

08. Usable privacy and security in the home; analyzing qualitative data (Guest lecture by Blase Ur) [SLIDES]

Optional reading:

Wednesday, February 10

09. Practicalities of research: IRBs and teamwork (Abby) [SLIDES]

Homework 3 due

Project preference forms also due

No readings for this class.

Monday, February 15

10. Quantitative data collection; field studies; hypothesis testing; simulating attack scenarios (Lujo) [SLIDES]

Homework 4 due

Project teams assigned (no written assignment)

Optional reading:

Wednesday, February 17

11. Security warnings (Lujo) [SLIDES]

Project proposal due

Optional reading:

Monday, February 22

12. Analyzing quantitative data with statistics (Nicolas) [SLIDES]

Homework 5 due

Optional reading:

Wednesday, February 24

13. Text passwords; graphical passwords (Nicolas) [SLIDES]

Optional reading:

Monday, February 29

14. Authentication in practice: challenge questions, two-factor auth, and biometrics (Lujo) [SLIDES]

Homework 6 due

IRB applications must be submitted to the IRB no later than this date

Optional reading:

Wednesday, March 2

15. In-class midterm exam 1

No readings for this class.

Monday, March 7

No class due to spring break

No readings for this class.

Wednesday, March 9

No class due to spring break

No readings for this class.

Monday, March 14

16. SSL, PKIs, and secure communication (Nicolas) [SLIDES]

Optional reading:

Wednesday, March 16

17. Usability of privacy policies and the dimensions of privacy notice (Lujo) [SLIDES]

Optional reading:

Monday, March 21

18. Progress report presentations

Project progress report due

Wednesday, March 23

19. Designing a usable, short-form privacy notice (Blase Ur) [[SLIDES](18-short privacy notice.pdf)]>

Homework 7 due

Monday, March 28

20. Privacy and security for mobile and ubicomp devices (Lujo) [SLIDES]

Optional reading:

Wednesday, March 30

21. Making privacy and anonymity tools usable (Nicolas) [SLIDES]

Homework 8 due

Optional reading:

Monday, April 4

22. Designing privacy tools for web browsing (Nicolas) [SLIDES]

Optional reading:

Wednesday, April 6

23. Social networks and privacy (Guest lecture by Manya Sleeper) [SLIDES]

Homework 9 due

Optional reading:

Monday, April 11

24. User education/training; anti-phishing (Lujo) [SLIDES]

Optional reading:

Wednesday, April 13

25. Behavioral Economics; Prospect Theory (Nicolas) [SLIDES]

Optional reading:

Monday, April 18

26. In-class midterm exam 2

No readings for this class.

Wednesday, April 20

27. Access control and policy configuration (Lujo) [SLIDES]

Homework 10 due

Optional reading:

Monday, April 25

28. Mental models and folk models of security; non-US perspectives in research; the usability of software updates (Nicolas) [SLIDES]

Optional reading:

Wednesday, April 27

29. Usable privacy and security in safety-critical devices (Lujo) [SLIDES]

Optional reading:

May 6, 2016 (Final exam period)

FINAL PROJECT PRESENTATIONS in Baker Hall A53, at 8:30am

Your final papers are also due at the beginning of this timeslot, to be emailed to both professors and the TA.

---

You are responsible for being familiar with the university standard for academic honesty and plagiarism. Please see the CMU Student Handbook for information. In order to deter and detect plagiarism, online tools and other resources may be used in this class. Students caught cheating or plagiarizing will receive no credit for the assignment on which the cheating occurred. Additional actions -- including assigning the student a failing grade in the class or referring the case for disciplinary action -- may be taken at the discretion of the instructors.

This class will have no final exam. However, the scheduled final exam period (May 6, 2016, in BH A53) will be used for final project presentations. You are required to be present for your group's final presentation during the exam period.

All homework is due in printed form in class at 3:00 PM each Wednesday, unless specified otherwise on the schedule above. Homework may not be submitted after 3:05 pm, and we do not accept late homework. Your single lowest homework grade will be dropped from your homework average.

Students taking the 12-unit version of the course will be asked to submit a short summary (3-7 sentences) and a "highlight" for particular readings specified in each homework assignment. The highlight may be something you found particularly interesting or noteworthy, a question you would like to discuss in class, a point you disagree with, etc.

Students are expected to complete the assigned reading prior to class so that they can participate fully in class discussions. To verify that students have completed the assigned reading, each class will begin with a short quiz. The quizzes will cover major points of the readings, including methodological techniques, findings, high-level takeaways, and major recommendations the authors made. Your single lowest quiz grade will be dropped.

Students taking the 12-unit version of this course are expected to do additional readings each week. In some cases, we will specify which extra reading(s) to do. In other cases, we will specify that students can choose from any of the optional readings for the week. All other students are encouraged to review some of the optional readings that they find interesting, but they need not submit summaries or highlights of the optional readings.

We will hold two in-class midterms during the course. These midterms will be centered around designing experiments, interpreting results, and analyzing research claims related to usable privacy and security. In essence, performing well on these exams will require that you apply the skills you learn in this course, rather than remembering trivia. The best way to prepare for these exams is to critically read all of the assigned papers for the course and to be an engaged participant in class discussions and in-class design assignments throughout the semester.

Students will work on semester projects in small groups that include students with a variety of areas of expertise. A choice of projects will be provided, and students will be given an opportunity to indicate their preferences before projects are assigned. Students who have their own ideas for projects should discuss them with the instructors early in the semester.As part of the project students will:

Students are encouraged to submit their project as a poster to the 2016 Symposium On Usable Privacy and Security, and/or as a full paper to SOUPS 2016 or another conference. A paper submission will likely require additional work after the end of the semester. To submit a poster will only require submitting a 2-page abstract.

Students signed up for the 12-unit version of this course are expected to play a leadership role in a project group that writes a project paper suitable for publication. Your final paper should be written in a style suitable for publication at a conference or workshop. The conference papers in the readings provide good examples of what a conference paper looks like and the style in which they are written. In addition to describing what you did in your study, your paper should include a related work section and properly-formatted references. Papers should follow the SOUPS 2016 technical papers formatting instructions. However, your report for the class need not adhere to the SOUPS page limits and should not be a blind submission; please include the names of the authors for the purposes of the class project.

All teaching materials in this class, including course slides, homeworks, assignments, practice exams and quizzes, are copyrighted; reproduction, redistribution and other rights solely belong to the instructors (Nicolas Christin and Lujo Bauer). In particular, it is not permissible to upload any or part of these materials to public or private websites without the instructor's explicit consent. Violating this copyright policy will be considered as an academic integrity violation, with the consequences discussed above. Reading materials are also copyrighted by their respective publishers and cannot be reposted or distributed without prior authorization from the publisher.

to the instructor, or to anyone else about any of the homework assignments. Any assistance, though, must be limited to discussion of the problem and sketching general approaches to a solution. Each student must write out his or her own solutions to the homeworks. Consulting another student's solution is prohibited, and submitted solutions may not be copied from any source. These and any other form of collaboration on assignments constitute cheating. Any form of collaboration is strictly prohibited on the exams and is considered cheating. If you have any question about whether some activity would constitute cheating, please feel free to ask. Cheating on an assignment/exam will result in failure of the course, and the university administration (department, college) will be notified per the appropriate procedures. Simply stated, feel free to discuss problems with each other, but do not cheat. It is not worth it, and you will get caught. In addition to the above, please also review fully and carefully Carnegie Mellon University's policies regarding Cheating and Plagiarism (http://www.cmu.edu/policies/documents/Cheating.html); Undergraduate Academic Discipline (http://www.cmu.edu/policies/documents/AcadRegs.html); and Graduate Academic Discipline (http://www.cmu.edu/policies/documents/GradDisc.html). In addition to the terms of the Graduate Academic Discipline policy, it is INI and ECE's policy that an INI or an ECE graduate student may not drop a course in which a disciplinary action is assessed or pending without the course instructor's explicit approval.