本文档介绍了如何使用 API 或 Blob 存储将 Microsoft Intune 日志注入到 Google Security Operations。解析器会处理日志,将其转换为统一数据模型 (UDM)。它会提取字段,将其映射到 UDM 属性,处理各种活动类型(创建、删除、修补、操作),并使用设备信息、用户详细信息和安全结果等其他上下文来丰富数据。它还针对“重新配置 CloudPCModel”操作执行特定逻辑,并处理不同的身份场景。
准备工作
请确保满足以下前提条件:
Google SecOps 实例
有效的 Azure 租户
对 Azure 的特权访问权限
对 Microsoft Intune 的特权访问权限
使用 Azure 存储配置日志注入
本部分概述了配置从 Azure 存储注入日志的流程,以便您有效地收集和分析 Microsoft Intune 中的日志。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-09-04。"],[[["\u003cp\u003eThis document details the process of collecting Microsoft Intune logs within Google Security Operations by configuring a dedicated feed using the \u003ccode\u003eAZURE_MDM_INTUNE\u003c/code\u003e ingestion label.\u003c/p\u003e\n"],["\u003cp\u003eSetting up the feed requires specific Microsoft Azure credentials, including an OAuth client ID, OAuth client secret, and the tenant ID, along with configuring the diagnostic settings within the Microsoft endpoint manager.\u003c/p\u003e\n"],["\u003cp\u003eMicrosoft Intune log data is transformed into a structured UDM format upon ingestion, and this process involves mapping various log fields such as \u003ccode\u003eactivityDateTime\u003c/code\u003e, \u003ccode\u003eactivityType\u003c/code\u003e, and \u003ccode\u003eresources.0.resourceId\u003c/code\u003e to their corresponding UDM fields.\u003c/p\u003e\n"],["\u003cp\u003eThe document provides a comprehensive UDM Mapping Table, showcasing how different Microsoft Intune log fields are normalized into UDM fields, alongside the logic applied during the parsing process, ensuring a standardized representation of log data.\u003c/p\u003e\n"],["\u003cp\u003eThe document outlines important prerequisites to get started such as having an active Azure Subscription, an active Intune tenant, and having a global administrator role on that tenant.\u003c/p\u003e\n"]]],[],null,["# Collect Microsoft Azure MDM (Mobile Device Management) Intune logs\n==================================================================\n\nSupported in: \nGoogle secops [SIEM](/chronicle/docs/secops/google-secops-siem-toc)\n| **Note:** This feature is covered by [Pre-GA Offerings Terms](https://chronicle.security/legal/service-terms/) of the Google Security Operations Service Specific Terms. Pre-GA features might have limited support, and changes to pre-GA features might not be compatible with other pre-GA versions. For more information, see the [Google SecOps Technical Support Service guidelines](https://chronicle.security/legal/technical-support-services-guidelines/) and the [Google SecOps Service Specific Terms](https://chronicle.security/legal/service-terms/).\n\nThis document explains how to ingest Microsoft Intune logs to\nGoogle Security Operations using API or Blob Storage. The parser processes the logs,\ntransforming them into a Unified Data Model (UDM). It extracts fields, maps them\nto UDM attributes, handles various activity types (Create, Delete, Patch, Action),\nand enriches the data with additional context like device information,\nuser details, and security results. It also performs specific logic for\n\"Reprovision CloudPCModel\" operations and handles different identity scenarios.\n\nBefore you begin\n----------------\n\nMake sure you have the following prerequisites:\n\n- Google SecOps instance\n- Active Azure tenant\n- Privileged access to Azure\n- Privileged access to Microsoft Intune\n\nConfigure log ingestion using Azure Storage\n-------------------------------------------\n\nThis section outlines the process of configuring log ingestion from Azure\nStorage, enabling you to effectively collect and analyze logs from Microsoft Intune.\n\n### Configure the Azure Storage Account\n\n1. In the Azure console, search for Storage accounts.\n2. Click **Create**.\n3. Specify values for the following input parameters:\n - **Subscription**: select the subscription.\n - **Resource Group**: select the resource group.\n - **Region**: select the region.\n - **Performance**: select the chosen performance (Standard recommended).\n - **Redundancy**: select the chosen redundancy (GRS or LRS recommended).\n - **Storage account name**: enter a name for the new Storage account.\n4. Click **Review + create**.\n5. Review the overview of the account and click **Create**.\n6. From the **Storage Account Overview** page, select submenu **Access keys** in **Security + networking**.\n7. Click **Show** next to **key1** or **key2**.\n8. Click **Copy to clipboard** to copy the key.\n9. Save the key in a secure location for future reference.\n10. From the **Storage Account Overview** page, select submenu **Endpoints** in **Settings**.\n11. Click **Copy to clipboard** to copy the **Blob service** endpoint URL, (for example, `https://\u003cstorageaccountname\u003e.blob.core.windows.net`).\n12. Save the endpoint URL in a secure location for future reference.\n\n### Configure Log Export for Microsoft Intune Logs\n\n1. Sign in to the [**Microsoft Intune**](/chronicle/docs/ingestion/default-parsers/intune.microsoft.com) web UI.\n2. Go to **Reports \\\u003e Diagnostic settings**.\n3. Click **+ Add diagnostic setting**.\n4. Provide the following configuration details:\n - **Diagnostic setting name** : Enter a descriptive name (for example, `Intune logs to Google SecOps`)\n - Select the diagnostic settings for `AuditLogs`, `OperationalLogs`, `DeviceComplianceOrg` and `Devices`.\n - Select the **Archive to a storage account** checkbox as the destination.\n - Specify the **Subscription** and **Storage Account**.\n5. Click **Save**.\n\nSet up feeds\n------------\n\nTo configure a feed, follow these steps:\n\n1. Go to **SIEM Settings \\\u003e Feeds**.\n2. Click **Add New Feed**.\n3. On the next page, click **Configure a single feed**.\n4. In the **Feed name** field, enter a name for the feed (for example, `Azure Storage Audit Logs`).\n5. Select **Microsoft Azure Blob Storage V2** as the **Source type**.\n6. Select Azure Storage Audit as the **Log type**.\n7. Click **Next**.\n8. Specify values for the following input parameters:\n\n - **Azure uri**: the blob endpoint URL.\n\n `ENDPOINT_URL/BLOB_NAME`\n\n Replace the following:\n - `ENDPOINT_URL`: the blob endpoint URL. (`https://\u003cstorageaccountname\u003e.blob.core.windows.net`)\n - `BLOB_NAME`: the name of the blob. (such as, `\u003clogname\u003e-logs`)\n - **Source deletion options**: select deletion option according to your preference.\n\n | **Note:** If you select the `Delete transferred files` or `Delete transferred files and empty directories` option, make sure that you granted appropriate permissions to the service account. \\* **Maximum File Age** : Includes files modified in the last number of days. Default is 180 days. \\* **Shared key**: the access key to the Azure Blob Storage.\n9. Click **Next**.\n\n10. Review your new feed configuration in the **Finalize** screen, and then click **Submit**.\n\nConfigure log ingestion using API\n---------------------------------\n\nThis section details the initial steps for setting up an application\nwithin Azure Active Directory to enable API-based log ingestion.\n\n### Configure an App on Azure AD\n\n1. Sign in to the **Azure Portal**.\n2. Optional: If you have access to multiple tenants, use the **Directories + subscriptions** in the top menu to switch to the correct tenant.\n3. Search for and select **Azure Active Directory**.\n4. Go to **Manage \\\u003e App registrations \\\u003e New registration**.\n5. Provide the following configuration details:\n - Enter a **Display Name** for the application.\n - Specify who can access the application.\n - Optional: Don't enter anything for **Redirect URI**.\n - Click **Register**.\n6. Copy and Save the **Application (client) ID** and **Directory (tenant) ID** from the **Overview** screen.\n\n### Configure Client Secret\n\n1. In **App Registrations**, select your new application.\n2. Go to **Manage \\\u003e Certificates \\& secrets \\\u003e Client secrets \\\u003e New client secret**.\n3. Add a **name** for your client secret.\n4. Add an **expiration** period of **2 Years** for the secret or specify a **custom** period.\n5. Click **Add**.\n6. **Copy** and **Save** the **Secret Value**.\n\n### Configure App Permissions\n\n1. In App Registrations, select your new application.\n2. Go to **Manage \\\u003e API Permissions \\\u003e Add a permission**.\n3. Select **Microsoft Graph**.\n4. Add the following **Application** permissions:\n - DeviceManagementApps.Read.All\n - DeviceManagementConfiguration.Read.All\n - DeviceManagementManagedDevices.Read.All\n - DeviceManagementRBAC.Read.All\n - DeviceManagementServiceConfig.Read.All\n - AuditLog.Read.All\n - Device.Read.All\n5. Click **Add permissions**.\n\n| **Important:** After adding permissions, you must click **Grant admin consent** for your tenant to consent to these application permissions (Requires a Global Administrator role).\n\nConfigure a feed in Google SecOps to ingest Microsoft Intune logs\n-----------------------------------------------------------------\n\n1. Go to **SIEM Settings \\\u003e Feeds**.\n2. Click **Add New**.\n3. In the **Feed name** field, enter a name for the feed (for example, **Microsoft Intune Logs**).\n4. Select **Third party API** as the **Source type**.\n5. Select **Microsoft Intune** as the **Log type**.\n6. Click **Next**.\n7. Specify values for the following input parameters:\n - **OAuth Client ID**: Enter the Application ID copied earlier.\n - **OAuth Client Secret**: Enter the Secret Value created earlier.\n - **Tenant ID**: Enter the Directory ID copied earlier.\n - **Asset namespace**: the \\[asset namespace\\] (/chronicle/docs/investigation/asset-namespaces).\n - **Ingestion labels**: the label applied to the events from this feed.\n8. Click **Next**.\n9. Review the feed configuration in the **Finalize** screen, and then click **Submit**.\n\nUDM mapping table\n-----------------\n\n**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/google-security-operations-2)"]]