You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user of Build Harness that works in a secure environment, I want BH to have fewer vulnerabilities than it has now, so that my environment may be more secure.
As a user of Build Harness that works in a regulated environment, I want vulnerability scanners like Grype to report that Build Harness has fewer CVEs than it does now, so that I can use it without having to justify so many vulnerabilities in my compliance paperwork.
The content you are editing has changed. Please copy your edits and refresh the page.
A recent scan of Build Harness showed 1 critical, 65 high, 249 medium, and 160 low CVEs
A likely avenue for being able to do this without making big sweeping changes is to evaluate whether there are any tools that are reporting CVEs that are not absolutely required and can be subject to removal from the image.
The text was updated successfully, but these errors were encountered:
As a user of Build Harness that works in a secure environment, I want BH to have fewer vulnerabilities than it has now, so that my environment may be more secure.
As a user of Build Harness that works in a regulated environment, I want vulnerability scanners like Grype to report that Build Harness has fewer CVEs than it does now, so that I can use it without having to justify so many vulnerabilities in my compliance paperwork.
Acceptance Criteria
Notes:
The text was updated successfully, but these errors were encountered: