Edit

Fortinet FortiNDR Cloud (using Azure Functions) connector for Microsoft Sentinel

  • Article

The Fortinet FortiNDR Cloud data connector provides the capability to ingest Fortinet FortiNDR Cloud events stored in Amazon S3 into Microsoft Sentinel using the Amazon S3 REST API.

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

Connector attributes

Connector attribute Description
Kusto function alias Fortinet_FortiNDR_Cloud
Kusto function url https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/Solutions/Fortinet%20FortiNDR%20Cloud/Parsers/Fortinet_FortiNDR_Cloud.md
Log Analytics table(s) FncEventsSuricata_CL
FncEventsObservation_CL
FncEventsDetections_CL
Data collection rules support Not currently supported
Supported by Fortinet

Query samples

Fortinet FortiNDR Cloud Suricata Logs

FncEventsSuricata_CL

| sort by TimeGenerated desc

Fortinet FortiNDR Cloud Observation Logs

FncEventsObservation_CL

| sort by TimeGenerated desc

Fortinet FortiNDR Cloud Detections Logs

FncEventsDetections_CL

| sort by TimeGenerated desc

Prerequisites

To integrate with Fortinet FortiNDR Cloud (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.
  • MetaStream Credentials/permissions: AWS Access Key Id, AWS Secret Access Key, FortiNDR Cloud Account Code are required to retrieve event data.

Vendor installation instructions

Note

This connector uses Azure Functions to connect to the Amazon S3 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 uses a parser based on a Kusto Function to normalize fields. Follow these steps to create the Kusto function alias Fortinet_FortiNDR_Cloud.

STEP 1 - Configuration steps for the Fortinet FortiNDR Cloud Logs Collection

The provider should provide or link to detailed steps to configure the 'PROVIDER NAME APPLICATION NAME' API endpoint so that the Azure Function can authenticate to it successfully, get its authorization key or token, and pull the appliance's logs into Microsoft Sentinel.

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

IMPORTANT: Before deploying the Fortinet FortiNDR Cloud connector, have the Workspace ID and Workspace Primary Key (can be copied from the following), as well as the as well as the MetaStream credentials (available in FortiNDR Cloud account management), readily available.

Option 1 - Azure Resource Manager (ARM) Template

Use this method for automated deployment of the Fortinet FortiNDR Cloud connector.

  1. Click the Deploy to Azure button below.

    Deploy To Azure

  2. Select the preferred Subscription, Resource Group and Location.

  3. Enter the Workspace ID, Workspace Key, AwsAccessKeyId, AwsSecretAccessKey, and/or Other required fields.

  4. Click Create to deploy.

Option 2 - Manual Deployment of Azure Functions

Use the following step-by-step instructions to deploy the Fortinet FortiNDR Cloud connector manually with Azure Functions(Deployment via Visual Studio Code).

Next steps

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