Suppress or Customize Vulnerability Identifiers at the group/subgroup level

Problem to solve

I received this inquiry from a SaaS, Ultimate customer who is interested in a feature to suppress specific identifiers on a group/sub-group? Or how can we tune the alerts better? They want to set the level of the alert to prioritize specific vulnerabilities - Eg. there is a slack webhook secrets alert: can we make this a 'high' instead of a 'critical' to better prioritize other secrets? Another example: e.g. below TF rule - this is not even best practice and this rule should be removed completely.

Proposal

Two parts:

1. Ability to tune identifiers/rules at group/sub-group level
2. deleting irrelevant vulnerabilities/rules completely for everyone

Allow customers to tune the vulnerability alerts at the group level based on the prioritization of the specific customer. If a vulnerability is considered 'critical' by GitLab, but the customer is not truly impacted by the vulnerability, they should be able to adjust the identifier level for that specific vulnerability to a more relevant identifier ie. 'low', and not receive an alert. Also, the ability to delete rules that are not relevant to the customers use case.

This ideally would be set at the group/subgroup level to apply these changes in bulk.

Intended users

• Amy (Application Security Engineer)
• Isaac (Infrastructure Engineer)
• Alex (Security Operations Engineer)
• Cameron (Compliance Manager)

-->

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.