Documentation Center
AlienVault® USM Anywhere™

Microsoft Windows Exchange NXLog

When you configure Microsoft Exchange Server to send logs through NXLog to USM Anywhere, you can use the Windows Exchange NXLog plugin to translate the raw log data into normalized events for analysis.

Device Details
Device vendor Microsoft
Device type DHCP server
Connection type Syslog

Integrating NXLog for Microsoft Exchange Server

Before you configure the integration, you must have the IP Address of the USM Anywhere Sensor.

To install NXLog CE and configure forwarding

  1. Download the newest stable NXLog Community Edition.
  2. Make a backup copy of the original C:\Program Files (x86)\nxlog\conf\nxlog.conf file and give it another name.
  3. Download the NXLog configuration for USM Anywhere and save it as your new nxlog.conf file.
  4. Open the configuration file for editing and replace usmsensoriphere with the IP address of the USM Anywhere Sensor.
  5. USM Anywhere listens for syslog at UDP port 514, TCP port 601, or TLS/TCP port 6514. Depending on the protocol you decide to use, edit the configuration file as detailed below. Make sure USM Anywhere allows inbound requests to the corresponding port.

  6. Some sections in the nxlog.conf file have been commented out to improve performance. Depending on which product you want to collect logs from, you need to uncomment the corresponding section.

    • To collect logs from the Microsoft Exchange Server, uncomment the section between EXCHANGE-NXLOG and /EXCHANGE-NXLOG.
  7. Save the file.
  8. Open Windows Services and restart the NXLog service.
  9. Open USM Anywhere and verify that you are receiving NXLog events.

Note: If you need to debug NXLog, open C:\Program Files (x86)\nxlog\data\nxlog.log.

Plugin Enablement

The Windows DHCP NXLog plugin automatically processes all messages when the raw message contains "SourceName":"EXCHANGE NXLOG".

Available Plugin Fields

The following plugin fields are important attributes extracted from the syslog message. The USM Anywhere reports use these fields, and you can also reference them when creating custom reports. In addition to reporting, the USM Anywhere correlation rules make use of these fields.

  • bytes_in
  • bytes_out
  • customfield_0
  • customfield_1
  • customfield_2
  • customfield_3
  • customfield_4
  • customfield_5
  • customfield_6
  • customfield_7
  • customheader_0
  • customheader_1
  • customheader_2
  • customheader_3
  • customheader_4
  • customheader_5
  • customheader_6
  • customheader_7
  • destination_address
  • destination_address_6
  • destination_zone
  • destination_hostname
  • device_direction
  • email_recipient
  • email_sender
  • email_subject
  • event_name
  • external_id
  • source_address
  • source_address_6
  • source_hostname
  • source_zone
  • source_service_name
  • timestamp_occured

Troubleshooting

For troubleshooting, refer to the vendor documentation:

https://technet.microsoft.com/en-us/library/bb124558(v=exchg.150).aspx