BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20241002T122438Z
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-MICROSOFT-CDO-TZID:13
BEGIN:STANDARD
DTSTART:20231105T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:STANDARD
DTSTART:20241103T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20240310T100000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:854574de-23d7-4565-b708-a399f3f7dee8
DTSTAMP:20241002T122438Z
SUMMARY:Threat Modeling @ W3C
DTSTART;TZID=America/Los_Angeles:20240925T144500
DTEND;TZID=America/Los_Angeles:20240925T154500
DESCRIPTION:https://www.w3.org/events/meetings/854574de-23d7-4565-b708-a399
 f3f7dee8/\n\nWhen a standard is written\, it's required to write Security 
 and Privacy Considerations and\, if the technology is particularly disrupt
 ive\, to sample the human rights impact.\nOne of the processes that can be
  used to get these considerations in a practical and structured way is to 
 use Threat Modeling\, a repeatable process with several techniques to unde
 rstand best what we're doing\, what can't go wrong\, and what we can do ab
 out it.\nIn this session\, we will explore how to initiate Threat Modeling
  from the early stages of a specification\, using practical examples. This
  approach ensures that everything is secure\, respects privacy\, and is pr
 operly documented.\n\nAgenda: https://docs.google.com/presentation/d/1zauM
 qnZ_e0U3JlNe3bCJacNh9h1VOkBX4_UynjqvQeg/edit#slide=id.g303b479e16d_0_15\n\
 nAgenda\n\n**Chairs:**\nSimone Onofri\n\n**Description:**\nWhen a standard
  is written\, it's required to write Security and Privacy Considerations a
 nd\, if the technology is particularly disruptive\, to sample the human ri
 ghts impact.\nOne of the processes that can be used to get these considera
 tions in a practical and structured way is to use Threat Modeling\, a repe
 atable process with several techniques to understand best what we're doing
 \, what can't go wrong\, and what we can do about it.\nIn this session\, w
 e will explore how to initiate Threat Modeling from the early stages of a 
 specification\, using practical examples. This approach ensures that every
 thing is secure\, respects privacy\, and is properly documented.\n\n**Goal
 (s):**\nSecure the standards\n\n\n\n**Materials:**\n- [minutes](https://ww
 w.w3.org/2024/09/25-threat-modeling-minutes.html)\n- [Session proposal on 
 GitHub](https://github.com/w3c/tpac2024-breakouts/issues/12)
STATUS:CONFIRMED
CREATED:20240916T214810Z
LAST-MODIFIED:20241002T122438Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:4 Concourse Level - Manhattan
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
END:VCALENDAR