Session
Transparency Upstream, Evidence Downstream: SBOMs, AI Code and the CRA
Given at Code & Compliance 2026, Brussels, 27 October 2026.
One fictional manufacturer, one real vulnerability, and today’s law. Maria spends a Log4Shell day under the EU Cyber Resilience Act, and her record is built from upstream signals: advisories, package URLs, SBOMs and VEX.
The talk shows why SBOMs taken from source, build, shipped artefact and running fleet give four different answers, and how a PHP interpreter that came with a base image can be in everything you shipped and in nothing you declared, as the October 2026 PHP flaws showed. It covers when the 24-hour reporting clock actually starts, why the same component version can lead to different verdicts, and what VEX cannot record: confidence in the verdict. It asks what a support period means when seven-year-old firmware has to be rebuilt, and what to keep when AI writes the code: the result, the toolchain and the reasoning, not the prompt. It closes with who signs, the manufacturer and not the maintainer, and with the second reader of the record: product liability under the revised Product Liability Directive.
William Janssen
CTO & Head of Engineering | Author of a book on the EU Cyber Resilience Act | Building the operational side of CRA compliance | Ex-Red Hat & Founder
The Hague, The Netherlands
Links
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top