Students in this class must adhere to ASU's academic integrity policy, which can be found at https://provost.asu.edu/academic-integrity/policy). Students are responsible for reviewing this policy and understanding each of the areas in which academic dishonesty can occur. In addition, all engineering students are expected to adhere to both the ASU Academic Integrity Honor Code and the Fulton Schools of Engineering Honor Code. All academic integrity violations will be reported to the Fulton Schools of Engineering Academic Integrity Office (AIO). The AIO maintains record of all violations and has access to academic integrity violations committed in all other ASU college/schools.
Students in this class must adhere to ASU's academic integrity policy, which can be found at https://provost.asu.edu/academic-integrity/policy). Students are responsible for reviewing this policy and understanding each of the areas in which academic dishonesty can occur. In addition, all engineering students are expected to adhere to both the ASU Academic Integrity Honor Code and the Fulton Schools of Engineering Honor Code. All academic integrity violations will be reported to the Fulton Schools of Engineering Academic Integrity Office (AIO). The AIO maintains record of all violations and has access to academic integrity violations committed in all other ASU college/schools.
Course content, including lectures, are copyrighted materials and students may not share outside the class, upload to online websites not approved by the instructor, sell, or distribute course content or notes taken during the conduct of the course (see ACD 304-06, "Commercial Note Taking Services" and ABOR Policy 5-308 F.14 for more information). You must refrain from uploading to any course shell, discussion board, or website used by the course instructor or other course forum, material that is not the student's original work, unless the students first comply with all applicable copyright laws; faculty members reserve the right to delete materials on the grounds of suspected copyright infringement.
Students, faculty, staff, and other individuals do not have an unqualified right of access to university grounds, property, or services. Interfering with the peaceful conduct of university-related business or activities or remaining on campus grounds after a request to leave may be considered a crime. All incidents and allegations of violent or threatening conduct by an ASU student (whether on- or off-campus) must be reported to the ASU Police Department (ASU PD) and the Office of the Dean of Students.
Arizona State University is committed to providing an environment free of discrimination, harassment, or retaliation for the entire university community, including all students, faculty members, staff employees, and guests. ASU expressly prohibits discrimination, harassment, and retaliation by employees, students, contractors, or agents of the university based on any protected status: race, color, religion, sex, national origin, age, disability, veteran status, sexual orientation, gender identity, and genetic information. Title IX is a federal law that provides that no person be excluded on the basis of sex from participation in, be denied benefits of, or be subjected to discrimination under any education program or activity. Both Title IX and university policy make clear that sexual violence and harassment based on sex is prohibited. An individual who believes they have been subjected to sexual violence or harassed on the basis of sex can seek support, including counseling and academic support, from the university. If you or someone you know has been harassed on the basis of sex or sexually assaulted, you can find information and resources at https://sexualviolenceprevention.asu.edu/faqs.
Problem sets or laboratory assignments or course project submitted after the due date/time are considered late and will not be graded. Late submissions will only be graded in cases of documented emergencies.
Discussion of course material and collaboration with other students is encouraged but each student must write/type and submit his/her own solution. Your essays, code and proofs (if applicable) should never contain sections which are identical to the submission of another student, past or present. Submitted work must be entirely that of the student(s) whose name(s) appear(s) on the submission and not solicited in any way from others. Violation of these policies can result in automatic failure of the course.
Week | Monday | Wednesday |
Topic Introduction to cybersecurity: Hardware Perspective |
Jan. 13 Overview of Hardware Security M. Kinsy |
Jan. 15 Taxonomy of Hardware Security M. Kinsy |
Topic Classic and Modern Encryption Algorithms |
Jan. 20 Martin Luther King Jr. M. Kinsy |
Jan. 22 Classical Encryption Techniques M. Kinsy |
Topic Message Authentication: Secrecy vs. Integrity |
Jan. 27 Modern Encryption Techniques M. Kinsy |
Jan. 29 Encryption & Digital Signatures M. Kinsy |
Topic Distributed Trustworthy Systems |
Feb. 03 Distributed Key Management M. Kinsy |
Feb. 05 Confidentiality Assessment M. Kinsy |
Topic Information Leakage |
Feb. 10 Covert Channels Project 1 DUE M. Kinsy |
Feb. 12 Side-Channels M. Kinsy |
Topic Trusted digital system design |
Feb. 17 Verilog Fundamentals M. Kinsy |
Feb. 19 Hardware Root-of-Trust Design Project 2 DUE M. Kinsy |
Topic Hardware Security Primities |
Feb. 24 Physical Unclonable Functions M. Kinsy |
Feb. 26 Project 3 Overview M. Kinsy |
Topic Hardware Security Primities |
Mar. 03 Fall Break M. Kinsy |
Mar. 05 Oblivious RAM (ORAM) & Rowhammer M. Kinsy |
Topic Hardware Authentication Techniques |
Mar. 10 Hardware Trojans M. Kinsy |
Mar. 12 Anti-Tamper Design Techniques Project 3 DUE M. Kinsy |
Topic Homomorphic Encryption (HE) |
Mar. 17 Homomorphic Encryption Algorithms M. Kinsy |
Mar. 19 HE Software and Hardware Libraries M. Kinsy |
Topic Post-Quantum Encryption (PQC) |
Mar. 24 PQC Algorithms |
Mar. 26 PQC Implementation Examples |
Topic Embedded systems (ES) security |
Mar. 31 Connected Component Security |
Apr. 02 Trusted Compute Base for ES Project 4 DUE |
Topic Programmable Hardware Systems Security |
Apr. 07 FPGA Secuirty Concerns |
Apr. 09 Watermarks and Identifiers |
Topic Secure Processor Design |
Apr. 14 Trusted Execution Environment (TEE) |
Apr. 16 Enclave-Based Computing |
Topic Review &Presentations |
Apr. 21 Hardware Secuirty Primitives |
Apr. 23 Secure Design Patterns Project 5 DUE |