RISK-BASED AUTOMATION
Separate rules for separate applications
Same vulnerability may not be equally critical in two different applications. With misconfigured automation that treats them the same, you might easily create friction with your developers.
Turn the output of your threat-modeling activities into labels for your applications and create separate automation rules for each label to ensure only relevant vulnerabilities are brought to the attention of development teams.