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
To help identify and eliminate unintentional vulnerabilities in generated test suites, we can add a debug feature that detects vulnerabilities found in the test suite by tools outside of the intentional vulnerabilities. I can envision two modes during scorecard generation:
Normal Debug: Generate a list of CWEs in the current expected results file, and then for each tool, each time a CWE in that list is identified outside of an expected test case for that CWE, dump out the CWE, and location found.
This is the most useful as it eliminates extraneous vulns of the type we actually count so tools don't 'strangely' find more vulns of a given type than expected.
Go Hard Debug: Report ANY CWEs outside of expected locations. Some tools find all kinds of extraneous stuff, so eliminate any findings mapped to 0 or -1. We might have to tune other parsers to map more extraneous findings to 0/-1, or add a filter her to eliminate CWEs we just don't care about.
This would all be done in BenchmarkScore, so would work across ALL the tools.
The text was updated successfully, but these errors were encountered:
To help identify and eliminate unintentional vulnerabilities in generated test suites, we can add a debug feature that detects vulnerabilities found in the test suite by tools outside of the intentional vulnerabilities. I can envision two modes during scorecard generation:
This is the most useful as it eliminates extraneous vulns of the type we actually count so tools don't 'strangely' find more vulns of a given type than expected.
This would all be done in BenchmarkScore, so would work across ALL the tools.
The text was updated successfully, but these errors were encountered: