Panduan ini menjelaskan cara mengekspor log Azure VPN ke Google Security Operations menggunakan Akun Penyimpanan Azure. Parser mengekstrak kolom dari log Azure VPN berformat JSON, lalu menggunakan pola Grok untuk mengekstrak detail lebih lanjut dari kolom properties.message. Terakhir, informasi yang diekstrak dipetakan ke kolom standar Model Data Terpadu (UDM).
Label Penyerapan: Label yang diterapkan ke semua peristiwa dari feed ini.
Klik Buat feed.
Untuk mengetahui informasi selengkapnya tentang cara mengonfigurasi beberapa feed untuk berbagai jenis log dalam keluarga produk ini, lihat Mengonfigurasi feed menurut produk.
Tabel Pemetaan UDM
Kolom Log
Pemetaan UDM
Logika
category
security_result.category_details
Dipetakan langsung dari kolom category dalam log mentah.
IV_PLAT
security_result.detection_fields.value
Dipetakan langsung dari kolom IV_PLAT dalam log mentah. Bagian dari key-value pair dalam array detection_fields, dengan kuncinya adalah IV_PLAT.
IV_PLAT_VER
security_result.detection_fields.value
Dipetakan langsung dari kolom IV_PLAT_VER dalam log mentah. Bagian dari key-value pair dalam array detection_fields, dengan kuncinya adalah IV_PLAT_VER.
IV_PROTO
security_result.detection_fields.value
Dipetakan langsung dari kolom IV_PROTO dalam log mentah. Bagian dari key-value pair dalam array detection_fields, dengan kuncinya adalah IV_PROTO.
IV_VER
security_result.detection_fields.value
Dipetakan langsung dari kolom IV_VER dalam log mentah. Bagian dari key-value pair dalam array detection_fields, dengan kuncinya adalah IV_VER.
level
security_result.severity
Dipetakan dari kolom level dalam log mentah. Jika level adalah Informational, severity disetel ke INFORMATIONAL.
local_ip
target.ip
Diekstrak dari kolom properties.message menggunakan pola grok dan dipetakan ke alamat IP target.
local_port
target.port
Diekstrak dari kolom properties.message menggunakan pola grok dan dipetakan ke nomor port target. Dikonversi ke jenis bilangan bulat.
operationName
metadata.product_event_type
Dipetakan langsung dari kolom operationName dalam log mentah.
properties.message
metadata.description
Diekstrak dari kolom properties.message menggunakan pola grok. Bergantung pada format pesan, deskripsi dapat mencakup detail tambahan yang diekstrak dari kolom desc2.
remote_ip
principal.ip
Diekstrak dari kolom properties.message menggunakan pola grok dan dipetakan ke alamat IP utama.
remote_port
principal.port
Diekstrak dari kolom properties.message menggunakan pola grok dan dipetakan ke nomor port utama. Dikonversi ke jenis bilangan bulat.
resourceid
target.resource.product_object_id
Dipetakan langsung dari kolom resourceid dalam log mentah.
waktu
timestamp, metadata.event_timestamp
Diuraikan dari kolom time dalam log mentah menggunakan format RFC 3339 dan dipetakan ke stempel waktu peristiwa dan stempel waktu UDM.
metadata.log_type
Hardcode ke AZURE_VPN.
metadata.vendor_name
Hardcode ke AZURE.
metadata.product_name
Hardcode ke VPN.
metadata.event_type
Ditetapkan secara dinamis berdasarkan keberadaan alamat IP. Jika remote_ip dan local_ip ada, nilai ini ditetapkan ke NETWORK_CONNECTION, jika tidak, nilai ini ditetapkan ke USER_RESOURCE_ACCESS.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eThis guide explains the process of exporting Azure VPN logs to Google Security Operations using an Azure Storage Account.\u003c/p\u003e\n"],["\u003cp\u003eAzure VPN logs are parsed to extract fields from JSON format, with further detail extraction from the \u003cstrong\u003eproperties.message\u003c/strong\u003e field using Grok patterns.\u003c/p\u003e\n"],["\u003cp\u003eThe extracted Azure VPN log information is mapped to standardized fields in the Unified Data Model (UDM) for analysis within Google SecOps.\u003c/p\u003e\n"],["\u003cp\u003eConfiguration steps include setting up an Azure Storage Account, enabling log export for Azure VPN Gateway logs, and configuring a feed in Google SecOps.\u003c/p\u003e\n"],["\u003cp\u003eThe UDM Mapping Table describes how specific log fields from Azure VPN logs are translated into UDM fields, including dynamic settings based on the presence of IP addresses for the \u003ccode\u003emetadata.event_type\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Collect Azure VPN 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 guide explains how to export Azure VPN logs to Google Security Operations using an Azure Storage Account. The parser extracts fields from JSON-formatted Azure VPN logs and then uses Grok patterns to extract further details from the **properties.message** field. Finally, it maps the extracted information to the standardized fields of the Unified Data Model (UDM).\n\nBefore you begin\n----------------\n\nEnsure you have the following prerequisites:\n\n- Google SecOps instance\n- An active Azure tenant\n- Privileged access to Azure\n\nConfigure Azure Storage Account\n-------------------------------\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 performance (Standard recommended).\n - **Redundancy**: Select the 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 the **Access keys** submenu 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 later use.\n10. From the **Storage Account Overview** page, select the **Endpoints** submenu 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 later use.\n\nHow to configure Log Export for Azure VPN Gateway Logs\n------------------------------------------------------\n\n1. Sign in to the **Azure Portal** using your privileged account.\n2. Select the **Subscription** being monitored.\n3. In the resource list of that subscription, locate the VPN gateway (this should typically be of the Resource Type, Virtual Network Gateway).\n4. Click the Gateway.\n5. Select **Monitoring \\\u003e Diagnostic Services**.\n6. Click **+ Add diagnostic setting** .\n - Enter a descriptive name for the diagnostic setting.\n7. Select **allLogs**.\n8. Select the **Archive to a storage account** checkbox as the destination.\n - Specify the **Subscription** and **Storage Account**.\n9. Click **Save**.\n\nSet up feeds\n------------\n\nThere are two different entry points to set up feeds in the\nGoogle SecOps platform:\n\n- **SIEM Settings \\\u003e Feeds \\\u003e Add New**\n- **Content Hub \\\u003e Content Packs \\\u003e Get Started**\n\nHow to set up the Azure VPN feed\n--------------------------------\n\n1. Click the **Azure Platform** pack.\n2. Locate the **Azure VPN** log type and click **Add new feed**.\n3. Specify values for the following fields:\n\n - **Source Type**: Microsoft Azure Blob Storage V2.\n - **Azure URI** : The blob endpoint URL.\n - `ENDPOINT_URL/BLOB_NAME`\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 the deletion option according to your ingestion preferences.\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.\n - **Maximum File Age**: Includes files modified in the last number of days.\n Default is 180 days.\n\n - **Shared key**: The access key to the Azure Blob Storage.\n\n **Advanced options**\n - **Feed Name**: A prepopulated value that identifies the feed.\n - **Asset Namespace** : [Namespace associated with the feed](/chronicle/docs/investigation/asset-namespaces).\n - **Ingestion Labels**: Labels applied to all events from this feed.\n4. Click **Create feed**.\n\n| **Note:** The Content Hub is not available on the SIEM standalone platform. To upgrade, contact your Google SecOps representative.\n\nFor more information about configuring multiple feeds for different log types within this product family, see [Configure feeds by product](/chronicle/docs/ingestion/ingestion-entities/configure-multiple-feeds).\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)"]]
