⚠️ 🔍 Agari Phishing Defense and Brand Protection

⚠️ Unpublished: This item is from a solution that is not yet published on Azure Marketplace or not installed in Content Hub.

🔍 Discovered: This item was discovered by scanning the solution folder but is not listed in the Solution JSON file.

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

Back to Connectors Index


Attribute Value
Connector ID Agari
Publisher Agari
Used in Solutions Agari
Collection Method Azure Function
Connector Definition Files Agari_API_FunctionApp.json
Ingestion API HTTP Data Collector APIConnector definition requires workspace key (SharedKey pattern)
Custom Log V1 Tables Yes 🔶 — ingests into tables with type-suffixed columns

This connector uses a Agari REST API connection to push data into Microsoft Sentinel Log Analytics.

Tables Ingested

This connector ingests data into the following tables:

Table Transformations Ingestion API Lake-Only
agari_apdpolicy_log_CL 🔶 ? ?
agari_apdtc_log_CL 🔶 ? ?
agari_bpalerts_log_CL ? ?

💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.

Permissions

Resource Provider Permissions:

Custom Permissions:

Setup Instructions

⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.

NOTE: This connector uses Azure Functions to connect to the Agari APIs to pull its logs into Microsoft Sentinel. This might result in additional data ingestion costs. Check the Azure Functions pricing page 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 to use Azure Key Vault with an Azure Function App.

1. STEP 1 - Get your Agari API credentials

  1. Log into any Agari product (Client ID and Secret are the same for all applications)
  2. Click on your username in the upper right and select Settings
  3. Click on the Generate API Secret link to generate an API client_id and client_secret (the link will read Regenerate API Secret if you have already generated an API client ID/secret previously)
  4. Copy both the client_id and client_secret that are generated

2. STEP 2 - (Optional) Enable the Security Graph API

Follow the instrcutions found on article Connect Microsoft Sentinel to your threat intelligence platform. Once the application is created you will need to record the Tenant ID, Client ID and Client Secret.

3. STEP 3 - Deploy the connector and the associated Azure Function

IMPORTANT: Before deploying the Agari Connector, have the Workspace ID and Workspace Primary Key (can be copied from the following), as well as the Agari API credentials from the previous step.

4. Choose a deployement option

5. Option 1: Deploy using the Azure Resource Manager (ARM) Template

  1. Click the Deploy to Azure button below.

    Deploy To Azure

  2. Select the preferred Subscription, Resource Group and Location.

  3. Enter the Workspace ID, Workspace Key, Agari Client ID, Agari Client Secret, select True or False for the products you subscribe to, and if you wish to share IoCs with Sentinel, select True For Enable Security Graph Sharing, and enter the required IDs from the Azure Application.

  1. Mark the checkbox labeled I agree to the terms and conditions stated above.
  2. Click Purchase to deploy.
  3. NOTE: Due to the use of Environment Variables to store log access times, the App requires 1 additonal manual step. In the Function App, select the Function App Name and select Click on Identity and for System assigned Identity, click on Azure role assignments and Add Role assignment. Select Subscription as the scope, select your subscription and set the Role to Contributor. Click on Save.

6. Option 2: Manual Deployment of Azure Functions

1. Create a Function App

  1. From the Azure Portal, navigate to Function App, and select + Add.
  2. In the Basics tab, ensure Runtime stack is set to Powershell Core.
  3. In the Hosting tab, ensure the Consumption (Serverless) plan type is selected.
  4. Make other preferrable configuration changes, if needed, then click Create.

2. Import Function App Code

  1. In the newly created Function App, select Functions on the left pane and click + Add.
  2. Click on Code + Test on the left pane.
  3. Copy the Function App Code and paste into the Function App run.ps1 editor.
  4. Click Save.

3. Configure the Function App

  1. In the Function App, select the Function App Name and select Configuration.
  2. In the Application settings tab, select + New application setting.
  3. Add each of the following eight to twelve (8-12) application settings individually, with their respective string values (case-sensitive): clientID clientSecret workspaceID workspaceKey enableBrandProtectionAPI enablePhishingResponseAPI enablePhishingDefenseAPI resGroup functionName subId enableSecurityGraphSharing <--- Required if enableSecurityGraphSharing is set to true ---> GraphTenantId GraphClientId GraphClientSecret logAnalyticsUri (optional)

4. Set Permissions for the App

  1. In the Function App, select the Function App Name and select Click on Identity and for System assigned Identity, set the status to On.

  2. Next, click on Azure role assignments and Add Role assignment. Select Subscription as the scope, select your subscription and set the Role to Contributor. Click on Save.

5. Complete Setup.

  1. Once all application settings have been entered, click Save. Note that it will take some time to have the required dependencies download, so you may see some inital failure messages.

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

Back to Connectors Index