Cybersecurity Under Pressure. Real Attacks, Real Lessons podcast

Validating Automotive Supplier VEX Claims

0:00
31:54
Manda indietro di 15 secondi
Manda avanti di 15 secondi

A supplier declares an automotive ECU not affected by a vulnerability identified in a software component. What evidence should the manufacturer request before relying on that assessment?


This Friday episode explores a hypothetical supplier-assurance scenario involving closed-source firmware, a safety-related ECU and production constraints. The discussion contrasts component absence with code reachability, examines build-specific evidence and considers the trade-offs between accepting an assessment, requesting further investigation, applying containment and updating software.


Editorial clarification: this is not a documented vehicle incident. A VEX statement does not by itself determine a TARA risk rating or authorize risk retention. Binary analysis findings remain bounded by their method and coverage. The evidence package discussed is an assurance proposal, not a universal VEX requirement; regulatory and safety consequences require case-specific assessment.


More analysis: https://cybersecurityunderpressure.com

Altri episodi di "Cybersecurity Under Pressure. Real Attacks, Real Lessons"