While the general view from the outside is that security just sort of happens, it's hard to see what goes into the day-to-day of releasing new products. How do large companies decide that something is (or isn't secure), how do they fix bugs before launch and how do they receive bugs afterward?
This talk will take an overview of what security review/auditing looks like and how Vulnerability reward programs operate and compliment this. It will be held by Paul Devitt, working at the Product Security team and Vulnerability rewards program at Google.
Slides: https://docs.google.com/presentation/d/1oC8JqyTMRG15C-E1qTUxcxMw7Ra4diWXVtl2iXv7g1c/edit?usp=sharing
Information Security Engineer
I've been at Google for 10 years, starting in Australia as internal technical support, making my way through Google Fiber, Alphabet companies, and finally with the Product Security team and Vulnerability rewards program. I studied Philosophy at University and haven't worked at a Mcdonald's yet but there is still time and hope.
GDSC Munich Lead
GDSC Munich Lead
GDSC Munich Core Team
GDSC Munich Core Team
GDSC Munich Advisor
GDSC Munich Advisor
GDSC Munich Core Team
GDSC Munich Core Team
Technical University of Munich
GDSC Munich Core Member
GDSC Munich Core Member
TUM
GDSC Munich Core Team
GDSC Munich Core Team
