Keynote: Window Snyder, Chief Software Security Officer, Intel in conversation with Jim Zemlin
Interviewat Open Source Summit North America 2018 · on Thursday, 2018-08-30· at 09:45· West Ballroom A/B·
summary
Open source code gets treated like any third‑party dependency: evaluate against requirements, isolate risky components via compartmentalization and isolation, and raise the minimum bar for professional development. Moving projects to higher‑level languages removes most memory‑corruption risk; deleting unused features cuts attack surface. Measure security tools by true positives (thousands of flags that yield one or two real issues is useless). Combine fuzzers, shared test suites and threat modeling at commit time to build layered defenses.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:00Security in open source
- 3:42Security in open source code
- 5:40Security in commercial code
- 7:53Hacking tactics
- 10:49Improving application security
- 14:18Security as a skill
- 17:55Shame
- 19:56Fear
- 24:11Advice
related talks
23mKeynote: Fireside Chat with Window Snyder & Katherine Druckman
11mKeynote: Securing Open Source
16mKeynote: There Is Just One Way to Do Open Source Security: Together
22mKeynote: Bringing Greater Trust and Security by Design to the Open Source Ecosys...
13mKeynote: Software Security: _You_ are the Calvary
15mKeynote: The Security Symphony
40mClosing Keynote: New Era of Software with modern Application Security
56mKeynote: AppSec: From Outsiders to Allies