Baseline requirements in Harness
pending feedback
W
Waterspout Antlion
Please provide an option to configure the Baseline so that it is set only on the first successful scan of the master/main branch. Currently, the Baseline is updated after every successful scan on master/main, which causes net new vulnerabilities to disappear from subsequent scans since the Baseline keeps shifting. As a result, builds are not being gated by new vulnerabilities, because each new successful scan resets the Baseline and removes the visibility of net new issues in following builds. This dynamic updating prevents us from blocking builds based on newly introduced vulnerabilities, which is a key requirement for our process.
Log In
Pritesh Chandaliya
pending feedback
There is way to set the baseline to a fixed value.
Please switch from regex to fixed value and select from the drop down. The drop down should show all the variants/branches scanned for that target.