jfrog / jfrog/jfrog-cli-security

jf docker scan: Provide an option to filter vulnerabilities by jfrog_research_severity

Open
#359 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature request
Dominant language
Go
Stars
13
Forks
50
Avg merge
3d 48m
Merged PRs (30d)
26

Description

Is your feature request related to a problem? Please describe.
While performing the scan of any docker (containers) image using Jfrog Xray, we currently don't have the option to filter vulnerabilities by JFrog Research Severity score (extended_information.jfrog_research_severity in the report)

Describe the solution you'd like to see
Command line option to option to filter vulnerabilities by JFrog Research Severity score. In case of the JFrog Research Severity score being absent, the default severity should be used as a fallback

jf docker scan <IMAGE:TAG> --min-jfrog-research-severity="HIGH,CRITICAL"

Describe alternatives you've considered
Currently it may be possible to use a manual post-filtering of the output using tools like jq

Additional context
It would be useful to have the same option in the Watches/Policies functionality - to be able to setup some policy based on the JFrog Research Severity score (with the same fallback mechanism)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the jf docker scan vulnerability-filtering entry point and how extended_information.jfrog_research_severity and severity are read from reports. Then inspect the Watches/Policies functionality to understand whether the same filtering is shared. Done means the CLI option applies the requested severity thresholds, falls back when the research score is absent, and the policy behavior is defined or implemented.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go
Domain
cli, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.