↳ GitHub sourceConnector

JoeSandboxThreatIntelligence

Description

JoeSandboxThreatIntelligence connector automatically generates and feeds threat intelligence for all submissions to JoeSandbox, improving threat detection and incident response in Sentinel. This seamless integration empowers teams to proactively address emerging threats.
Declared status
1
Declared author / publisher
Joe Security LLC

Declared sources

Metadata from the source file. No dependencies inferred from KQL.

Data types

Declared permissions

read and write permissions on the workspace are required.
Workspace
Workspace
read permissions to shared keys for the workspace are required. [See the documentation to learn more about workspace keys](https://docs.microsoft.com/azure/azure-monitor/platform/agent-windows#obtain-workspace-id-and-key).
Keys
Workspace
Azure Subscription
Azure Subscription with owner role is required to register an application in azure active directory() and assign role of contributor to app in resource group.
Microsoft.Web/sites permissions
Read and write permissions to Azure Functions to create a Function App is required. [See the documentation to learn more about Azure Functions](https://docs.microsoft.com/azure/azure-functions/).
REST API Credentials/permissions
**JoeSandbox API Key** is required.

Connector instructions

Content published in the repository. Refer to the original file for all parameters.

>**NOTE:** This connector uses Azure Functions to connect to the JoeSandbox API to pull JoeSandbox Threat IOCs into Microsoft Sentinel. This might result in additional costs for data ingestion and for storing data in Azure Blob Storage costs. Check the [Azure Functions pricing page](https://azure.microsoft.com/pricing/details/functions/) and [Azure Blob Storage pricing page](https://azure.microsoft.com/pricing/details/storage/blobs/) 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.
Workspace ID
Primary Key
Option 1 - Azure Resource Manager (ARM) Template for Flex Consumption Plan
Use this method for automated deployment of the data connector using an ARM Template. 1. Click the **Deploy to Azure** button below. [![Deploy To Azure](https://aka.ms/deploytoazurebutton)](https://aka.ms/sentinel-JoeSandbox-azuredeployflex) 2. Select the preferred **Subscription**, **Resource Group** and **Location**. 3. Enter the **Application ID**, **Tenant ID**,**Client Secret**, **JoeSandbox API Key**, **JoeSandbox Initial Fetch Date**, **TimeInterval** and deploy. 4. Mark the checkbox labeled **I agree to the terms and conditions stated above**. 5. Click **Purchase** to deploy.
Option 2 - Azure Resource Manager (ARM) Template for Premium Plan
Use this method for automated deployment of the data connector using an ARM Template. 1. Click the **Deploy to Azure** button below. [![Deploy To Azure](https://aka.ms/deploytoazurebutton)](https://aka.ms/sentinel-JoeSandbox-azuredeploypremium) 2. Select the preferred **Subscription**, **Resource Group** and **Location**. 3. Enter the **Application ID**, **Tenant ID**,**Client Secret**, **JoeSandbox API Key**, **JoeSandbox Initial Fetch Date**, **TimeInterval** and deploy. 4. Mark the checkbox labeled **I agree to the terms and conditions stated above**. 5. Click **Purchase** to deploy.

Related content

Links established from declared identifiers and solution manifests.

Source provenance

GitHub

Displayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.

Source identifier
JoeSandbox
Additional source files 2Solutions/JoeSandbox/Data Connectors/JoeSandboxThreatIntelligence_FunctionApp.jsonsource ↗Solutions/JoeSandbox/Data/Solution_JoeSandbox.jsonsolution-membership ↗
GSTEP / CATALOG TRACKING

Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC

GSTEP sync dates, separate from the source content’s publication dates.