Close gap: configuration and usage of third party security training

What does this MR do and why?

In the GitLab documentation is no comprehensive guide about the requirements for or how to configure and use the security training for vulnerabilities. The only mention is how to enable this here. We do not tell our customers what they would need to do after, how it would look or if this is an inclusive offer from GitLab.

I do think we need to define the minimum we need in our documentation regarding this external training:

• Liability Disclaimer
• Requirements to enable this fully
• What data is transported about the vuln to the outside
• Find Sales stable counterpart for customers to approach on this

Initially discovered in Access Request

Information from other Sources

• Blog Post: How to get integrated secure coding advice in GitLab
  • MR: Create Blog Posts “2022-03-23-here’s-how-to-get-integrated-secure-coding-advice-in-gitlab”
• Blog Post: Kontra and GitLab integrate vulnerability education into the DevOps workflow
  • MR: https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/101550
• GitLab Partner Page: Security
• Secure Code Warrior Page: GitLab Integration
• Secure Code Warrior Page: GitLab Partner Page
• Kontra Page: KONTRA & GitLab: Integrating Security Education Into The Developers’ Workflow

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.