Adding an in-house application to the Easy2Patch catalog

Security has been a major concern since the dawn of the information age. Especially nowadays, there are a lot of data breaches from relatively large companies. And a significant number of breaches are caused by software vulnerabilities rather than protocol vulnerabilities. In this article, I will talk about the importance of using up-to-date software and adding special products to the catalog.

Easy2Patch hosts hundreds of 3rd party software catalogs. However, in-house developed, or licensed products may not be included in the catalog. It is also not possible for these products to be added to the catalog by E2P Software. Because the products added to the catalog must be accessible, downloadable, and installable software by all customers. Easy2Patch provides a feature called Custom Product Injection for adding enterprise-specific applications to the catalog. So, with this feature, products that cannot be included in the catalog can be added. The product added to the catalog will be distributable via SCCM or Intune as application.

There are many attack vectors that can be launched from a software vulnerability, and serious scenarios can occur from them. So how can we protect ourselves from these attacks? The answer is to use up-to-date software. As you know, security updates for a wide variety of operating systems are periodically released by vendors. What about 3rd party software? You can manually update them by visiting their official website, downloading, and installing the latest version. However, if there are many 3rd party applications, it is not easy to check all software in this way and to keep it up to date. These processes can take a lot of time and are prone to errors. Easy2Patch can be used to make the 3rd party software centralized update process much easier and more convenient.

First, on the Easy2Patch screen, one of the Application, Intune Update or Intune Application tabs is switched. This feature is only available in Advanced and Enterprise licensing. Select the node with the license owner's name in the Custom App Category at the bottom of the list and right-click then select Add Applicaton.

The following screens are filled in order:

  • Title: The name of the application is entered.

  • Description: enters a short description about the application.

  • Version: The version information that appears on the Add/remove Programs screen of the product is entered. It is important to enter it exactly as it appears. Publisher: manufacturer information is entered.

  • URL/File: The file is displayed from a URL or local file system.

  • File Name: The name of the file. It is filled automatically.

  • Digest: It is the digest information of the file. is filled automatically.

  • Auto Deploy: Allows the application to be deployed automatically during deployment on SCCM or Intune.

  • Title: The name of the application is entered.

  • Description: enters a short description about the application.

  • Icon: An icon file with ico extension can be given, which can be up to 1 MB in size.

  • Title: The name of the application is entered.

  • Description: Enters a short description about the application.

  • Install Command Line: Enter the unattended installation parameters. The name of the application does not need to be entered.

  • Uninstall Command Line: Unattended uninstall parameters are entered. The name of the application does not need to be entered.

  • Installation Behavior: Deploy to User or System option is selected.

  • Detection Method: These are important parameters that must be entered to understand whether the application is installed on the target system. These parameters are searched in the Uninstall registry sets of the target system.

    • App To Sarch: Searches the DisplayName registry key of the application. It can be done in queries with a similar name by adding a wildcard (*) to this field. Fortinet means beginning with the word Fortinet.

    • Exclude Name: Adds the condition that this name should not appear in the DisplayName field.

    • Version: Searches the application's DisplayVersion registry key.

    • App MSI Code: It checks the MSI code of applications that have MSI setup.

    • Architecture: x86: Searches for 32-bit application installed on a 32-bit or 64-bit system. x64: Searches for 64-bit application installed on a 64-bit system.

Click the Save button and the application is added to the list. The application is now distributable.

After adding the application to the tree, the Save button must be click. After this stage, the application can now be publish.

Last updated