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

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more