Connect Microsoft 365 Defender to Azure Sentinel

By Ashwin Venugopal -

 




Plan for Microsoft 365 Defender Connectors

A purpose-driven user interface is provided by the Microsoft 365 security portal to mitigate threats detected by Microsoft 365 Defender whose products includes:
  • Microsoft Defender for Endpoint
  • Microsoft Defender for Identity
  • Microsoft Defender for Office 365
  • Microsoft Cloud App Security

Each of the products have a connector that is capable of sending alerts to the Security Alerts table in Sentinel. In the Microsoft 365 Defender connector only Microsoft Defender for Endpoint data is configurable currently.

Connect alerts from Microsoft Defender for Office 365

Microsoft Defender for Office 365 can easily safeguard your organization against malicious threats posed by email messages, links (URL), and collaboration tools with the help of following types of ingested alerts:
  • A potentially malicious URL click was detected
  • Email messages containing malware removed after delivery
  • Email messages containing phish URLs removed after delivery
  • Email reported by the user as malware or phish
  • Suspicious email sending patterns detected
  • User restricted from sending email

Connect alerts from Microsoft Defender for Endpoint

A security platform designed to prevent, detect, investigate, and respond to advanced threats is called Microsoft Defender for Endpoint that can create alerts when suspicious security events are seen in an organization. You can fetch alerts generated in Microsoft Defender ATP so that you can effectively analyze security events.

Connect the Microsoft 365 Defender connector

The Microsoft 365 Defender connector allows you to stream advanced hunting logs- a type of raw event data- from Microsoft 365 Defender into Azure Sentinel. By using the Microsoft 365 Defender connector, you can collect your Microsoft Defender for Endpoint advanced hunting events and stream them straight into new purpose-built tables in your Azure Sentinel workspace. These tables are built on the same schema that is used in the Microsoft 365 Defender portal, giving you complete access to the full set of advanced hunting logs and allowing you to do the following:
  • Easily copy your existing Microsoft Defender ATP advanced hunting queries into Azure Sentinel.

  • Use the raw event logs to provide more insights for your alerts, hunting, and investigation, as well as correlate events with data from other data sources in Azure Sentinel.

  • Store the logs with increased retention, beyond Microsoft Defender for Endpoint or Microsoft 365 Defender's default retention of 30 days. You can do so by configuring the retention of your workspace or by configuring per-table retention in Log Analytics.

The Microsoft Defender for Endpoint collection options are as follows:

Events type

Table name

Machine information (including OS information)

DeviceInfo

Network properties of machines

DeviceNetworkInfo

Process creation and related events

DeviceProcessEvents

Network connection and related events

DeviceNetworkEvents

File creation, modification, and other file system events

DeviceFileEvents

Creation and modification of registry entries

DeviceRegistryEvents

Sign-ins and other authentication events

DeviceLogonEvents

DLL loading events

DeviceImageLoadEvents

More events types

DeviceEvents

 










Comments

Post a Comment

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more