topic Re: Filtering vulnerabilties in the new application in Open Q&A

Filtering vulnerabilties in the new application

gschramm — Tue, 13 Jan 2026 09:24:58 GMT

Hi,

in the classic "third-party vulnerabilties" app the findings could be filtered by management zone. The new "vulnerabilities" app does not have that filter, there is only an experimental option to filter via segements

All other new applications make use of the dt.security.context, however the new vulnerabilties app doesn't seem take this into account.

Am I overlooking something or is really not possible to just show findings for a specific application / management zone /security context?

Re: Filtering vulnerabilties in the new application

Julius_Loman — Tue, 13 Jan 2026 09:45:45 GMT

@gschramm Segments have to be used. See https://docs.dynatrace.com/docs/shortlink/vulnerabilities-upgrade-classic-to-latest#management-zones

Re: Filtering vulnerabilties in the new application

gschramm — Tue, 13 Jan 2026 11:17:00 GMT

Thanks, I find this very confusing. All other apps use the dt.security_context for permission and allow the use of segements for further slicing & dicing.

However the vulnerabilty app ignores the dt.security_context and requires segements for slicing the data..

This is confusing and disappointing.

to use making use of segementsdt.security.context, just this one now requires segements.. yet another configuration to handle

Re: Filtering vulnerabilties in the new application

Julius_Loman — Tue, 13 Jan 2026 12:29:31 GMT

@gschramm you can create segments based on the dt.security_context value. By utilizing variables in segments, you can define just one segment with parameters.