Box (using Azure Functions) connector for Microsoft Sentinel

The Box data connector provides the capability to ingest Box enterprise's events into Microsoft Sentinel using the Box REST API. Refer to Box documentation for more information.

This is autogenerated content. For changes, contact the solution provider.

Connector attributes

Connector attribute	Description
Log Analytics table(s)	BoxEvents_CL
Data collection rules support	Not currently supported
Supported by	Microsoft Corporation

Query samples

All Box events

BoxEvents

| sort by TimeGenerated desc

Prerequisites

To integrate with Box (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.
• Box API Credentials: Box config JSON file is required for Box REST API JWT authentication. See the documentation to learn more about JWT authentication.

Vendor installation instructions

Note

This connector uses Azure Functions to connect to the Box REST API to pull 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 connector depends on a parser based on Kusto Function to work as expected BoxEvents which is deployed with the Microsoft Sentinel Solution.

STEP 1 - Configuration of the Box events collection

See documentation to setup JWT authentication and obtain JSON file with credentials.

STEP 2 - Choose ONE from the following two deployment options to deploy the connector and the associated Azure Function

IMPORTANT: Before deploying the Box data connector, have the Workspace ID and Workspace Primary Key (can be copied from the following), as well as the Box JSON configuration file, readily available.

Next steps

For more information, go to the related solution in the Azure Marketplace.