Skip to content

Feature: Segregate HIGH and CRITICAL CVEs in Image Scanning via Trivy  #4166

Open
@tayalrishabh96

Description

@tayalrishabh96

🔖 Feature description

As of now Devtron is clubbing HIGH and CRITICAL CVEs into CRITICAL CVEs only. This is hampering blocking of deployments if CVE is actually CRITICAL and not HIGH.

🎤 Pitch

In my use-case I only want to block deployments if CVE is CRITICAL and not in case CVE is categorized as HIGH. But since Devtron is clubbing HIGH and CRITICAL into CRITICAL it is becoming difficult to address the use-case.

✌️ Solution

Either clubbing HIGH CVEs with MEDIUM or creating 4 separating categories should fix.

🔄️ Alternative

NA

👀 Have you spent some time to check if this issue has been raised before?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

AB#6473

Metadata

Metadata

Labels

ICA-AUG24Issue Cleanup Activity Aug 2024criticalUsed for prioritising issuesenhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions