OneLogin IAM Platform(using Azure Functions) connector for Microsoft Sentinel
The OneLogin data connector provides the capability to ingest common OneLogin IAM Platform events into Microsoft Sentinel through Webhooks. The OneLogin Event Webhook API which is also known as the Event Broadcaster will send batches of events in near real-time to an endpoint that you specify. When a change occurs in the OneLogin, an HTTPS POST request with event information is sent to a callback data connector URL. Refer to Webhooks documentation for more information. The connector provides ability to get events which helps to examine potential security risks, analyze your team's use of collaboration, diagnose configuration problems and more.
This is autogenerated content. For changes, contact the solution provider.
Connector attributes
| Connector attribute | Description |
|---|---|
| Log Analytics table(s) | OneLogin_CL |
| Data collection rules support | Not currently supported |
| Supported by | Microsoft Corporation |
Query samples
OneLogin Events - All Activities.
OneLogin
| sort by TimeGenerated desc
Prerequisites
To integrate with OneLogin IAM Platform(using Azure Functions) make sure you have:
- 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.
- Webhooks Credentials/permissions: OneLoginBearerToken, Callback URL are required for working Webhooks. See the documentation to learn more about configuring Webhooks.You need to generate OneLoginBearerToken according to your security requirements and use it in Custom Headers section in format: Authorization: Bearer OneLoginBearerToken. Logs Format: JSON Array.
Vendor installation instructions
Note
This data connector uses Azure Functions based on HTTP Trigger for waiting POST requests with logs 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.
Note
This data connector depends on a parser based on a Kusto Function to work as expected OneLogin which is deployed with the Microsoft Sentinel Solution.
STEP 1 - Configuration steps for the OneLogin
Follow the instructions to configure Webhooks.
- Generate the OneLoginBearerToken according to your password policy.
- Set Custom Header in the format: Authorization: Bearer
<OneLoginBearerToken>. - Use JSON Array Logs Format.
STEP 2 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function
IMPORTANT: Before deploying the OneLogin data connector, have the Workspace ID and Workspace Primary Key (can be copied from the following).
Next steps
For more information, go to the related solution in the Azure Marketplace.