BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//bsides-bristol-2026//talk//PLBDFK
BEGIN:VTIMEZONE
TZID:Europe/London
BEGIN:DAYLIGHT
DTSTART:20250822T000000
TZNAME:BST
TZOFFSETFROM:+0100
TZOFFSETTO:+0100
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20251026T020000
RDATE:20261025T020000
TZNAME:GMT
TZOFFSETFROM:+0100
TZOFFSETTO:+0000
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20260329T020000
RDATE:20270328T020000
TZNAME:BST
TZOFFSETFROM:+0000
TZOFFSETTO:+0100
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:We Didn't Have a Patch: How Defence in Depth Saved Our Customers f
 rom Log4Shell - Simon wilks
DTSTART;TZID=Europe/London:20260822T143000
DTEND;TZID=Europe/London:20260822T145000
DTSTAMP:20260812T231545Z
UID:pretalx-bsides-bristol-2026-PLBDFK@pretalx.com
DESCRIPTION:In December 2021\, we had the Log4J / Log4Shell Zero day\n\nTh
 is isn't a talk about Log4Shell itself. It's the story of how an customers
  application was initially compromised but protected from exploit success 
 before a patch was deployed\, not because we predicted the vulnerability\,
  but because years earlier we'd implemented a layered security approach ba
 sed on default-deny principles.\n\nThe technology has changed since 2021. 
 The principles haven't.
LOCATION:Rookie Track
URL:https://pretalx.com/bsides-bristol-2026/talk/PLBDFK/
END:VEVENT
END:VCALENDAR