Challenges & Benefits of Certification for Security Hardware
summary
Argues that hardware roots are necessary because software alone can’t scale, cites concrete IP and certifications: Rambus tests side‑channel resistance with the Rambus EPA workstation, offers a CryptoManager root of trust already in FIPS 140‑2 CAVP and targeting FIPS 140‑3, provides an ISO 26262 ASIL‑D automotive variant, and notes cryptographic accelerators used in Common Criteria EAL4+ certified products. Describes costs: lab fees, engineer time, and likely rework when standards change.
AI-written summary · about
chapters (13)
- 0:00Introduction to certification
- 1:05Why hardware security matters
- 2:31Types of hardware security IP
- 4:18Building vs buying security IP
- 6:23Measuring security effectiveness
- 7:48Role of certification in security
- 11:16NIST FIPS 140 certification
- 13:42FIPS 140-3 updates and challenges
- 15:08ISO 26262 functional safety
- 16:13ISO/SAE 21434 automotive cybersecurity
- 17:16Common Criteria overview
- 17:58Benefits of certification for customers
- 19:48Q&A and closing remarks
related talks
36mSecurity compliance: A global perspective
48mCXO PANEL: Security Certifications for IoT Devices
37mHow To Approach InfoSec Like a Fed(eral Auditor)
44mHardware Security By Design
41mUnique Challenges Of Security Programs For Hardware/IoT Makers
59mNationally Critical Infrastructure needs Secure Hardware
17mA First Secure RISC-V Common Criteria Certified Root of Trust
16mKeynote: RISC-V Security - Current Initiatives and Future Trends