Filter third-party vulnerabilities
Once you enable Application Security and you see the list of third-party vulnerabilities appear on the Third-party vulnerabilities page, there are several ways you can organize them for easy management and to prioritize problems:
- You can filter vulnerabilities by vulnerability details, global timeframe, and management zone. You can combine any of these filters.
- You can mute (silence) vulnerabilities that you don't consider important.
- You can filter vulnerabilities by recommended fixes.
See below for details.
Filter by vulnerability details
The following filters are available:
Public internet exposure,
Sensitive data affected,
Public exploit available,
Vulnerable functions in use
Snyk/CVE ID: If you filter by the Snyk ID or CVE ID, it must be a perfect match
Vulnerable component: Part of the vulnerable component name
Vulnerability ID: Select a vulnerability based on the 'S' string that represents its ID
Affected or related entity: Select and enter any combination of the following:
Process group name,
Kubernetes workload name,
Kubernetes cluster name,
- You can't add an entity more than once.
Tag, you can use tags on a host, process group, and process group instance, with the syntax
key. For more information about tagging, see Define and apply tags.
- If a security problem affects more than 5,000 processes, the Affected or related entity filter may not be able to find all security problems impacted by the entered entity.
Filter by global timeframe
You can use the global timeframe selector to filter third-party vulnerabilities on the following pages:
On the Third-party vulnerabilities page, it displays vulnerabilities that were open within the selected global timeframe. However, the data displayed about an entry reflects the current state of the entry, not the historical state.
On the vulnerability details page, it displays entities that were affected and libraries that were vulnerable during the selected global timeframe. An affected entity or a vulnerable component is shown:
- If it was already affected or vulnerable during the selected timeframe
- If it's still affected or vulnerable
Filter by management zone
You can use the management zones filter on the following pages. Note that for each case, the filter applies to different components:
- On the Third-party vulnerabilities page, filtering by management zone applies to third-party vulnerabilities. The management zone filter doesn't affect the other vulnerability fields, such as Public internet exposure or Sensitive data affected; other than Vulnerability, all values on this page are based on the whole environment.
- On the vulnerability details page, filtering by management zone applies to vulnerable components and affected entities (processes, process groups, hosts, services, etc.). The management zone filter doesn't affect the majority of data on the infographic; other than Affected entities, all values on this page are based on the whole environment.
- When a vulnerability stops affecting a management zone, it won't show up when you filter for that management zone.
- When a vulnerability is resolved (when it has stopped affecting the whole environment), it shows up regardless of the selected management zone.
For more information on how to set up and apply management zones, and about the rules that define and limit the entities that can be accessed within a management zone, see Management zones.
Management zone calculation is based on processes (process group instances). Management zones are calculated when a vulnerability is opened and every 15 minutes after that until the vulnerability is resolved. A management zone is affected by a vulnerability if a process (process group instance) of the management zone uses a software component that has the reported vulnerability.
If you determine that a vulnerability isn't serious and you want to filter it out from the list of third-party vulnerabilities, you can mute (silence) it. Dynatrace analyzes muted vulnerabilities periodically, but you can filter them out by
To mute a vulnerability
- Go to the details page of the vulnerability and select Mute problem in the upper-right corner.
- Select a reason for muting the vulnerability and, optionally, provide additional information.
- Select Save.
Note: You need to wait up to a minute for the change to take effect. Refresh the page to see your change.
Muted problems don't appear on the list of vulnerabilities unless you filter for them.
The status change of the vulnerability is logged under the Problem evolution section of the vulnerability details page. Select Details to see who muted the vulnerability, the reason for muting, and any additional comments. Note that Problem evolution shows only the last five events that occurred within the last 30 days.
You can unmute a vulnerability by selecting Unmute problem on the details page of the respective vulnerability. Unmuting a vulnerability makes it active again—its status changes back to
Note: You won't be able to mute/unmute a vulnerability if
- Muting/unmuting is already in progress
- Required permissions are missing
- The vulnerability status is
- The vulnerability status is
Muted - Resolved
Hover over Mute problem/Unmute problem to see why muting/unmuting isn't possible.
Filter by recommended fixes with Davis Security Advisor
To filter by recommended fixes, on the Third-party vulnerabilities page, select an upgrade and then select Add as filter.
- After adding a recommended fix as a filter, you can extend filtering by vulnerability details.
- You can add multiple filters for recommended fixes all at once. In this case, you will get a cumulated list of vulnerabilities based on the selected fixes.
- If you use the management zones filter, you'll get a list of third-party vulnerabilities that affect the selected management zone.
Note: You won't receive recommendations for
- Muted vulnerabilities
- Vulnerabilities filtered by the global filter in a past timeframe
- Resolved vulnerabilities
For more information about Davis Security Advisor, see Davis Security Advisor calculations.