ESET Inspect

>**NOTE:** This connector uses Azure Functions to connect to ESET Inspect to pull its logs into Microsoft Sentinel. This might result in additional data ingestion costs. Check the [Azure Functions pricing page](https://azure.microsoft.com/pricing/details/functions/) for details.

>**(Optional Step)** Securely store workspace and API authorization key(s) or token(s) in Azure Key Vault. Azure Key Vault provides a secure mechanism to store and retrieve key values. [Follow these instructions](https://docs.microsoft.com/azure/app-service/app-service-key-vault-references) to use Azure Key Vault with an Azure Function App.

Step 1 - Create an API user

1. Log into the ESET PROTECT console with an administrator account, select the **More** tab and the **Users** subtab. 2. Click on the **ADD NEW** button and add a **native user**. 3. Create a new user for the API account. **Optional:** Select a **Home group** other than **All** to limit what detections are ingested. 4. Under the **Permission Sets** tab, assign the **Inspect reviewer permission set**. 4. Log out of the administrator account and log into the console with the new API credentials for validation, then log out of the API account. 5.

Step 2 - Copy Workspace ID and Key

>**IMPORTANT:** Before deploying the ESET Inspect connector, have the Workspace ID and Workspace Primary Key (can be copied from the following) readily available.

Workspace ID

Primary Key

Step 3 - Deploy the Azure Resource Manager (ARM) Template

Use this method for automated deployment of the ESET Inspect connector using an ARM Tempate. 1. Click the **Deploy to Azure** button below. [](https://aka.ms/sentinel-ESETInspect-azuredeploy) 2. Select the preferred **Subscription**, **Resource Group** and **Location**. 3. Enter the **Workspace ID**, **Workspace Key**, **API Username**, **API Password** , enter the **Inspect base URL** and the **first ID** to start ingesting detections from. - The defailt starting ID is **0**. This means that all detections will be ingested. - Note: If using Azure Key Vault secrets for any of the values above, use the`@Microsoft.KeyVault(SecretUri={Security Identifier})`schema in place of the string values. Refer to [Key Vault references documentation](https://docs.microsoft.com/azure/app-service/app-service-key-vault-references) for further details. 4. Mark the checkbox labelled **I agree to the terms and conditions stated above**. 5. Click **Purchase** to deploy.