BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//hack-lu-2023//speaker//AJMN93
BEGIN:VTIMEZONE
TZID:Europe/Luxembourg
BEGIN:DAYLIGHT
DTSTART:20221019T000000
TZNAME:CEST
TZOFFSETFROM:+0200
TZOFFSETTO:+0200
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20221030T030000
RDATE:20231029T030000
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20230326T030000
RDATE:20240331T030000
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:Almost 2 years after log4j .. if your PSIRT has survived\, Are the
  Lessons learned or not learned  on security incident & vulnerability mana
 gement ? - FrederiqueD\, Thales
DTSTART;TZID=Europe/Luxembourg:20231019T093000
DTEND;TZID=Europe/Luxembourg:20231019T095500
DTSTAMP:20260808T184624Z
UID:pretalx-hack-lu-2023-USNSEZ@pretalx.com
DESCRIPTION:In Dec 2021\, the media and public discovered the “famous”
  log4j vulnerability.\nThey realized that for every product or website usi
 ng software  or  shared libraries and components \, these products can bec
 ome vulnerable to cyber attack.\n\nCompanies in technology sector producin
 g «software » had to face the same « disease  or scary movie ».  A 
 small library used everywhere has damaged almost all software  & websites.
  \n\nAt this time a part of companies believed they were prepared with a P
 SIRT or a CSIRT or a CERT\, the other part had to “improvise\, resolve a
 nd learn” \n\nToday’s   main « key » questions which seems of inte
 rest:\n\n* Do we all remember (good and bad parts of the experience) ?\n\n
 * Have we realized it’s a miracle the PSIRT teams survived the experienc
 e ?\n\n* Have we learned the lessons of what happened with log4j ? \n\n* A
 re we now  prepare when (‘and not if’) a new « vulnerability scary m
 ovie » will come back
LOCATION:Salle Europe
URL:https://pretalx.com/hack-lu-2023/talk/USNSEZ/
END:VEVENT
END:VCALENDAR