Digital Shadows Searchlight

>**NOTE:** This connector uses Azure Functions to connect to a 'Digital Shadows Searchlight' 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 the 'Digital Shadows Searchlight' 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 - Configuration steps for the 'Digital Shadows Searchlight' API** The provider should provide or link to detailed steps to configure the 'Digital Shadows Searchlight' API endpoint so that the Azure Function can authenticate to it successfully, get its authorization key or token, and pull the appliance's logs into Microsoft Sentinel.

**STEP 2 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function** >**IMPORTANT:** Before deploying the 'Digital Shadows Searchlight' connector, have the resource ID of the Log Analytics workspace where the `DigitalShadows_V2_CL` table will live, as well as the 'Digital Shadows Searchlight' API authorization key(s) or Token, readily available. The connector authenticates to Azure Monitor using a system-assigned managed identity; no shared workspace key is required.

**Option 1 - Azure Resource Manager (ARM) Template** Use this method for automated deployment of the 'Digital Shadows Searchlight' connector. 1. Click the **Deploy to Azure** button below. [](https://aka.ms/sentinel-Digitalshadows-azuredeploy) 2. Select the preferred **Subscription**, **Resource Group** and **Location**. 3. Enter the **DcrWorkspaceResourceId** (the full resource ID of your Log Analytics workspace, in the form `/subscriptions/<sub>/resourceGroups/<rg>/providers/Microsoft.OperationalInsights/workspaces/<workspace>`), **API Username**, **API Password**, 'and/or Other required fields'. >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 labeled **I agree to the terms and conditions stated above**. 5. Click **Purchase** to deploy. The template provisions a Data Collection Endpoint, a Data Collection Rule, the `DigitalShadows_V2_CL` table, and grants the Function Apps' managed identities the **Monitoring Metrics Publisher** role on the Data Collection Rule.

**Option 2 - Manual Deployment of Azure Functions** Use the following step-by-step instructions to deploy the 'Digital Shadows Searchlight' connector manually with Azure Functions.

1. Create a Function App

1. From the Azure Portal, navigate to [Function App](https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.Web%2Fsites/kind/functionapp). 2. Click **+ Create** at the top. 3. In the **Basics** tab, ensure Runtime stack is set to **python 3.11**. 4. In the **Hosting** tab, ensure **Plan type** is set to **'Consumption (Serverless)'**. 5.select Storage account 6. 'Add other required configurations'. 5. 'Make other preferable configuration changes', if needed, then click **Create**.

2. Enable the system-assigned managed identity and grant it permission to publish metrics

1. In the Function App screen, open **Identity** under **Settings**. 2. On the **System assigned** tab, set **Status** to **On** and click **Save**. Note the displayed **Object (principal) ID** — you will need it to grant the role. 3. Navigate to the **Data Collection Rule** (DCR) that owns the `Custom-DigitalShadows_V2_CL` stream and open its **Access control (IAM)** blade. 4. Click **+ Add role assignment**, select the **Monitoring Metrics Publisher** role, choose **Managed identity** as the member type, and assign the Function App's system-assigned identity. Save. 5. Repeat steps 1-4 for the second (`exclude`) Function App if you are running both.

3. Import Function App Code(Zip deployment)

1. Install Azure CLI 2. From terminal type **az functionapp deployment source config-zip -g <ResourceGroup> -n <FunctionApp> --src <Zip File>** and hit enter. Set the `ResourceGroup` value to: your resource group name. Set the `FunctionApp` value to: your newly created function app name. Set the `Zip File` value to: `digitalshadowsConnector.zip`(path to your zip file). Note:- Download the zip file from the link - [Function App Code](https://github.com/Azure/Azure-Sentinel/blob/master/Solutions/Digital%20Shadows/Data%20Connectors/Digital%20Shadows/digitalshadowsConnector.zip)

4. Configure the Function App

1. In the Function App screen, click the Function App name and select **Configuration**. 2. In the **Application settings** tab, select **+ New application setting**. 3. Add each of the following application settings individually, under Name, with their respective string values (case-sensitive) under Value: DigitalShadowsAccountID DigitalShadowsKey DigitalShadowsSecret DigitalShadowsURL HistoricalDays DCE_URL DCR_IMMUTABLE_ID STREAM_NAME ClassificationFilterOperation HighVariabilityClassifications FUNCTION_NAME (add any other settings required by the Function App) Set the `DigitalShadowsURL` value to: `https://api.searchlight.app/v1` Set the `HighVariabilityClassifications` value to: `exposed-credential,marked-document` Set the `ClassificationFilterOperation` value to: `exclude` for exclude function app or `include` for include function app Set the `DCE_URL` value to your Data Collection Endpoint logs-ingestion URI (e.g. `https://<dce-name>.<region>-1.ingest.monitor.azure.com`). Set the `DCR_IMMUTABLE_ID` value to the immutable ID of the Data Collection Rule (visible in the DCR overview blade as `Immutable ID`). Set the `STREAM_NAME` value to: `Custom-DigitalShadows_V2_CL` >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 [Azure Key Vault references documentation](https://docs.microsoft.com/azure/app-service/app-service-key-vault-references) for further details. 4. Once all application settings have been entered, click **Save**.