找到 config.yaml 文件。通常,它位于 Linux 上的 /etc/bindplane-agent/ 目录中或 Windows 上的安装目录中。
使用文本编辑器(例如 nano、vi 或记事本)打开该文件。
按如下方式修改 config.yaml 文件:
receivers:udplog:# Replace the port and IP address as requiredlisten_address:"0.0.0.0:514"exporters:chronicle/chronicle_w_labels:compression:gzip# Adjust the path to the credentials file you downloaded in Step 1creds_file_path:'/path/to/ingestion-authentication-file.json'# Replace with your actual customer ID from Step 2customer_id:<customer_id>
endpoint:malachiteingestion-pa.googleapis.com# Add optional ingestion labels for better organizationingestion_labels:log_type:'ENDPOINT_PROTECTOR_DLP'raw_log_field:bodyservice:pipelines:logs/source0__chronicle_w_labels-0:receivers:-udplogexporters:-chronicle/chronicle_w_labels
将 Content Policy Type 的值分配给 security_result.rule_id。
Destination
metadata.ingestion_labels.value
Destination 的值会分配给 ingestion_labels 对象的 value 字段,其中 key 为“目的地”。
Destination Type
metadata.ingestion_labels.value
Destination Type 的值会分配给 ingestion_labels 对象的 value 字段,其中 key 为“目的地类型”。
Device PID
metadata.ingestion_labels.value
Device PID 的值会分配给 ingestion_labels 对象的 value 字段,其中 key 为“设备 PID”。
Device Serial
metadata.ingestion_labels.value
Device Serial 的值会分配给 ingestion_labels 对象的 value 字段,其中 key 为“设备序列号”。仅当 Device Serial 不为空时才执行此操作。
Device VID
metadata.ingestion_labels.value
Device VID 的值会分配给 ingestion_labels 对象的 value 字段,其中 key 为“设备 VID”。
File Name
target.file.full_path
将 File Name 的值分配给 target.file.full_path。
File Size
target.file.size
File Size 的值会赋给 target.file.size 并转换为无符号整数。
IP Address
principal.ip
将 IP Address 的值分配给 principal.ip。
Item Details
metadata.ingestion_labels.value
Item Details 的值会分配给 ingestion_labels 对象的 value 字段,其中 key 为“商品详情”。
Log ID
metadata.product_log_id
将 Log ID 的值分配给 metadata.product_log_id。
MAC Address
principal.mac
在将所有连字符替换为英文冒号后,MAC Address 的值会分配给 principal.mac。
Matched Item
metadata.ingestion_labels.value
Matched Item 的值会分配给 ingestion_labels 对象的 value 字段,其中 key 为“匹配的商品”。
Message
security_result.summary
将 Message 的值分配给 security_result.summary。
OS
principal.platform
OS 的值用于确定 principal.platform 的值。如果 OS 包含“Windows”,则将 principal.platform 设置为“WINDOWS”。如果 OS 包含“Mac”,则将 principal.platform 设置为“MAC”。如果 OS 包含“Lin”,则将 principal.platform 设置为“LINUX”。
[[["易于理解","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。"],[],[],null,["# Collect Endpoint Protector DLP 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 Netwrix Endpoint Protector DLP\n(Data Loss Protection) logs to Google Security Operations using Bindplane.\nThe parser extracts fields from the syslog messages, leveraging grok patterns to\nidentify key information. It then maps these extracted fields to the Unified\nData Model (UDM), handling various data types and enriching the output with\nmetadata like vendor and product information. The parser also performs several\ndata transformations, including string manipulation and conditional merging of\nfields based on operating system and other criteria.\n\nBefore you begin\n----------------\n\nMake sure you have the following prerequisites:\n\n- Google SecOps instance\n- Windows 2016 or later, or a Linux host with `systemd`\n- If running behind a proxy, firewall [ports](/chronicle/docs/ingestion/use-bindplane-agent#verify_the_firewall_configuration) are open\n- Privileged access to Netwrix Endpoint Protector\n\nGet Google SecOps ingestion authentication file\n-----------------------------------------------\n\n1. Sign in to the Google SecOps console.\n2. Go to **SIEM Settings \\\u003e Collection Agents**.\n3. Download the **Ingestion Authentication File**. Save the file securely on the system where Bindplane will be installed.\n\nGet Google SecOps customer ID\n-----------------------------\n\n1. Sign in to the Google SecOps console.\n2. Go to **SIEM Settings \\\u003e Profile**.\n3. Copy and save the **Customer ID** from the **Organization Details** section.\n\nInstall the Bindplane agent\n---------------------------\n\nInstall the Bindplane agent on your Windows or Linux operating system according\nto the following instructions.\n\n### Windows installation\n\n1. Open the **Command Prompt** or **PowerShell** as an administrator.\n2. Run the following command:\n\n msiexec /i \"https://github.com/observIQ/bindplane-agent/releases/latest/download/observiq-otel-collector.msi\" /quiet\n\n### Linux installation\n\n1. Open a terminal with root or sudo privileges.\n2. Run the following command:\n\n sudo sh -c \"$(curl -fsSlL https://github.com/observiq/bindplane-agent/releases/latest/download/install_unix.sh)\" install_unix.sh\n\n### Additional installation resources\n\nFor additional installation options, consult the [installation guide](/chronicle/docs/ingestion/use-bindplane-agent#install_the_bindplane_agent).\n\nConfigure the Bindplane agent to ingest Syslog and send to Google SecOps\n------------------------------------------------------------------------\n\n1. Access the configuration file:\n - Locate the `config.yaml` file. Typically, it's in the `/etc/bindplane-agent/` directory on Linux or in the installation directory on Windows.\n - Open the file using a text editor (for example, `nano`, `vi`, or Notepad).\n2. Edit the `config.yaml` file as follows:\n\n receivers:\n udplog:\n # Replace the port and IP address as required\n listen_address: \"0.0.0.0:514\"\n\n exporters:\n chronicle/chronicle_w_labels:\n compression: gzip\n # Adjust the path to the credentials file you downloaded in Step 1\n creds_file_path: '/path/to/ingestion-authentication-file.json'\n # Replace with your actual customer ID from Step 2\n customer_id: \u003ccustomer_id\u003e\n endpoint: malachiteingestion-pa.googleapis.com\n # Add optional ingestion labels for better organization\n ingestion_labels:\n log_type: 'ENDPOINT_PROTECTOR_DLP'\n raw_log_field: body\n\n service:\n pipelines:\n logs/source0__chronicle_w_labels-0:\n receivers:\n - udplog\n exporters:\n - chronicle/chronicle_w_labels\n\n - Replace the port and IP address as required in your infrastructure.\n - Replace `\u003ccustomer_id\u003e` with the actual customer ID.\n - Update `/path/to/ingestion-authentication-file.json` to the path where the authentication file was saved in the [Get Google SecOps ingestion authentication file](/chronicle/docs/ingestion/default-parsers/endpoint-protector-dlp#get-auth-file) section.\n\nRestart the Bindplane agent to apply the changes\n------------------------------------------------\n\n- To restart the Bindplane agent in Linux, run the following command:\n\n sudo systemctl restart bindplane-agent\n\n- To restart the Bindplane agent in Windows, you can either use the **Services**\n console or enter the following command:\n\n net stop BindPlaneAgent && net start BindPlaneAgent\n\nConfigure Syslog on Netwrix Endpoint Protector\n----------------------------------------------\n\n1. Sign in to the **Endpoint Protector** web UI.\n2. Go to **Appliance \\\u003e SIEM Integration**.\n3. Click **Add New**.\n4. Provide the following configuration details:\n - **SIEM Status** : Toggle switch to **enable** the SIEM server.\n - **Disable Logging** : Toggle switch to **enable** logging.\n - **Server Name**: Enter a unique and meaningful server name.\n - **Server Description**: Add a description for this integration.\n - **Server IP or DNS**: Enter the Bindplane agent IP address.\n - **Server Protocol** : Select **UDP**.\n - **Server Port** : Enter the Bindplane agent port number (for example, `514` for UDP).\n - **Exclude Headers** : Toggle switch to **enable** log headers.\n - **Log Types**: Select the available logs to send to the SIEM.\n5. Click **Save**.\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)"]]