🚫 [Deprecated] WireX Network Forensics Platform via AMA
🚫 Deprecated: This connector has been deprecated and may be removed in future versions.
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊
| Attribute | Value |
|---|---|
| Connector ID | WireX_Systems_NFPAma |
| Publisher | WireX_Systems |
| Used in Solutions | WireX Network Forensics Platform |
| Collection Method | AMA |
| Connector Definition Files | template_WireXsystemsNFPAMA.json |
The WireX Systems data connector allows security professional to integrate with Microsoft Sentinel to allow you to further enrich your forensics investigations; to not only encompass the contextual content offered by WireX but to analyze data from other sources, and to create custom dashboards to give the most complete picture during a forensic investigation and to create custom workflows.
Tables Ingested
This connector ingests data into the following tables:
| Table | Selection Criteria | Transformations | Ingestion API | Lake-Only |
|---|---|---|---|---|
CommonSecurityLog |
DeviceProduct == "WireX NFP"DeviceVendor == "WireX" |
✓ | ✓ | ? |
💡 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.
Install and configure the Linux agent to collect your Common Event Format (CEF) Syslog messages and forward them to Microsoft Sentinel.
Notice that the data from all regions will be stored in the selected workspace 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
-
Navigate to Microsoft Sentinel workspace ---> configuration ---> Data connector blade .
-
Search for 'Common Event Format (CEF) via AMA' data connector and open it.
-
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
-
Run the command provided in the CEF via AMA data connector page to configure the CEF collector on the machine
Step B. Forward Common Event Format (CEF) logs to Syslog agent
Contact WireX support (https://wirexsystems.com/contact-us/) in order to configure your NFP solution to send Syslog messages in CEF format to the proxy machine. Make sure that they central manager can send the logs to port 514 TCP on the machine's IP address.
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:
-
Make sure that you have Python on your machine using the following command: python -version
-
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
Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊