---
title: Trusted Vendor Rule
slug: neurons/help/en_us/trusted-vendor-rule
createdAt: 2026-11-05T08:02:08.304Z
---

Trusted Vendors are used for listing valid digital certificates. A digital certificate is an electronic document that uses a digital signature to bind together a public key with an identity. This includes information such as the name of a person or organization, address, and so on. Digital certificates are issued by a certificate authority and used to verify that a public key belongs to an individual. App Control queries each file execution to detect the presence of a digital certificate. If the file has a valid digital certificate and the signer matches an entry in the Trusted Vendor list, the file is allowed to run, and overrides any trusted ownership checking.

Rule creation workflow steps:

1. What **Rule** do you want to create?
2. **What** vendor do you want to trust?
3. **When** is the rule assigned?
4. **Summary** and Save

## Create an Elevate Rule

1. On the **What do you want to do?** page, select **I want to add a trusted vendor**.
2. Click **Next**.
   The **Choose Trusted Vendor** page appears.
3. Click **Add Trusted Vendor**.
   The **Trusted vendor - Settings** panel appears.
4. Enter the name of the **Vendor**. Optionally, select whether to use regular expressions.
5. To restrict the rule to apply only to files in a certain location, enter the **Path**. If no path is entered, the rule will apply to all files signed by the vendor. Optionally, select whether to use regular expressions.
6. Optionally enter a **Description**.
7. Click **Save**.
   The vendor appears in the **Trusted Vendors** list.
8. Click **Next**.
   The **Trusted Vendor - When is this assigned?** page appears.
9. In **Select a source**, use the drop-down to select the source of the items, any selected or added sources will display in the **Selected Items** section. Select from:
   - **AD Groups**: The AD Display and Group names are listed, you can use the search and filter to refine the list. Alternatively, you can manually add a group, by clicking **Add manually**.
   - **AD Users**: Enter domain\username and click **Add**.
   - **App Control Users**: The username of users that App Control has recorded an event for. Select the required users.
   - **Computer Groups**: Enter the computer group, for example: CN=ComputerGroup. If you want to include nested groups select Search nested groups. Click **Add**.
   - **Device Organizational Units**: Enter the organizational unit, for example: OU=Corporation. If you want to include sub-OUs selec&#x74;**&#x20;Include sub-OUs**. Click **Add**.
   - **Devices**: The Device and Host names of all Neurons discovered window devices are listed, you can use the search and filter to refine the list. Alternatively, you can manually add a device, by clicking **Add manually**.
   - **Entra ID Groups**: Displays the collection of users, devices, or groups synced from Microsoft Entra ID. To configure and sync Entra ID groups, refer to [Configuring Entra ID](docId\:lqeCTG_or-1Smnw4sX_a4).
   - **Entra ID Users**: Displays the list of users that are synced form Microsoft Entra ID. To sync and configure Entra ID users, refer to [Configuring Entra ID](docId\:lqeCTG_or-1Smnw4sX_a4).
   - **IP Addresses**: Enter the IP addresses and select whether you want to match regular expressions against IP addresses. Click **Add**.
     **Example**:
     - 192.168.0.1: select the client device with an IP of 192.168.0.1
     - 192.168.0.\*: select the client devices with an IP of 192.168.0.\<any>
     - 192.168.0.15-25: select all client devices within the IP range of 192.168.0.15 to 192.168.0.25
   - **Parent Processes**: The Parent Processes are listed on two tabs: **App Control Data** and **App Templates**. Select the required processes.
   - **Scripted**: Scripted rules enable custom rule creation using PowerShell or VBScript to dynamically allow, deny ,or elevate application control. Form more information about adding scripted rules, refer to [Scripted Rule](docId\:j5dfvVgIox3qAYKRJR64U).
   - Alternatively, select **Everyone** to create the rule for the Everyone group, this includes any user that logs on to a device that has the configuration successfully deployed, with the exception of Administrators.
10. Once you are finished adding to the **Selected Items**. Click **Next**.
    The **Save Rule and Rule Summary** page appears.
11. Enter a **Name** for the rule, and provide an optional **Description**.
12. In **Categories**, enter an optional category tag for the rule.
    You can add an existing category, or create a new one. The Categories assigned to a rule are visible in the [Configuration Rules](docId\:DZgL6s_on4oT3kJaQltfD) table.
    - To add: Click in **Categories** to display a drop-down list of existing categories, select the required categories.
    - To create: Click in **Categories** and type the new category tag, click out of the field to create and save the category.
13. The default status for the rule is to be **Active**, if you do not want to make the rule active yet, toggle the **Rule Status** to off.
14. Click **Save** to save the rule and return to the configuration, where you'll see the new rule listed in the **Rules** section.
    Alternatively click **Save & Add another**, to save the rule and return to the **What do you want to do?** page to create another rule for the configuration.
15. When you have added all the rules to the configuration, click **Save** to save the configuration as draft. Or, click **Save & Publish** to save the version of the configuration.
    Once published, the configuration is available for assignment to a policy.
