8:30 – 9:00

Registration

9:00 – 9:30

Defending the Number: Making an SBOM → CRA Decision You Can Explain Later

Article 14 is live, which means somebody eventually has to explain why a given vulnerability was or wasn’t reported. That explanation is the deliverable, not the number. Working from one real container SBOM and multiple scanners and databases that disagree with each other, this talk builds the audit trail backwards: what you matched, what you dropped, what you assumed, and what evidence you kept. Less about tooling selection, more about the artefacts that make a defensible process. Closing posture, unchanged since April: sources will contradict, you will have to be opinionated, and your CRA defence is in the process. This is not a finish line, it’s a treadmill.

9:30-10:00

Lukas Krug, Stackable
Lukas Krug,
Stackable

AI-Assisted Vulnerability Management for an Open Source Data Platform

Our product is a data platform that bundles open source projects such as Apache Kafka, Apache Airflow, Apache Spark and Trino, each in several supported versions. Because of that vast scope, a single platform release contains over 50,000 reported vulnerabilities across its roughly 40 product and operator images. With two supported releases at any time we face that scope twice over, which is far more than our security team can analyze by hand.

10:00-10:30

Vladimir Slavov
Vladimir Slavov, Bosch, OpenChain

OpenChain: Towards a More Secure and Compliant Software Supply Chain

Across industries, more than half of the software used is now open source (OSS). This includes both OSS in a company’s own developed products, and OSS in components provided by suppliers. The shift towards OSS has led to an ever increasing demand for license compliance, security assurance, and software bills of material (SBOMs). In addition to that, the need for supply chain visibility required to address security issues will only become more crucial with the introduction of the EU’s Cyber Resilience Act.
To deal with these challenges, organizations can adopt the ISO standards developed within the OpenChain community, namely 5230:2020 for license compliance and 18974:2023 for security assurance. This talk will highlight where to start and how you can get involved in the OpenChain community.

10:30-11:00

Tea break

11:00-11:30

Emelie Markianos, Threat Intelligence consultant

What Does the Internet Know About Your Software?

Every piece of software an organization runs — from the framework in production to the small utility library buried four dependencies deep — has a public shadow: commit histories, mailing list threads, forum posts, expired domains, and the personal footprints of the people who maintain it. None of this is secret. All of it is searchable. And almost none of it shows up in a vendor questionnaire or an SBOM. This talk uses open-source intelligence (OSINT) as a lens for a question security teams rarely ask directly:
what does the internet already know about the software we depend on — and about the people who build it?

11:30-12:00

Martin von Willebrand
Martin von Willebrand, Double Open

ORT Server as an open source tool for software asset tracking and regulatory compliance.

ORT Server covers software component analytics, scanning, vulnerability monitoring and resolution, license compliance, SBOM and artefact management. It is a fully open source platform with many adopters across Europe. It supports configuration as code and within a nice UI. It’s an API first platform well suited for MCP servers and building agentic workflows to e.g. manage vulnerabilities or license compliance rule violations.
This talk introduces the ORT Server, it’s building blocks and it’s community, and its capabilities, mapping them to the CRA obligations. It goes on to show practical usage patterns. And examples on how agentic workflows can be built

12:00-12:30

Emil Albrektsson
Emil Albrektsson, Application security developer @ Nav

Building TPT: From alert chaos to clear priorities


Applications generate hundreds of vulnerability alerts, but which ones actually matter? Nav’s AppSec team built TPT (Titt på Ting), an open-source tool that helps remediate this problem using free data sources. In this talk, I’ll share how we transformed overwhelming vulnerability backlogs into actionable, prioritized workflows. Learn about our risk-scoring approach, how we aggregate data from multiple free sources, and the UX principles that help developers prioritize.

12:30-13:30

Lunch

13:30-14:00

To be announced

14:00-14:30

Arnaud Le Hors, IBM, OpenSSF
Arnaud Le Hors, IBM, OpenSSF

How many security badges do we need?

The EU Cyber Resilience Act puts a responsibility on the manufacturer for all components used. A SBOM is required and for each component, the manufacturer needs to do due diligence – both for open source and commercial components.
In order to help, there has been multiple projects that create some sort of assessment on the projects, in many cases with a “security badge”.
This talk is a call to action: Is it helpful to create more badges? There are so many that open source developers are overwhelmed, which unfortunately leads to them not doing anything. What can we do to simplify for Open Source projects and still assist manufacturers?

14:30-15:00

To be announced

15:00-15:30

Break
After the break, single track session

15:30-16:00

Astor Nummelin Carlberg
Astor Nummelin Carlberg, Director of Open Source Sovereignty at SUSE

KEYNOTE: Beyond compliance : Building resilience

The Cyber Resilience Act asks a clear question of every product placed on the European market: is it secure enough? That question matters, but it is not the only one. Resilience also depends on what happens when circumstances change, such as when a supplier changes its terms, a jurisdiction changes its laws, or a critical component is left without anyone to maintain it.
This talk takes a broad view of how Europe’s policy agenda is moving from compliance towards resilience. It connects the CRA to the wider EU push on digital sovereignty, including the new Open Source Strategy and the Cloud and AI Development Act. It then asks what these mean for the organisations that build and run software. The argument is that open source and open standards sit at the centre of the answer, because they decide whether an organisation can still choose, adapt and act when it matters most.

16:00-17:00

Olle E. Johansson
Olle E. Johansson

Summary and closing

Olle E. Johansson

Open Source Security Foundation
OWASP Foundation
Open regulatory compliance working group (ORCWG.ORG)