DependencyTrack / DependencyTrack/dependency-track
Policy violations only updated after BOM upload, not after VEX upload
- Dominant language
- Java
- Stars
- 4.2k
- Forks
- 811
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 237
Description
### Current Behavior
See: https://github.com/DependencyTrack/dependency-track/discussions/4992
It seems the policy violations are only updated if I upload a new SBOM after suppressing the findings
### Steps to Reproduce
1.Define a policy for severity
2. Upload a BOM with a component matched by policy
3. Suppress the security finding
4. Notice that the project still has a policy violation reported
5. Upload a BOM again (the same as in 2.)
6. Notice that the project has the policy violation reported
### Expected Behavior
Policy violations should be updated immediatelly after VEX upload/suppression
### Dependency-Track Version
4.13.1
### Dependency-Track Distribution
Container Image
### Database Server
PostgreSQL
### Database Server Version
_No response_
### Browser
N/A
### Checklist
- [x] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [x] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this defect was already reported
Contributor guide
Assessment
This issue has not been assessed yet.