🚫 🔍 [Deprecated] FireEye Network Security (NX) via AMA

🚫 Deprecated: This connector has been deprecated and may be removed in future versions.

🔍 Discovered: This item was discovered by scanning the solution folder but is not listed in the Solution JSON file.

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

↑ Back to Connectors Index

Attribute Value
Connector ID FireEyeNXAma
Publisher FireEye
Used in Solutions FireEye Network Security
Collection Method AMA
Connector Definition Files template_FireEyeNX_CEFAMA.json

The FireEye Network Security (NX) data connector provides the capability to ingest FireEye Network Security logs into Microsoft Sentinel.

Tables Ingested

This connector ingests data into the following tables:

Table Selection Criteria Transformations Ingestion API Lake-Only
CommonSecurityLog DeviceVendor == "FireEye" ✓ ✓ ?

💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.

Permissions

Resource Provider Permissions: - Workspace (Workspace): read and write permissions are required. - Keys (Workspace): read permissions to shared keys for the workspace are required. See the documentation to learn more about workspace keys.

Custom Permissions:

Setup Instructions

⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.

NOTE: This data connector depends on a parser based on a Kusto Function to work as expected FireEyeNXEvent which is deployed with the Microsoft Sentinel Solution. 1. Kindly follow the steps to configure the data connector

Step A. Configure the Common Event Format (CEF) via AMA data connector

Note:- CEF logs are collected only from Linux Agents

  1. Navigate to Microsoft Sentinel workspace ---> configuration ---> Data connector blade .

  2. Search for 'Common Event Format (CEF) via AMA' data connector and open it.

  3. Check If there is no existing DCR configured to collect required facility of logs, Create a new DCR (Data Collection Rule)

    Note:- It is recommended to install minimum 1.27 version of AMA agent Learn more and ensure there is no duplicate DCR as it can cause log duplicacy

  4. Run the command provided in the CEF via AMA data connector page to configure the CEF collector on the machine

Step B. Configure FireEye NX to send logs using CEF

Complete the following steps to send data using CEF:

2.1. Log into the FireEye appliance with an administrator account

2.2. Click Settings

2.3. Click Notifications

Click rsyslog

2.4. Check the Event type check box

2.5. Make sure Rsyslog settings are:

Step C. Validate connection

Follow the instructions to validate your connectivity:

Open Log Analytics to check if the logs are received using the CommonSecurityLog schema.

It may take about 20 minutes until the connection streams data to your workspace.

If the logs are not received, run the following connectivity validation script:

  1. Make sure that you have Python on your machine using the following command: python -version

  2. You must have elevated permissions (sudo) on your machine - Run the following command to validate your connectivity:: sudo wget -O Sentinel_AMA_troubleshoot.py https://raw.githubusercontent.com/Azure/Azure-Sentinel/master/DataConnectors/Syslog/Sentinel_AMA_troubleshoot.py&&sudo python Sentinel_AMA_troubleshoot.py --cef

2. Secure your machine

Make sure to configure the machine's security according to your organization's security policy

Learn more >

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

↑ Back to Connectors Index