Oracle Cloud Infrastructure (using Azure Functions) connector for Microsoft Sentinel

The Oracle Cloud Infrastructure (OCI) data connector provides the capability to ingest OCI Logs from OCI Stream into Microsoft Sentinel using the OCI Streaming REST API.

Connector attributes

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

Query samples

All OCI Events

OCI_Logs_CL

| sort by TimeGenerated desc

Prerequisites

To integrate with Oracle Cloud Infrastructure (using Azure Functions) make sure you have:

Vendor installation instructions

Note

This connector uses Azure Functions to connect to the Azure Blob Storage API to pull logs 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 and Azure Blob Storage 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 OCILogs which is deployed with the Microsoft Sentinel Solution.

STEP 1 - Creating Stream

  1. Log in to OCI console and go to navigation menu -> Analytics & AI -> Streaming
  2. Click Create Stream
  3. Select Stream Pool or create a new one
  4. Provide the Stream Name, Retention, Number of Partitions, Total Write Rate, Total Read Rate based on your data amount.
  5. Go to navigation menu -> Logging -> Service Connectors
  6. Click Create Service Connector
  7. Provide Connector Name, Description, Resource Compartment
  8. Select Source: Logging
  9. Select Target: Streaming
  10. (Optional) Configure Log Group, Filters or use custom search query to stream only logs that you need.
  11. Configure Target - select the strem created before.
  12. Click Create

Check the documentation to get more information about Streaming and Service Connectors.

STEP 2 - Creating credentials for OCI REST API

Follow the documentation to create Private Key and API Key Configuration File.

IMPORTANT: Save Private Key and API Key Configuration File created during this step as they will be used during deployment step.

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

IMPORTANT: Before deploying the OCI data connector, have the Workspace ID and Workspace Primary Key (can be copied from the following), as well as OCI API credentials, readily available.

Next steps

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