Add Vulnerability Research group in Secure
Problem to solve
The product categories page does not reflect the current organization and responsibilities of the Secure stage since the Vulnerability Research team moved to Secure. We need to explicit the role of the Vulnerability Research team from a product perspective.
Proposal
This MR adds a new Group within the Secure stage and moves the Vulnerability Database
category to this new group.
This allows to have a group::vulnerability research
label to properly organize and track the work of this independent team.
This will also reflect the fact that the Vulnerability Database
category is no longer under the Composition Analysis group responsibilities. This category is still marketing:false
to follow the categories guideline:
There is a maximum of 8 high-level categories per stage to ensure we can display this on our website and pitch deck. (Categories that do not show up on marketing pages show up here in italics and do not count toward this limit.)
Preview:
- product categories page: https://add-vulnerability-research-group-in-secure.about.gitlab-review.app/handbook/product/categories/#vulnerability-research-group
- secure handbook page: https://add-vulnerability-research-group-in-secure.about.gitlab-review.app/handbook/engineering/development/secure/#vulnerability-research
Approvals:
-
VP of Product @sfwgitlab -
VP of Product Strategy @markpundsack -
The Product Director relevant to the stage group(s) @ddesanto -
The Engineering Director relevant to the stage group(s) @tstadelhofer -
CEO @sytses