|
407 | 407 | <artifactId>dependency-check-maven</artifactId> |
408 | 408 | <version>${owasp.dependency-check.version}</version> |
409 | 409 | <configuration> |
410 | | - <!-- Fail build on High/Critical CVEs (CVSS >= 7) per security.md --> |
| 410 | + <!-- Hard gate: build fails on High/Critical CVEs (CVSS >= 7) |
| 411 | + per security.md AND on operational failures of the |
| 412 | + scanner itself. failOnError stays at the default (true) |
| 413 | + so a silent NVD-feed degradation does NOT pass as a |
| 414 | + green build (Reviewer round-3 finding #1). --> |
411 | 415 | <failBuildOnCVSS>7</failBuildOnCVSS> |
412 | | - <!-- Do NOT fail the build on NVD-feed download/connection |
413 | | - hiccups (the upstream NVD API is rate-limited and |
414 | | - occasionally returns 5xx, which would otherwise red-X |
415 | | - every PR). The gate still fails on real CVE findings |
416 | | - via failBuildOnCVSS above; transient NVD outages just |
417 | | - skip the analysis for that run. |
418 | | - RAN-42 tracks making the gate fully robust (NVD API |
419 | | - key, cached data, etc.); this is the minimal compromise |
420 | | - to satisfy RAN-46 AC #5 without breaking PRs. --> |
421 | | - <failOnError>false</failOnError> |
| 416 | + <!-- Stable on-disk cache directory. ci-java.yml caches |
| 417 | + this path between runs (actions/cache), which is the |
| 418 | + primary mitigation for transient NVD-feed/H2 issues: |
| 419 | + after the first successful run on a fresh runner, the |
| 420 | + cache holds a pre-populated H2 DB and incremental |
| 421 | + updates are short. --> |
| 422 | + <dataDirectory>${user.home}/.m2/repository/org/owasp/dependency-check-data</dataDirectory> |
| 423 | + <!-- Use NVD_API_KEY when available (drastically reduces |
| 424 | + throttle / 5xx rates from the NVD API). The build |
| 425 | + falls back to the unauthenticated path when the |
| 426 | + secret is unset; that path is rate-limited but works |
| 427 | + once the cache is warm. RAN-42 tracks the secret |
| 428 | + provisioning + a dedicated nightly NVD-refresh job. --> |
| 429 | + <nvdApiKey>${env.NVD_API_KEY}</nvdApiKey> |
422 | 430 | </configuration> |
423 | 431 | <executions> |
424 | 432 | <!-- Bind dependency-check:check into the verify phase so |
|
0 commit comments