Sponsored by CYCODE
GitHub Actions is an increasingly popular DevOps tool because of its rich marketplace and ease of use. As part of our research into the GitHub Actions security landscape, we discovered several pitfalls in the workflow that could result in severe security consequences. For example, we noticed many developers using event input data to improve their workflow process. In theory, this helps to streamline and simplify the workflow; in practice, however, this data could be controlled by an attacker and potentially compromise the build process. Unless developers deeply understand GitHub best practices, these workflows are likely to have mistakes that are costly and could create supply chain risk to the application.
In this webinar, we'll discuss how we found and disclosed vulnerable workflows in several popular open source tools, delve into GitHub Actions architecture to understand the possible consequences of these vulnerabilities, and present possible mitigations for these issues.
You’ve probably written a hundred abstracts in your day, but have you come up with a template that really seems to resonate? Go back through your past webinar inventory and see what events produced the most registrants. Sure – this will vary by topic but what got their attention initially was the description you wrote.
Paint a mental image of the benefits of attending your webinar. Often times this can be summarized in the title of your event. Your prospects may not even make it to the body of the message, so get your point across immediately. Capture their attention, pique their interest, and push them towards the desired action (i.e. signing up for your event). You have to make them focus and you have to do it fast. Using an active voice and bullet points is great way to do this.
Always add key takeaways. Something like this....In this session, you’ll learn about: