Workflow Configuration Parameters in the Mend Platform

Overview

This article covers the Automation Workflow configuration options within the Application of the Mend Platform.

Getting it done

Workflows - General Details

The General Details section is where you name your workflow. This value is displayed in the Name column within the Automation page of the Mend Platform.

Tip: We recommend naming the workflow with a value that will help you and your team understand its usage.

Workflows - Triggering Event

The Triggering Event section is where you set the event(s) (WHEN) to trigger the workflow:

AI Analysis
Code Analysis
Containers Analysis
Dependencies Analysis
New Application Created
New Project Created

Workflows - Scope Conditions

The Scope Conditions section is where you define the scope that the conditions/triggers will apply to, where you can select the option to Include/Exclude the defined settings:

Entire Organization
Application
Project
Labels

Workflows - Event Conditions

The Event Conditions section is where you set the condition(s) (IF) to trigger the workflow. You can set multiple conditions condition groups and define their logical expressions (OR, AND).

By Model Scan Complete - AI

Condition	Details
`Is Malicious Model`	The workflow action will be triggered if a malicious model is detected (or not). You can set the workflow trigger values to either `True` or `False`.
`Licenses`	The workflow action will be triggered if a specific License Name is found (or not). You can set the workflow trigger values to either `In`, `Is Empty`, `Match`, `Not In`, `No Match`, or `Regex` and select license name(s) from the dropdown list. Notes: Event conditions for licenses rely on exact string matches and do not support ranges. For example: If an event condition specifies “LGPL 1.0 or Later”, LGPL 1.0 will only be matched when the library license is listed as "LGPL 1.0 or Later" and not if the library license is listed as "LGPL 2.0". The number of selected licenses is limited to 50.
`Model Age`	Set the Model Age by those older than a certain number of days or months, defining a specific date range (`Between`), `Greater Than`, or `Less Than`.
`Model Name`	The workflow action will be triggered if a model name matching the defined criteria is detected.
`Vulnerability ID`	The workflow action will be triggered if a specific Vulnerability ID is found (or not). You can set the workflow trigger values to either `Equals` or `Not Equals`.
`Vulnerability Score`	Set the Vulnerability Score rating criteria that will trigger the workflow action. The supported syntax is a decimal number from 0 - 10. For example: `5.4`
`Vulnerability Severity`	The workflow action will be triggered if a Vulnerability Severity equals (or not). You can set the workflow trigger values to either `Unknown`,`Low`, `Medium`, `High`, or `Critical`.

By Code Scan Complete - SAST

Condition	Details
`Finding Age`	Set the Finding Age by those older than a certain number of days or months, defining a specific date range (`Between`) or `Greater Than`.
`Finding CWE Type`	Set the specific CWE Type ID from the provided dropdown list that will trigger the workflow action. Note: Using the OWASP Top 10, SANS Top 25 or PCI DSS templates from the Template Gallery will autofill all the relevant CWE Type IDs.
`Finding Severity`	Set the Findings Severity and occurrences criteria that will trigger the workflow action. The supported syntax is a number greater than 0.

By Dependencies Scan Complete - SCA

Condition	Details
`EPSS Score`	Set the EPSS Score rating criteria that will trigger the workflow action. The supported syntax is a decimal number from 0 - 1. For example: `0.4`.
`Is Malicious Package`	The workflow action will be triggered if a malicious package is detected (or not). You can set the workflow trigger values to either `True` or `False`.
`Library Name`	The workflow action will be triggered if a library name matching the defined criteria is detected.
`Licenses`	The workflow action will be triggered if a specific License Name is found (or not). You can set the workflow trigger values to either `In`, `Is Empty`, `Match`, `Not In`, `No Match`, or `Regex` and select license name(s) from the dropdown list. Note: Event conditions for licenses rely on exact string matches and do not support ranges. For example: If an event condition specifies “LGPL 1.0 or Later”, LGPL 1.0 will only be matched when the library license is listed as "LGPL 1.0 or Later" and not if the library license is listed as "LGPL 2.0". The number of selected licenses is limited to 50.
`Vulnerability ID`	The workflow action will be triggered if a specific Vulnerability ID is found (or not). You can set the workflow trigger values to either `Equals` or `Not Equals`.
`Vulnerability Reachable`	The workflow action will be triggered if a Reachable Vulnerability is found (or not). You can set the workflow trigger values to either `True`, `False`, or `Unknown`.
`Vulnerability Score`	Set the Vulnerability Score rating criteria that will trigger the workflow action. The supported syntax is a decimal number from 0 - 10. For example: `5.4`
`Vulnerability Severity`	The workflow action will be triggered if a Vulnerability Severity equals (or not). You can set the workflow trigger values to either `Unknown`,`Low`, `Medium`, `High`, or `Critical`.

By Image Scan Complete - Containers

Condition	Details
`EPSS Score`	Set the EPSS Score rating criteria that will trigger the workflow action. The supported syntax is a decimal number from 0 - 1. For example: `0.4`.
`Library Name`	The workflow action will be triggered if a library name matching the defined criteria is detected.
`Licenses`	The workflow action will be triggered if a specific License Name is found (or not). You can set the workflow trigger values to either `In`, `Is Empty`, `Match`, `Not In` or `No Match` and select license name(s) from the dropdown list. Note: Event conditions for licenses rely on exact string matches and do not support ranges. For example: If an event condition specifies “LGPL 1.0 or Later”, LGPL 1.0 will only be matched when the library license is listed as "LGPL 1.0 or Later" and not if the library license is listed as "LGPL 2.0".
`Vulnerability ID`	The workflow action will be triggered if a specific Vulnerability ID is found (or not). You can set the workflow trigger values to either `Equals` or `Not Equals`.
`Vulnerability Reachable`	The workflow action will be triggered if a Reachable Vulnerability is found (or not). You can set the workflow trigger values to either `True` or `False`.
`Vulnerability Score`	Set the Vulnerability Score rating criteria that will trigger the workflow action. The supported syntax is a decimal number from 0 - 10. For example: `5.4`
`Vulnerability Severity`	The workflow action will be triggered if a Vulnerability Severity equals (or not) . You can set the workflow trigger values to either `Unknown`,`Low`, `Medium`, `High`, or `Critical`.

Workflows - Action options

The Actions section is where you set the response (THEN) to the condition(s) being met for the workflow.

Value	Details
`Assign Label`	Set the Labels from the provided dropdown list that will be assigned for the Application/Project. Note: The number of selected labels is limited to 50.
`Create Jira Issue`	Create a Jira Issue. Note: Creating Jira Issues from within the Mend Platform requires you to have Mend's Jira Integration installed and configured.
`Create Policy Violation`	Create a Policy Violation for a triggered completed scan. You have to configure the Violation Priority, Violation SLA, and if to fail the pipeline when a violation is detected. To learn more about configuring policy violation settings, please refer to our Configure Policy Violations with Automation Workflows documentation.
`Email Scan Details`	When triggered, findings from this workflow are added to the scan summary email sent to the Organization and Application Admins. Notification preferences can be managed from the Profile settings ().

Email Notifications

Navigate to My Profile → Email Notifications to enable/disable Scan Summary Email notifications for your user.

Email notifications can be enabled/disabled per organization or as a bulk operation for all the organizations your user is a member of, using the Enable for All Organizations toggle.

Click “Yes, Enable” when prompted, to confirm.

Email Notifications Behavior

By default, users will receive scan summary emails only for applications they are authorized to access, based on their assigned permissions.

Reference

Create an Automation Workflow in the Mend Platform

Edit an Automation Workflow in the Mend Platform

Disable an Automation Workflow in the Mend Platform

Delete an Automation Workflow in the Mend Platform

Workflow Configuration Parameters in the Mend Platform

Configure Policy Violations with Automation Workflows