Azure-Sentinel/DataConnectors/JumpCloud Single Sign On
v-amolpatil 10f239299b migrate app insights to log analytic workspace code change in azure deploy files 2024-01-10 15:30:29 +05:30
..
AzureFunctionJumpCloud V laanjana/update runtime version update( 4) and extensionBundle version (#6675) 2022-11-28 18:31:42 +05:30
Readme.md Update Readme.md 2021-08-13 18:02:19 -07:00
azuredeploy_JumpCloud_API_FunctionApp.json migrate app insights to log analytic workspace code change in azure deploy files 2024-01-10 15:30:29 +05:30

Readme.md

Azure Sentinel Data Connector for JumpCloud SSO event logs

This Azure Function App will connect to the JumpCloud Rest-API using your JumpCloud api Token and retrieve the event logs and ingest them into a custom table called "JumpCloud" in your Log Anaytics Workspace used by Azure Sentinel.

The Azure Function has bee setup to trigger once every 5 minutes and trigger a seperate execution for each log type listed in the configuration you setup.

Prerequisites

Before deplying this Arm Template

  1. Decide which of the JumpCloud logs you want to ingest into Azure Sentinel, details on the log types available are found in their documentation here. You can choose any combination of event type for ingestion However Do not mix 'ALL' type with any other or duplicate events will be ingested.
  2. You may need a JumpCloud license that enables Directory Insights to be able to access the Rest-API.
  3. Follow the instructions on the JumpCloud docs on how to access your API Key.
  4. You will need your WorkspaceID and WorkspaceKey for the Log Analytics Workspace you want the logs to be ingested into.

NOTE: There maybe additional charges incurred on your Azure Subscription if you run this Azure Function

Deployment

The simplest way to deploy is to launch the Deployment template from the Deploy to [Azure Button below]

NOTES:

  1. Where possible details in the Deployment Template have been prepopulated.
  2. The function name needs to be globally unique, a random character generator will generate several charactors to append to your entered name. Be aware that this name is also used for the associated storage account so if your prefix is too long the template will fail validation becuase the name is longer than the permitted length for a storage Account Name.
  3. Once successfully deployed the function will start triggering within 5 minutes and the inital request to JumpCloud will be for logs since the previous midnight UTC time.

Deploy to Azure