Bridging the Gap: The Convergence of Hardware and Software Security
summary
Argues that software must be scanned on the device because vulnerabilities only reveal themselves when running on hardware, and teams struggle to convince hardware engineers to test software in situ. Recommends treating firmware the same as application code — treat firmware like software — with vulnerability scanning, secure development practices, and SecOps workflows. Reports heavy use of AI-assisted testing alongside traditional vulnerability scanning to find issues across hardware and software layers.
AI-written summary · about
related talks
40mHardware Security Is Hard: How Hardware Boundaries Define Platform Security
44mHardware Security By Design
41mUnique Challenges Of Security Programs For Hardware/IoT Makers
03mGreat software is secure software
01h 06mEscaping Vulnerability Hell: Bridging the Gap Between Developers and Security Teams
49mPragmatic Approaches To Building Secure Software
45mBuilding Secure Software: Practical Strategies for Developers
38mPrioritizing Trust While Creating Applications