Wednesday Jan 19th 5PM ET Meetup w/ Vickie Li
9 views
Skip to first unread message
OWASP Boston Chapter
Jan 18, 2022, 9:52:36 PM1/18/22
to OWASP Boston Chapter
This month OWASP Boston will be welcoming Vickie Li. Vickie is a Developer Evangelist at ShiftLeft and author of No Starch Press' Bug Bounty Bootcamp. Vickie will be providing a workshop style take on source code analysis.
Signup at https://www.meetup.com/owaspboston/events/283239683/
Analyzing source code for vulnerabilities: A how-to workshop
Writing code is hard. Writing secure code is even harder. Serious security vulnerabilities often stem from small programming mistakes. As developers, we can safeguard our applications by catching these mistakes in our own code.
Performing a source code review is one of the best ways to find security issues in code. But how do you do it? In this workshop, we will first go through the basics of how to review your code for vulnerabilities and some tactics for performing an effective security code review on your application.
But the process of manually analyzing code for vulnerabilities can be very time-consuming. In the second part of this talk, we will also talk about how to use the interactive code analysis tool Joern to make code analysis more efficient.
Analyzing source code for vulnerabilities: A how-to workshop
Writing code is hard. Writing secure code is even harder. Serious security vulnerabilities often stem from small programming mistakes. As developers, we can safeguard our applications by catching these mistakes in our own code.
Performing a source code review is one of the best ways to find security issues in code. But how do you do it? In this workshop, we will first go through the basics of how to review your code for vulnerabilities and some tactics for performing an effective security code review on your application.
But the process of manually analyzing code for vulnerabilities can be very time-consuming. In the second part of this talk, we will also talk about how to use the interactive code analysis tool Joern to make code analysis more efficient.
How do you effectively trace user input in code?
How can you efficiently link bug sources to sensitive sink functions?
Reply all
Reply to author
Forward
0 new messages