This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
(Latest Dynatrace)
A spinning radar on top of the DevSecOps Lifecycle Coverage with Snyk pages lets you know that
Application Security is actively monitoring the coverage status o...
If a vulnerability keeps being resolved and reopened, even if the third-party application containing the vulnerability has been upgraded, it might be that a process is still using that vulnerable lib...
Different number of affected entities
The number of affected entities (process groups or hosts) on the Third-party vulnerabilities page (in the Affected entities column for a sp...
See below for potential reasons why the monitoring status radar on Application Security pages shows Monitoring stopped. Please check settings on any of the pages below.
Monitoring stoppe...
When the feed import isn't working:
If the vulnerability feed hasn't been imported, Runtime Vulnerability Analytics cannot detect any third-party vulnerabilities.
If the vulnerability f...
* If the Application Security overview, Third-party vulnerabilities, and Code-level vulnerabilities pages don't display any data, Application Security is activated but not enabled...
If, on the details page of a third-party vulnerability, data for public internet exposure and reachable data assets isn't available, this happens because one or more related hosts are running in Infr...
A vulnerability might be identified incorrectly. Possible reasons for false positives include:
The extracted information from the software component isn't correct and a wrong library was identi...
All vulnerabilities on the Vulnerabilities page appear as closed when no software components are reported. Make sure that the necessary OneAgent features have been confirmed.
To confirm t...
