BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.securitybsides.org.uk//bsides-london-2024//talk//83Q
 AGY
BEGIN:VTIMEZONE
TZID:GMT
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:GMT
TZOFFSETFROM:+0100
TZOFFSETTO:+0000
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:BST
TZOFFSETFROM:+0000
TZOFFSETTO:+0100
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-bsides-london-2024-83QAGY@cfp.securitybsides.org.uk
DTSTART;TZID=GMT:20241214T160000
DTEND;TZID=GMT:20241214T161500
DESCRIPTION:We've been in the wrong place at the right time between us for 
 between 30-40 years\, in just about every sector imaginable. \n\nWe're see
 ing both mid-sized organisations and enterprises in the situation where th
 ey have all the consultancy recommendations - Managed Security Service Pro
 vider\, Endpoint Detection And Response\, Network Detection & Response\, e
 xtended Detection & Response\, Managed Detection & Response\, but IR still
  isn't solved. \n\nThere's  frustration from both the MSSPs and Detection 
 & Response providers\, and from customers.\nThis talk explores:\nThe diffe
 rence between Incident Management and Incident Response\nThe history of ho
 w people get into Security\, and Incident Response\nEnterprise Architectur
 e View of these\nThe changes that have introduced a wicked problem: \n  No
 n-Technical or Non-Security Incident Managers attempting Incident Response
 \n  Technical Incident Responders attempting IR without the business link 
 of Incident management\nThe frustrations from MSSPs and Detection & Respon
 se Providers\nCustomer Frustrations\nPotential ways of solving this within
  the security community
DTSTAMP:20260609T050102Z
LOCATION:Rookie track 2
SUMMARY:MSSP\, MDR\, MFA - So Why isn't Incident Response Solved? - Tim Hay
 nes
URL:https://cfp.securitybsides.org.uk/bsides-london-2024/talk/83QAGY/
END:VEVENT
END:VCALENDAR