Loading

Microsoft Sentinel

Version 1.3.0 (View all)
Subscription level
What's this?
Basic
Developed by
What's this?
Elastic
Ingestion method(s) API, Azure Event Hub
Minimum Kibana version(s) 9.3.0
9.2.4
9.1.10
8.19.10

Microsoft Sentinel is a scalable, cloud-native security information and event management (SIEM) system that delivers an intelligent and comprehensive solution for SIEM and security orchestration, automation, and response (SOAR). Microsoft Sentinel provides cyberthreat detection, investigation, response, and proactive hunting, with a bird's-eye view across your enterprise.

Use the Microsoft Sentinel integration to collect and parse Alerts and Incidents from Microsoft Sentinel REST API and Events from the Microsoft Azure Event Hub, then visualise the data in Kibana.

Agentless integrations allow you to collect data without having to manage Elastic Agent in your cloud. They make manual agent deployment unnecessary, so you can focus on your data instead of the agent that collects it. For more information, refer to Agentless integrations and the Agentless integrations FAQ.

Agentless deployments are only supported in Elastic Serverless and Elastic Cloud environments. This functionality is in beta and is subject to change. Beta features are not subject to the support SLA of official GA features.

The Microsoft Sentinel integration collects logs for three types of events: Alert, Event and Incident.

Alert: Alert allows collecting all alerts for an incident via API.

Incident: Incident allows collecting all incidents via API.

Event: Event allows collecting all alerts for an incident streamed to an Azure Event Hub.

Unless you choose Agentless deployment, the Elastic Agent must be installed. Elastic Agent must be installed. For more details, check the Elastic Agent installation instructions. You can install only one Elastic Agent per host.

For Rest API, this module has been tested against the 2024-03-01 version.

  1. Navigate to Log Analytics Workspace: From the Azure Portal's navigation menu, locate and select Log Analytics workspaces.
  2. Select your Workspace: Choose the Log Analytics workspace associated with your Azure Sentinel deployment.
  3. Navigate to Data Export: Within the Log Analytics workspace, locate and select the Data Export option. This is usually found in the settings menu.
  4. New Export Rule: Within Data export click on New export rule to create a new rule.
  5. Under Basic section: Provide a rule name for the data export rule.
  6. Under Source section: Select the tables you want to export data to storage account.
  7. Under Destination section: Provide the destination details like the Subscription name and Storage account name to which you want to export data.
  8. Review + Create: In the review + create section, select Create.
  1. Open Azure Portal and Register a new Azure Application.
  2. After the application has been created, it will generate Client ID, Client Secret and Tenant ID values that are required for data collection.
  3. To get Workspace Name, Subscription ID, and Resource Group navigate to Microsoft Sentinel and select desired workspace among the list.
  4. Go to Manage > API permissions in your portal, then add the following permissions for Microsoft Graph:
    • SecurityAlert.Read.All with both Application and Delegated permission types.
    • User.Read with the Delegated permission type.
  1. In the top search bar in Kibana, search for Integrations.
  2. In the search bar, type Microsoft Sentinel.
  3. Select the Microsoft Sentinel integration and add it.
  4. Add all the required integration configuration parameters:
    • REST API input type: URL, Login URL, Client ID, Client Secret, Tenant Id, Resource Group Name, Subscription ID, Workspace Name, Interval, and Initial Interval.
    • Azure Event Hub input type: Authentication type (Connection String or Client Secret). For Connection String: Consumer Group, Connection String, Storage Account, and Storage Account Key. For Client Secret: Azure Event Hub, Consumer Group, Tenant ID, Client ID, Client Secret, Event Hub namespace, plus Storage Account (and optional container). For client secret setup and required RBAC roles, see the Azure Logs integration or Filebeat azure-eventhub input documentation.
  5. Save the integration.

This is the Alert dataset.

This is the Event dataset.

This is the Incident dataset.

This integration includes one or more Kibana dashboards that visualizes the data collected by the integration. The screenshots below illustrate how the ingested data is displayed.