Many tools stop when a patch or pull request exists. VulnTrek tracks each exposure from the scanner finding to a closed record: a named owner, a real ticket, a human approval, a fresh re-scan and a closure an auditor can follow.
Results from your existing scanners are merged at intake, so the same issue on the same asset is tracked once.
Every finding is assigned to a person, so nothing waits in a shared queue.
The finding is raised in your own ticketing system, such as Jira, and the ticket number and link stay attached to it.
Suggested fixes and scans need an approval from an owner or admin. Nothing is changed automatically.
After the fix is merged, a new scan confirms the issue is gone. Simulated or test runs are labelled as such and never count as verified.
The owner confirms closure with the pull request and re-scan attached. The closing date is recorded and the record cannot be edited afterwards.
VulnTrek does not replace your scanners or your ticketing system, and it does not close findings by itself. A person always confirms closure.