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...
OneAgent in Infrastructure Monitoring mode automatically injects into processes to be able to monitor backing services written in Java and runtime metrics for supported languages. If the auto-injecti...
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...
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...
* 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 there's no information about the affected database on the details page of an attack by an SQL injection exploit type, the Java JDBC OneAgent feature is disabled.
Note: Be sure to check wit...
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...
