Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create Taking-responsibility-for-your-software-How-to-simply-monitor-… #3177

Merged
merged 1 commit into from
Nov 3, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
---
title : "Taking responsibility for your software - How to simply monitor your solutions for known vulnerabiities and keep your customers informed"
track : Governance
project : Risk and Governance
type : working-session
topics :
featured :
event : mini-summit
when_year : 2024
when_month : Dec
when_day : Wed
when_time : WS-15-16
hey_summit :
session_slack:
#status : draft
description :
banner :
organizers :
- Jan Thielscher

youtube_link :
zoom_link :
---

## About this session
Today's software solutions comprise of many different artefacts: Open source, own code, configurations, 3rd party licensed or produced tools, etc. Your customers tend to expect you to keep them informed about any issues arising from known vulnerabilities. Upcoming legal frameworks such as the European Cyber Resilience Act will even enforce this trend.
It is essential to set up a solution allowing you to offer this information in an effortless and timely manner. This speech will introduce you to the challenges associated with this task and demonstrate how a solution might look like to cope with them.
Loading