[[["易于理解","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 provides instructions on how to collect Forcepoint Data Loss Prevention (DLP) logs using a Google Security Operations forwarder, which are then parsed and mapped to the Unified Data Model (UDM) format.\u003c/p\u003e\n"],["\u003cp\u003eTo configure Forcepoint DLP, you must access the Forcepoint Security Manager console and specify the Google Security Operations forwarder's IP address or hostname and port in the syslog settings.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring the Google Security Operations forwarder involves creating a new forwarder, selecting "Forcepoint DLP" as the log type, and setting up Syslog as the collector type with the appropriate protocol, address, and port.\u003c/p\u003e\n"],["\u003cp\u003eThe parser extracts key information from Forcepoint DLP CEF logs and maps various fields like \u003ccode\u003efname\u003c/code\u003e, \u003ccode\u003edestinationHosts\u003c/code\u003e, \u003ccode\u003eproductVersion\u003c/code\u003e, and others to their corresponding UDM fields, as detailed in the provided UDM Mapping Table.\u003c/p\u003e\n"],["\u003cp\u003eThe parser has undergone several updates since it was first created, including mapping more fields, bug fixes, and support for new log formats.\u003c/p\u003e\n"]]],[],null,["# Collect Forcepoint 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 describes how you can collect Forcepoint Data Loss Prevention (DLP)\nlogs by using a Google Security Operations forwarder.\n\nFor more information, see [Data ingestion to Google Security Operations overview](/chronicle/docs/data-ingestion-flow).\n\nAn ingestion label identifies the parser which normalizes raw log data to structured\nUDM format. The information in this document applies to the parser with the\n`FORCEPOINT_DLP` ingestion label.\n\nConfigure Forcepoint DLP\n------------------------\n\n1. Sign in to the **Forcepoint Security Manager** console.\n2. In the **Additional actions** section, select the **Send syslog message** checkbox.\n3. In the **Data security** module, select **Settings** \\\u003e **General** \\\u003e **Remediation**.\n4. In the **Syslog settings** section, specify the following:\n - In the **IP address or hostname** field, enter the IP address or hostname of the Google Security Operations forwarder.\n - In the **Port** field, enter the port number.\n - Clear the **Use syslog facility for these messages** checkbox.\n5. To send the syslog server a verification test message, click **Test connection**.\n6. To save your changes, click **Ok**.\n\nConfigure the Google Security Operations forwarder to ingest Forcepoint DLP logs\n--------------------------------------------------------------------------------\n\n1. Go to **SIEM Settings** \\\u003e **Forwarders**.\n2. Click **Add new forwarder**.\n3. In the **Forwarder Name** field, enter a unique name for the forwarder.\n4. Click **Submit** . The forwarder is added and the **Add collector configuration** window appears.\n5. In the **Collector name** field, type a name.\n6. Select **Forcepoint DLP** as the **Log type**.\n7. Select **Syslog** as the **Collector type**.\n8. Configure the following mandatory input parameters:\n - **Protocol**: specify the connection protocol that the collector uses to listen for syslog data.\n - **Address**: specify the target IP address or hostname where the collector resides and listens for syslog data.\n - **Port**: specify the target port where the collector resides and listens for syslog data.\n9. Click **Submit**.\n\nFor more information about the Google Security Operations forwarders, see [Manage forwarder configurations through the Google Security Operations UI](/chronicle/docs/install/forwarder-management-configurations).\nIf you encounter issues when you create forwarders, contact [Google Security Operations support](/chronicle/docs/getting-support).\n\nField mapping reference\n-----------------------\n\nThis parser extracts key-value pairs from Forcepoint DLP CEF formatted logs, normalizing and mapping them to the UDM. It handles various CEF fields, including sender, recipient, actions, and severity, enriching the UDM with details like user information, affected files, and security results.\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)"]]