Dynatrace Runtime Vulnerability Analytics enables you to detect, visualize, analyze, monitor, and remediate open-source and third-party vulnerabilities, as well as the security vulnerabilities in libraries and first-party code in production and pre-production environments at runtime.
Runtime Vulnerability Analytics (RVA) detects and evaluates vulnerabilities in your environment based on what's actually running, not just what's deployed. Dynatrace OneAgent monitors loaded libraries, runtime components, and data flows in real time. Vulnerabilities are only reported when affected components are actively used, reducing noise and false positives.
For third-party vulnerabilities, Dynatrace:
Detects libraries and runtime components as they are loaded by processes.
Matches component names and versions against trusted vulnerability feeds.
Issues a vulnerability only when the component is in use.
For code-level vulnerabilities, Dynatrace:
Analyzes how user input flows through the application.
Identifies insecure code paths that could be exploited.
Assesses risk based on exposure to the public internet and access to sensitive data assets.
Vulnerabilities are automatically resolved when the root cause is no longer present; for example, if a vulnerable library is removed or a process is stopped. RVA continuously adapts to topology changes and dynamic environments.
For technical details, see Vulnerability evaluation. For a quick walkthrough, see Discover the new Dynatrace Runtime Vulnerability Analytics experience.
Before you begin, ensure your environment meets the necessary requirements:
You're using a supported version of Dynatrace. Review the release notes for currently supported versions.
For Runtime Vulnerability Analytics to work properly, make sure deep monitoring is enabled in Settings > Process and contextualize > Process groups > Process group monitoring.
For .NET, Go, and Python technologies, for which automatic deep monitoring is disabled, you need to manually enable deep monitoring on each host. For more information, see Process deep monitoring.
Dynatrace detects third-party vulnerabilities in the following technologies.
| Technology | Minimum OneAgent version |
|---|---|
| Go1 | 1.245 |
| Java2 | 1.221 |
| Java runtimes | 1.253 |
| Kubernetes | 1.219 |
| .NET1 | 1.233 |
| .NET runtimes | 1.255 |
| Node.js3 | 1.231 |
| Node.js runtimes | 1.253 |
| PHP | 1.231 |
| Python1'4 | 1.309 |
| Python runtimes | 1.309 |
For .NET, Go, and Python technologies, for which automatic deep monitoring is disabled, you need to manually enable deep monitoring on each host. For more information, see Process deep monitoring.
Java on z/OS is currently not supported.
Using Webpack or other bundlers might have an impact on automatic vulnerability detection. This is because the software components cannot be detected, as they are hidden behind the bundler configuration and not available at runtime. Only packages that are deployed as external packages can be detected and reported. For details, see Node.js: Limitations.
For Python vulnerabilities, Dynatrace currently supports only two states for reachable data assets: Within range and Not available.
Third-party vulnerability detection helps you identify open-source and third-party vulnerabilities in production and pre-production environments at runtime. To monitor third-party vulnerabilities, enable third-party vulnerability detection.
Code-level vulnerability detection leverages code inspection at runtime to identify vulnerabilities in libraries and first-party code. To monitor code-level vulnerabilities, enable code-level vulnerability detection.
OneAgent version 1.239+
Go to Settings > Analyze and alert > Application security > General settings > Third-party Vulnerability Analytics and select Enable Third-party Vulnerability Analytics.
To define the default third-party vulnerability detection control for all processes and Kubernetes nodes
Go to Settings > Analyze and alert > Application security > General settings > Third-party vulnerability Analytics and select one of the Global third-party vulnerability detection control modes:
You can also define custom monitoring rules based on certain criteria. In this case, the default monitoring mode applies to all processes and Kubernetes nodes that are not matched by a rule.
Optional
After you enable Third-party Vulnerability Analytics, Dynatrace starts generating vulnerabilities for all supported technologies by default. To control which of these technologies should receive vulnerabilities
Go to Settings > Analyze and alert > Application security > General settings > Third-party Vulnerability Analytics and enable or disable technologies as needed.
Runtime technologies (for example, Java, Node.js, and .NET runtimes) are tied to the corresponding main technology (for example, Java and Node.js). If the main technology is disabled, the corresponding runtime technology is automatically disabled. If you enable the main technology, enabling the corresponding runtime technology is optional.
Select Save changes.
This step is required only to monitor vulnerabilities in Python technology.
Optional
To enable OneAgent monitoring for Java vulnerable functions
For more information about function usage, see Vulnerable functions.
After you enable third-party and code-level vulnerability detection, you can
Vulnerabilities.For details on how Dynatrace evaluates third-party and code-level vulnerabilities, see Vulnerability evaluation.
Runtime Vulnerability Analytics consumption depends on your Dynatrace licensing model:
Dynatrace Platform Subscription (DPS): measured in GiB‑hours. For details, see Calculate your consumption of Runtime Vulnerability Analytics (RVA) (DPS).
Dynatrace classic licensing: measured in Application Security units (ASUs). For details, see Application Security monitoring (ASUs).