<img src="https://certify.alexametrics.com/atrk.gif?account=Zpb+p1uhUo20dG" style="display:none" height="1" width="1" alt="">
Git-based Security Workflows for Developers


Think About Your Audience Before Choosing a Webinar Title

Sponsored by shiftleft

Thursday, August 13, 2020
1 pm EDT


The future of application security must be developer-centric. 

The modern incarnation of application security tools like SAST, DAST and WAF came about nearly 20 years ago. In the early 2000s software development was very different. The software development lifecycle was defined by waterfall development models, physical servers and monolithic code bases managed by SVN-based repositories. In that era, security tools were designed with AppSec Teams as the primary users and they were run as one of the final confirmation steps in the waterfall release model.  

Today development is fast and cloud-based, with microservices architectures and Git-based repositories. However, application security workflows haven’t evolved in meaningful ways. Git is the center of modern software development and re-thinking security workflows for Developers should naturally be Git-based. 

Putting the needs of developers first should be the key design principle of Git-based security workflows and maximizing developer productivity should be the goal. Yet in doing so, AppSec must still be able to create, manage and enforce organizational security standards. 

This webinar will cover:

  • Why the future of application security must be developer-centric
  • Key design goals and requirements for creating Git-based security workflows
  • Key technology goals and requirements for creating such workflows
  • A Real-world example implementation & results  
Arun Balakrishnan
Director of Product Management - ShiftLeft

Director of Product Management - ShiftLeft

Andrew Fife
Head of Marketing - ShiftLeft
Head of Marketing - ShiftLeft

On-Demand Viewing:

What You’ll Learn in This Webinar

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:

  • You know you’ve cringed at misspellings and improper grammar before, so don’t get caught making the same mistake.
  • Get a second or even third set of eyes to review your work.
  • It reflects on your professionalism even if it has nothing to do with your event.