Windows DHCP Server (via Filebeat)

Our Integration guide was accurate at the time of writing but vendors change things frequently! If you find errors or anything is outdated, let us know by raising a request in the Samurai Help Center and we shall get it updated.

Use this document to install and configure the Filebeat agent to send Windows DHCP Server logs to Samurai using the Samurai Local Collector deployed in your network.

To complete this Integration you will need to:

1. Ensure the Samurai Logstash Integration is installed on the desired local collector
2. Ensure correct network connectivity
3. Download & Install Filebeat
4. Configure & Enable DHCP Server Audit Logging
5. Configure & Start Filebeat

 This guide is based on the premise of a single Samurai Local Collector installation with deployment of a single Windows host with the DHCP Server service enabled and configured. Repeat these steps outlined in this guide for each Windows DNS Server and site.

Ensure the Samurai Logstash Integration is installed on the desired local collector

Verify in the Samurai Application that the Samurai Logstash Integration is installed on the desired Samurai Local Collector:

1. Login to your Samurai Application tenant.
2. Click Telemetry > Integrations from the main menu.
3. Verify that an integration with Product set to the value Logstash exists on the desired collector. 
4. Note down the IP address of the Samurai Local Collector. This will be used later when configuring the Beat-agent.
   
   If no Logstash integration has been installed, use the following guide to have it installed: Samurai Logstash Integration.

Ensure correct network connectivity

You must ensure the following connectivity requirements are fulfilled:

Download & Install Filebeat

Perform the steps outlined in Step 1: Install Filebeat as per the vendor documentation.

 Make sure to click the Windows tab for OS selection.

Configure & Enable DHCP Server Audit Logging

 DHCP Server Audit Logging should be enabled by default and these steps are used to validate that logging is enabled and determine the logging path.

Configure via Powershell

1. To view the DHCP Audit logging config, run the command Get-DhcpServerAuditLog.

   PS C:\> Get-DhcpServerAuditLog
   
   Path : C:\Windows\system32\dhcp
   Enable : True
   MaxMBFileSize : 70
   DiskCheckInterval : 50
   MinMBDiskSpace : 20

2. Verify that the flag Enabled is set to True.
   1. In case logging is not enabled, run the commend Set-DhcpServerAuditLog. Example command with arguments is presented below.

      PS C:\> Set-DhcpServerAuditLog -Enable $True -Path C:\dhcp

   2. The DHCP server needs to be restarted after logging has been enabled, run the following command to restart the service.

      PS C:\> Restart-Service DHCPServer

3. Note down the file path that has been configured, this will be used later in the section Configure & Start Filebeat.

Configure & Start Filebeat

1. Access the Filebeat installation folder and open and edit the file filebeat.yml.
2. Modify the below template by replacing the section IP_OF_LOCAL_COLLECTOR with the IP address of the Samurai Local Collector running the Samurai Logstash Integration collected during the step Ensure the Samurai Logstash Integration is installed on the desired local collector.
3. Modify the paths section of the template to use the path that was configured for the DHCP Server Audit log file location from Configure & Enable Windows DHCP Server Audit Logging.
    Follow the vendor documentation when configuring the paths section.

   # ============================== Filebeat inputs ===============================
   filebeat.inputs:
   - type: filestream
   id: win_dhcp
   enabled: true
   paths:
   - 'C:\Windows\System32\dhcp\Dhcp*'
   include_lines: ['^\d+,(\d+\/){2}\d+,.*$']
   tags: [win_dhcp_server]
   
   # ------------------------------ Logstash Output -------------------------------
   output.logstash:
   hosts: ["IP_OF_LOCAL_COLLECTOR:5044"]

4. Replace the default configuration of filebeat.yml with the modified template and save the file.
5. Perform the steps outlined in Step 5: Start Filebeat as per the vendor documentation to start the service.
    Make sure to click the Windows tab for OS selection.