|Instructor||Gang Wang (firstname.lastname@example.org)|
|Time/Location||TR: 11:00 AM - 12:15 PM, 0216 Siebel Center for Comp Sci|
|Instructor Office Hour||Tue: 12:15 PM - 1:00 PM at Siebel 4316|
|TA||Hyun Bin (HB) Lee, email@example.com, Office hour: TR: 10:00 AM - 10:45 AM at Siebel 4309|
Program security, trusted base, privacy, anonymity, non-interference, information flow, confinement, advanced auditing, forensics, intrusion detection, key management and distribution, policy composition and analysis, formal approaches to specification and verification of secure systems and protocols, and topics in applied cryptography. Course Information: Same as ECE 424. 3 undergraduate hours. 3 or 4 graduate hours. Prerequisite: CS 461. Recommended: CS 475.
Learning Goals: Identify and address privacy issues in social networks; Apply machine learning to security and address adversarial machine learning; Use crypto constructs (homomorphic encryption, multi-party computation, etc.); Identify and address issues with de-identification; Use hardware designed to support trusted computing; Reason about information flow, computational security for encryption; Recognize threats and design mitigations for security in key sectors (healthcare, power grid, transportation, etc.); Understand architecture and recognize threats for smartphone security; Recognize issues with web privacy (especially cookies and advertising); Analyze human factors; Recognize and mitigate insider threats; Understand architecture and recognize threats for security in the Internet of Things (IoT); Recognize drivers and tactics in cyber warfare, and other topics of emerging interest in security and privacy.
Important note: It assumes a basic knowledge of the area such as the material covered by Computer Security I (CS 461). This semester it will expect ability to program in Java and C or C++.
Participation: Students are required to attend all the lectures. Please inform the instructor and the TA via email if you cannot make it to the class due to travel or sickness.
Quizzes: Students are expected to complete a short quiz within 24 hours after each lecture. The quiz contains 4-5 single-choice or multi-choice questions. The quiz is closely related to the respective lecture and is designed to be light-weighted (and hopefully fun) to improve student engagement during the lecture. Quiz is not graded --- students will receive points by simply trying them.
Machine Problem (MP): Students are expected to work on 4-5 MPs throughout the semester. The projects will involve hand-on programming and data analysis, covering various topics that complement the lecture topics. Example topics include tracking user location based on social network data, interacting with Bitcoin APIs, multiple parties performing joint machine-learning without directly exchanging data. The list of project topics will be released later in Spring 2020.
Survey paper: This is for 4-credit student only.
|Week 1: Jan 21||Course Plan (GW) slides||MP1 open|
|Week 1: Jan 23||Introduction (GW) slides|
|Week 2: Jan 28||Online Social Networks (GW) slides|
|Week 2: Jan 30||Machine Learning 1 (GW) slides|
|Week 3: Feb 4||Machine Learning 2 (GW) slides||MP1 due|
|Week 3: Feb 6||Crypto Constructs (GW) slides||MP2 open|
|Week 4: Feb 11||De-Identification (GW) slides|
|Week 4: Feb 13||Trusted Computing 1 (HB) slides||MP2 due (MP3 open)|
|Week 5: Feb 18||Trusted Computing 2 (HB) slides|
|Week 5: Feb 20||Information Flow (GW) slides|
|Week 6: Feb 25||Crypto Models (GW) slides|
|Week 6: Feb 27||No Class|
|Week 7: Mar 3||Crypto Models (GW)||MP3 due|
|Week 7: Mar 5||Health IT|
|Week 8: Mar 10||Midterm|
|Week 8: Mar 12||Bitcoin (GW)||MP4 open|
|Week 9: Mar 17||Spring Break|
|Week 9: Mar 19||Spring Break|
|Week 10: Mar 24||Smartphones 1 (GW)|
|Week 10: Mar 26||Smartphones 2 (GW)||Survey Proposal due|
|Week 11: Mar 31||Web Privacy (GW)|
|Week 11: Apr 2||Automobiles (GW)|
|Week 12: Apr 7||Internet Security (GW)||MP4 due|
|Week 12: Apr 9||Automobiles AML (GW)||MP5 open|
|Week 13: Apr 14||Code Stylometry (GW)|
|Week 13: Apr 16||Smart Grid (CG)|
|Week 14: Apr 21||Hardware Side Channels (CF)|
|Week 14: Apr 23||Insider Threats (GW)|
|Week 15: Apr 28||Cyber Warfare (GW)|
|Week 15: Apr 30||Conclusion (GW)||MP5 due|
|Week 16: May 5||PM 5 Presentation|
|Week 16: May 7||Reading day, no class|
|Week 16: May 8||Final exam (7pm - 10pm), SC0216|
|Week 16: May 10||Survey due (Sunday midnight)|
|Class attendance and participation||15%|
This will be used for 100% of the grade for 3-credit students and 75% of the grade for 4-credit students. 4-credit students are expected to complete a survey paper (25% of the total grade). Letter grades are assigned based on how well you do (e.g., 90+ means "A"), not based on your performance relative to other students. We do not curve the grades in any way.
Late Policy: Please see the individual assignment instructions.
Academic Integrity: Students must follow the university's guidelines on academic conduct (quick link). This course will have a zero-tolerance policy regarding plagiarism. You should complete all the assignments and quizzes on your own. In this course, you can help your classmates with questions such as how to use the programming language, what the library classes or methods do, what the errors mean, and how to interpret the assignment instructions. You are encouraged to post any such questions to the course discussion forum, and are also encouraged to answer questions posted to the forum from other students. However, you may not give or receive help from others (except the TA) with writing your program code or writing your answers for any of the assignments or tests. Do not show or share your program code with others, and do not view or copy source code from others. All electronic work submitted for this course will be archived and subjected to automatic plagiarism detection. Whenever in doubt, please seek clarifications from the instructor. Students who violate Academic Integrity policies will be immediately reported to the department and the college (which could leave a permanent mark on the transcript).
Note: students who are struggling with problems in a program assignment may have trouble interpreting an error message or diagnosing an error in their source code. I encourage you to ask questions about the interpretation of error messages on the forum, and to offer constructive advice to fellow students who run into such problems. If you are asking for help with an error or problem, describe it without showing code where possible. When necessary, you may post a short segment of your code that you believe contains the problem (a handful of lines where you believe the problem to be). However, refrain from posting significant portions of your problem solution to the course discussion board. Posts with excessive code may be deleted without notice. Ask the instructor if you are unsure what you are about to post is appropriate. Other than small code segments posted to the course discussion board, you should not use any mechanisms to share or view another student's code, and should not post your own code in any publicly accessible location.
Special Accommodations: If you need special accommodations because of a disability, please contact the instructor in the first week of classes.