CI Fuzz Coffee Hour

Hello security fans and community,
it's been a while since we last met! And we would like to change this!
We are starting off a series of initiatives with a cool format to provide the possibility for connecting, engaging, sharing knowledge and getting together more regularly to talk about all things security and fuzzing.

So - what to expect?
Every last Wednesday of the month, we will welcome you for a digital coffee hour together with our awesome developer advocate Josh Grant to discuss topics like security, testing and fuzzing, sharing tips and tricks on how to accomplish everyday (or allday) challenges, getting hands on experience and also opening the floor for your questions.

To make this format valuable and engaging we will prepare a focus topic for the first 15-30 minutes with hands-on demos, awesome experts and of course insights on what's going on in the world of fuzzing.

Afterwards, the floor is open for your questions, discussions, and comments.

This Week
Join me, Josh Grant, to discuss how to secure your code as a JavaScript developer.

Writing code can be difficult enough, but what about making that code secure?

In the JavaScript world, a hot topic is application security, or AppSec for short. This kind of security means thinking about how to make code as secure as possible. AppSec means thinking of the security of code that you wrote,by yourself or someone on your team, and the code that you didn’t write, such as third-party libraries or packages added via a source code registry.. For code you didn’t write, there are common tools such as npm’s audit functionality and services like Dependabot. For code you did write, there are approaches such as linting and code coverage tools and dynamic application testing approaches like fuzzing.

In this coffee hour, we’ll discuss how to secure code you wrote and code you didn’t write and some tools and approaches for securing your JavaScript code from the comfort of your developer workstation. In addition to discussing general AppSec techniques for JavaScript developers, we will walk through some examples of security vulnerabilities in JavaScript projects, and how to use tools to find these vulnerabilities.

Agenda
(all times Central European Time CET)

4 PM - 4:05 PM: Welcome and overview of the day’s coffee hour.
4:05 PM - 4:15 PM: As a JavaScript developer, how can I make my code more secure?
4:15 PM - 4:35 PM: AppSec for JavaScript
4:35 PM and on: Discussion, Questions and Closing