Blog: why you need a security champions program - 10/14

From Commit, a deep dive into stats around the dev/sec divide.

https://www.youtube.com/watch?v=yX-uEkdpw2w&list=PLFGfElNsQthbJaOG4pV450Y_eIdfr2p9Y&index=6

Transcript: https://www.rev.com/transcript-editor/Edit?token=jXa47PGWwZOkK5TLva0A9B0F2y9LSg9jqJXzS_CwsG9IDVvxGIW6ZTY_GqDwZhqlnDuoexj7fEY_y3dZ79k9oxlOlfQ&loadFrom=MyFiles&openShareModal=False&page=1&sortBy=Uploaded&sortOrder=Desc&pageSize=25

Checklist

• If you have a specific publish date in mind (please allow 3 weeks' lead time)
  • Include it in the issue title
  • Give the issue a due date of a minimum of 2 working days prior
  • If your post is likely to be >2,000 words, give a due date of a minimum of 4 working days prior
• If time sensitive
  • Add ~"Blog: Priority" label and supplied rationale in description
  • Mention @rebecca to give her a heads up ASAP
• If wide-spread customer impacting or sensitive, mention @nwoods to give her a heads up ASAP, apply the sensitive label, and check the PR handbook in case you need to open an announcement request instead of a blog post issue
• If the post is about one of GitLab's Technology Partners, including integration partners, mention @TinaS, apply the Partner Marketing label, and see the blog handbook for more on third-party posts
• If the post is about one of GitLab's customers, mention @KimLock and @FionaOKeeffe, apply the Customer Reference Program label, and see the blog handbook for more on third-party posts
• Indicate if supporting an event or campaign
• Indicate if this post requires additional approval from internal or external parties before publishing (please provide details in a comment)