BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.com//fwd-cloudsec-2026//talk//AVWK8T
BEGIN:VTIMEZONE
TZID:PST
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T100000Z
TZNAME:PST
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:PST
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T110000Z
TZNAME:PDT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T030000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:PDT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-fwd-cloudsec-2026-AVWK8T@pretalx.com
DTSTART;TZID=PST:20260601T102000
DTEND;TZID=PST:20260601T104000
DESCRIPTION:Sending cloud security alerts at scale is an absolute minefield
 . False positives\, wrong attribution\, alert floods\, missing context\, s
 tale findings\, and unclear remediation expectations burn trust with the e
 ngineers who have to respond. The cloud makes it worse. Ownership is fragm
 ented across platform\, app\, and data teams\, resources are ephemeral\, a
 nd tools that work fine at small scale behave unpredictably in complex env
 ironments.\nThis talk shares lessons from a multi-year effort operationali
 zing alerting across AWS and GCP using native services and third party too
 ls. We'll cover the edge cases that break cloud security alerting at scale
  (attribution that spans multiple teams\, grouping alerts back to root cau
 se fixes\, tuning detection rules through feedback loops\, building except
 ion workflows that don't kill developer velocity) and the patterns we land
 ed on to fix them.
DTSTAMP:20260502T124033Z
LOCATION:Room 2
SUMMARY:Stop Training Engineers to Ignore You: Cloud Security Alerting at S
 cale - Paul Benoit
URL:https://pretalx.com/fwd-cloudsec-2026/talk/AVWK8T/
END:VEVENT
END:VCALENDAR