↳ Source GitHubConnecteur

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.
Statut déclaré
1
Auteur / éditeur déclaré
Joe Security LLC

Sources déclarées

Métadonnées du fichier source. Aucune dépendance déduite du KQL.

Types de données

Permissions déclarées

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.

Instructions du connecteur

Contenu publié dans le dépôt. Consultez le fichier original pour l’ensemble des paramètres.

>**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.

Contenus associés

Liens établis à partir des identifiants déclarés et des manifests des solutions.

Traçabilité de la source

GitHub

Les valeurs affichées proviennent des fichiers du dépôt Azure/Azure-Sentinel. Elles décrivent le modèle publié, pas la configuration de votre workspace.

Identifiant source
JoeSandbox
Autres fichiers source 2Solutions/JoeSandbox/Data Connectors/JoeSandboxThreatIntelligence_FunctionApp.jsonsource ↗Solutions/JoeSandbox/Data/Solution_JoeSandbox.jsonsolution-membership ↗
GSTEP / SUIVI DU CATALOGUE

Ajouté au catalogue : 16 sept. 2026 · 05:49 UTC
Dernier changement observé : 16 sept. 2026 · 05:49 UTC

Dates de synchronisation GSTEP, distinctes des dates de publication du contenu source.