An ingestion label identifies the parser that normalizes raw log data to structured
UDM format. The information in this document applies to the parser with the
FIREEYE_NX ingestion label.
Configure FireEye NX
Sign in to the FireEye NX interface.
Go to Settings > Notifications.
To enable a syslog notification configuration, select the rsyslog checkbox.
Click Add rsyslog server.
In the Name field, enter a name to label your FireEye connection to the Google SecOps instances.
In the IP address field, enter the Google SecOps forwarder IP address.
Select the Enabled checkbox.
In the Delivery list, select Per event.
In the Notifications list, select All events.
In the Format list, select CEF.
In the Account field, don't enter any information.
In the Protocol list, select the protocol.
Click Add new rsyslog server.
Configure the Google SecOps forwarder to ingest FireEye NX logs
In the Google SecOps menu, select Settings > Forwarders > Add new forwarder.
In the Forwarder name field, enter a unique name for the forwarder.
Click Submit. The forwarder is added and the Add collector configuration
window appears.
In the Collector name field, enter a unique name for the collector.
In the Log type field, specify FireEye NX.
Select Syslog as the Collector type.
Configure the following input parameters:
Protocol: specify the connection protocol that the collector uses to listen
to syslog data.
Address: specify the target IP address or hostname where the collector
resides and listens to syslog data.
Port: specify the target port where the collector resides and listens
to syslog data.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Collect FireEye NX 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 the FireEye Network Security and Forensics (NX) logs by using a Google Security Operations forwarder.\n\nFor more information, see [Data ingestion to Google SecOps overview](/chronicle/docs/data-ingestion-flow).\n\nAn ingestion label identifies the parser that normalizes raw log data to structured\nUDM format. The information in this document applies to the parser with the\n`FIREEYE_NX` ingestion label.\n\nConfigure FireEye NX\n--------------------\n\n1. Sign in to the FireEye NX interface.\n2. Go to **Settings \\\u003e Notifications**.\n3. To enable a syslog notification configuration, select the **rsyslog** checkbox.\n4. Click **Add rsyslog server**.\n5. In the **Name** field, enter a name to label your FireEye connection to the Google SecOps instances.\n6. In the **IP address** field, enter the Google SecOps forwarder IP address.\n7. Select the **Enabled** checkbox.\n8. In the **Delivery** list, select **Per event**.\n9. In the **Notifications** list, select **All events**.\n10. In the **Format** list, select **CEF**.\n11. In the **Account** field, don't enter any information.\n12. In the **Protocol** list, select the protocol.\n13. Click **Add new rsyslog server**.\n\n | **Note:** Ensure that you send syslog to the collector on a unique **UDP** or **TCP** port with port number **11583**.\n\nConfigure the Google SecOps forwarder to ingest FireEye NX logs\n---------------------------------------------------------------\n\n1. In the Google SecOps menu, select **Settings \\\u003e Forwarders \\\u003e Add new forwarder**.\n2. In the **Forwarder name** field, enter a unique name for the forwarder.\n3. Click **Submit** . The forwarder is added and the **Add collector configuration** window appears.\n4. In the **Collector name** field, enter a unique name for the collector.\n5. In the **Log type** field, specify `FireEye NX`.\n6. Select **Syslog** as the **Collector type**.\n7. Configure the following input parameters:\n - **Protocol**: specify the connection protocol that the collector uses to listen to syslog data.\n - **Address**: specify the target IP address or hostname where the collector resides and listens to syslog data.\n - **Port**: specify the target port where the collector resides and listens to syslog data.\n8. Click **Submit**.\n\nFor more information about the Google SecOps forwarders, see [Manage forwarder configurations through the Google SecOps UI](/chronicle/docs/install/forwarder-management-configurations).\n\nIf you encounter issues when you create forwarders, contact [Google SecOps support](https://console.cloud.google.com/support)."]]
