CSC 433 - Privacy in the Digital Age, Spring 2025
All students in this course will be required to survey a real-world privacy incident throughout the semester. Here are some good sources New York Privacy Stories, New York Privacy Projects. However, try to explore any personal privacy incident you experienced.
Your task will involve providing details related to the following items:
- Incident description
- Implication of the incident
- Root cause analysis of the incident
- Precautions or countermeasures
- Timeline of the entire incident showing when the incident was discovered, actions taken, etc.
- What did you learn from the incident, and how can you apply any of the concepts or content covered in the course to address or even avoid such incidents?
Schedule
| Deadline | Assignment |
|---|---|
| 02/13 | Privacy incident topic submission (10 points) |
| 03/07 | Progress report covering points 1 to 3 listed above (30 points) |
| 04/22 | Final full report covering all points (60 points) |
The various survey assignments are designed to make sure you make proper steady progress throughout the semester. These assignments will enable you to obtain early feedback on your ongoing work. All survey-related assignments will be graded within one to two weeks if they are submitted on time. No late assignments will be accepted, except for legitimate reasons (obtaining approval from the instructor beforehand).
Deliverables
Topic Selection
Submission through a Google form. You are expected to submit your own topic ideas (provide a small paragraph describing the topic you want to work on). Please submit two to three ideas using the following Google Form.
Progress/Full Report
After the title, provide your names and unity ID. Submission should be in PDF.
Use Latex with font size 11pt and single space. The final report should be around 6 pages excluding references. Use the ACM Latex style file available here ACM_LATEX. Use the sample-sigconf.tex sample and change the font size to 11pt [\documentclass[sigconf,11pt]{acmart}] Or use Overleaf. Submissions not following this format will be penalized.Here are some things we will be looking for in your report:
- Properly formatted bibliography with an appropriate number of references (most reports should have at least 10 references; references can include online blogs, and conference or journal papers). Use IEEE or ACM format BibTeX format using \bibliographystyle{acm} or \bibliographystyle{IEEEtran}
- Paper that has been spell checked and proofread. If English is not your native language, please request a friend to help you proofread your final paper before you submit it. Also, take advantage of word processors with spell checkers and grammar checkers like `Grammarly'. There are also writing centers on campus with tutors who can assist you.
- Well-formatted paper (adequate margins and spacing, proper font size, clear figures with appropriate captions, etc.).
Grading rubric for progress report
| Criteria | Weight |
|---|---|
| Incident description | 20% |
| Implication of the incident | 30% |
| Root cause analysis of the incident | 40% |
| Reference | 10% |
Grading rubric for full final report
| Criteria | Weight |
|---|---|
| Incident description | 10% |
| Implication of the incident | 10% |
| Root cause analysis of the incident | 20% |
| Precautions or countermeasures | 20% |
| Timeline of the entire incident showing when the incident was discovered, actions taken, etc. | 20% |
| What did you learn from the incident, and how can you apply any of the concepts or content covered in the course to address or even avoid such incidents? | 10% |
| Reference | 10% |