BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DevOps.com - ECPv5.16.4//NONSGML v1.0//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:DevOps.com
X-ORIGINAL-URL:https://devops.com
X-WR-CALDESC:Events for DevOps.com
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20200308T070000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:20201101T060000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/New_York:20200603T130000
DTEND;TZID=America/New_York:20200603T140000
DTSTAMP:20260811T191326
CREATED:20200519T171316Z
LAST-MODIFIED:20200603T191314Z
UID:136139-1591189200-1591192800@devops.com
SUMMARY:Why Securing Server-Side JavaScript Source Code is So Hard & How-to Fix it
DESCRIPTION:JavaScript is arguably the most important modern programming language\, but despite its massive popularity\, it is inherently very difficult to secure. As a dynamically typed and interpreted programming language\, static analysis of JavaScript source code is very limited in how it can analyze data-flow. However\, code property graphs offer new ways to reconstruct data-flows in dynamic languages via detailed annotations.
URL:https://devops.com/webinars/why-securing-server-side-javascript-source-code-is-so-hard-how-to-fix-it/
LOCATION:Live Webinar\, Boca Raton\, FL\, United States
ATTACH;FMTTYPE=image/png:https://devops.com/wp-content/uploads/2020/05/Why-securing-server-side.png
ORGANIZER;CN="DevOps.com":MAILTO:webinars@devops.com
END:VEVENT
END:VCALENDAR