When you configure Microsoft DHCP Server to send log data to USM Appliance, you can use the DHCP Client Service NXLog plugin to translate the raw log data into normalized events for analysis.
|Device Type||Client Service|
|Data Source Name||dhcp-nxlog|
|Data Source ID||1584|
Integrating Microsoft DHCP Server and NXLog
Before you configure Microsoft DHCP Server to send logs to USM Appliance through NXLog, you must have the IP Address of the USM Appliance Sensor.
To send log data through NXLog to USM Appliance
If not done already, download nxlog.conf, and then place it in the conf directory of your NXLog installation. Depending on which version you use, the directory can be C:\Program Files (x86)\nxlog\conf for the 32-bit version or C:\Program Files\nxlog\conf for the 64-bit version.
Note: This step overwrites the default nxlog.conf file. You may want to back up the original copy before placing the one provided by AlienVault.
- Open the nxlog.conf file in a text editor.
Update the root path of your NXLog installation.
Locate the following lines:
#define ROOT C:\Program Files\nxlog
#define ROOT C:\Program Files (x86)\nxlog
- Uncomment the path that matches the NXLog installation on your Windows machine.
Enter the USM Appliance Sensor IP address.
Locate the following line:
define OUTPUT_DESTINATION_ADDRESS <USM-Appliance-Sensor-IP>
- Replace <USM-Appliance-Sensor-IP> with the IP address of the USM Appliance All-in-One or USM Appliance Sensor that will receive the Windows events.
Uncomment the section between DHCP-NXLOG and /DHCP-NXLOG.
Important: Only remove the first # symbol in each line when uncommenting the sections. The remaining # symbol indicates that the line is either a comment or optional.
In addition, uncomment the following lines, above the DHCP-NXLOG section:
# Module xm_json
- Save the file.
- Start or restart the NXLog service.
For plugin enablement information, see Enable Plugins.
If enabling the plugin on assets, you will find it listed as Microsoft : DHCP Client Service : NXLog.
Additional Resources and Troubleshooting
For troubleshooting, refer to the vendor documentation: