Project

Hardware Security Education for All

A collaborative curriculum project. The modules let a department teach hardware security inside required design courses, so students who never enroll in a hardware-security elective still meet reverse engineering, side channels, logic locking, and hardware Trojans.

People

Tanvir HossainEECS, University of Kansas · tanvir@ku.edu
Mahmudul HasanEECS, University of Kansas · m.hasan@ku.edu
Kareem El-ArabyEECS, University of Kansas
Lorenzo R. GodinezEECS, University of Kansas
Swarup BhuniaECE, University of Florida · swarup@ece.ufl.edu
Md Tauhidur RahmanECE, Florida International University · mdtrahma@fiu.edu
Tamzidul HoqueEECS, University of Kansas · hoque@ku.edu

Email addresses follow the author block of the curriculum paper. For an instructor packet, write to the Kansas group.

The paper this site follows

This site follows the paper Bringing Hardware Security Education to All: A Seamless Curriculum Integration Approach, prepared for ISQED 2027. The paper states the three obstacles, the five design rules, the nine modules, where each one has been taught, and the limits of the survey results.

If a lab manual and the paper disagree on a step, students follow the manual. This site uses the paper for status, scope, and survey results.

The paper also states the workforce context. An industry analysis projects growth in the U.S. semiconductor workforce from about 345,000 to about 460,000 positions by 2030, with a large share of new technical roles at risk of going unfilled. Employment of information security analysts is projected to grow much faster than employment overall. The required courses in the programs that train those graduates still skip hardware security.

What a department can take

  • The selection principle and the five rules, if you want to write a module of your own.
  • The catalog, if you want to drop an existing module into a course you already teach.
  • The results, if you need to know what has been taught and what is still only written down.

The site is a set of static pages. Nothing here needs a server-side application.

Support

This work was supported in part by the U.S. National Science Foundation (NSF) Secure and Trustworthy Cyberspace (SaTC) program under Award No. 2114157.

Any opinions, findings, and conclusions or recommendations expressed in this material are those of the authors and do not necessarily reflect the views of the U.S. National Science Foundation.

The project is a collaboration of the University of Kansas, the University of Florida, and Florida International University.