# Transition from Classic to New Application Security monitoring rules

**URL:** <https://community.dynatrace.com/t/transition-from-classic-to-new-application-security-monitoring-rules/51839>\
**Category:** Dynatrace Tips\
**Tags:** application-security, tips-and-tricks\
**Created:** [May 27, 2025, 2:08pm UTC](https://community.dynatrace.com/t/transition-from-classic-to-new-application-security-monitoring-rules/51839 "2025-05-27T14:08:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dburgstaller](https://avatars.discourse-cdn.com/v4/letter/d/5fc32e/32.png) [@dburgstaller](https://community.dynatrace.com/u/dburgstaller)\
**Post date:** [May 27, 2025, 2:08pm UTC](https://community.dynatrace.com/t/transition-from-classic-to-new-application-security-monitoring-rules/51839/1 "2025-05-27T14:08:10Z")

</div>

**Glossary**

Resource attribute = a key-value-pair that is sent by the Dynatrace OneAgent that is easily customisable by the customer. ([Resource attributes - Dynatrace Docs](https://docs.dynatrace.com/docs/discover-dynatrace/platform/oneagent/resourcel-attributes) )

K8s labels = Labels that are set on various Kubernetes resources when managing the Kubernetes environment ([Labels and Selectors](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/) )

**Tips for engaging with the New rules**

We suggest creating the new rules **first** and verifying with the per-rule preview to make sure the desired entities are matched.

After you’re satisfied with the rules, you can flip the toggle called _Enable new monitoring rules_ in _Settings app \> Application security \> General settings._

Every rule can consist of multiple conditions that are linked by a logical AND operator.

**ℹPlease be mindful when switching the monitoring rules, as switching from Classic to New monitoring rules has an impact on the&nbsp;entities that you monitor.**

**The problem**

In classic Dynatrace, you could define rules for Third-party vulnerabilities based on management zones, host tags, and process tags.

This approach had some inconveniences:

- Time delay when adding new entities to a management zone.
- The necessity to understand various Dynatrace concepts (like “management zones” and “tags”) to create rules based on them.
- A lot of complexity and a lack of transparency on what will be monitored.
- One ruleset targeting different entity types, Application Security is monitoring (processes, K8s resources)
- No ease-of-use when modifying rules (e.g., no auto-complete - making the rule prone to typos)
- A different setup from code-level vulnerabilities and attack protection.

**The solution**

We introduced a new way of setting up what you want to monitor with Application Security.

Existing customers are eligible to see both **Classic** and **New** rules, while new customers will only be able to see the **New** ones.

Existing customers can see a toggle in the classic settings (_Application security \> General settings_) called _Enable new monitoring rules_ to switch between the rule sets.

 ![RVA_Settings.png](https://global.discourse-cdn.com/dynatrace/original/2X/4/4c78fbf17c7b78ecb3e8b348e92d29609897f961.jpeg)

The **New** rules are based on more transparent and straightforward concepts:

- Library and runtime vulnerability monitoring can be configured using **resource attributes** , for example, _host.name contains prod_
- Kubernetes vulnerability monitoring can be configured using **Kubernetes labels** , for example, _[kubernetes.io/hostname](http://kubernetes.io/hostname) contains prod_

We introduced more ease-of-use and transparency when setting up rules:

- You get suggestions for keys & values
  - Based on the information available in your environment
  - You’re still able to enter any text in these fields

- You have more comparison options (e.g. _contains, exists, startsWith,_ …)
- Each rule allows you to preview the entities that are matched with the conditions given

 ![Rule_suggestions.png](https://global.discourse-cdn.com/dynatrace/original/3X/d/4/d40d51470b3dae17b702fde43e61ed2dc8368ee9.png)  
_Suggestions_

 ![Rule_preview.png](https://global.discourse-cdn.com/dynatrace/original/3X/7/f/7f8fc55b18088841fe23a7ba38af3e085207a85b.png)

_Per-rule preview of matched entities of the rule_

You can read more about the new monitoring rules in the public documentation: [Monitoring rules - Third-party Vulnerability Analytics - Dynatrace Docs](https://docs.dynatrace.com/docs/shortlink/tpv-monitoring-rules#new).

We came up with a set of common use cases you could consider when setting up the “new” monitoring rules. They can also be found in the public documentation: [use cases for monitoring rules - Dynatrace Docs](https://docs.dynatrace.com/docs/secure/application-security/vulnerability-analytics/third-party-vulnerabilities/use-cases-monitoring-rules) .