microsoft/dhcp-client

VendorMicrosoft Corporation
AuthorCrowdStrike
Version1.1.0
Minimum LogScale Version1.82.0

Dynamic Host Configuration Protocol (DHCP) is a standard protocol defined by RFC 1541 that allows servers to distribute IP addressing and configuration information. This package provides a parser for Microsoft DHCP client logs. Augment your end point monitoring coverage by ingesting this data to LogScale.

This package provides a parser for DHCP client events in JSON format.

Breaking Changes

This update includes parser changes, which means that data ingested after upgrade will not be backwards compatible with logs ingested with the previous version.

Updating to version 1.0.0 or newer will therefore result in issues with existing queries in for example dashboards or alerts created prior to this version.

See CrowdStrike Parsing Standard (CPS) 1.0 for more details on the new parser schema.

Follow the CPS Migration to update your queries to use the fields and tags that are available in data parsed with version 1.0.0.

Installing the DHCP Client Package in LogScale

There is no installation process for dhcp-client. An IP address will ensure that it is running on all endpoints by default. To install the package in LogScale:

  1. Find the repository where you want to send the logs, or create a new one.

  2. Navigate to your repository in the LogScale interface, click Settings and then Packages on the left.

  3. Click Marketplace and install the LogScale package for Microsoft DHCP Client (i.e. microsoft/dhcp-client).

  4. When the package has finished installing, click Ingest tokens on the left (still under the Settings, see Ingest Tokens).

  5. In the right panel, click + Add Token to create a new token. Give the token an appropriate name (e.g.the name of the server and the name of the server the token is ingesting logs for), and assign the parser to microsoft-windows-dhcp-client. You can assign the parser to the LogScale Collector Configuration as described in the documentation: Windows Event Log Example

    Before leaving this page, view the ingest token and copy it to your clipboard — to save it temporarily elsewhere.

Now that you have a repository set up in LogScale along with an ingest token you're ready to send logs to LogScale.

Next, configure the Falcon LogScale Collector to ship the logs into LogScale. Follow LogScale Collector Download and Install Falcon Log Collector Using Curl Commands(Full Install) and Configure Falcon Log Collector. LogScale Collector documentation also provides an example of how you can configure your datasource- see our Windows Event Log Example.

DHCP Client Log Configuration

Use the following configuration to collect DHCP Client logs: 

sources:
  dhcp:
    type: wineventlog
    channels:
      - name: Microsoft-Windows-Dhcpv6-Client/Operational
      - name: Microsoft-Windows-Dhcpv6-Client/Admin
      - name: Microsoft-Windows-Dhcp-Client/Operational
      - name: Microsoft-Windows-Dhcp-Client/Admin
    includeXML: false
    language: 1033
    sink: logscale
sinks:
  logscale:
    type: humio
    token: <your token>
    url: http://localhost:8080

To enable the required logging:

  1. Open Event Viewer (eventvwr)

  2. Click Applications and Services Logs → Microsoft → Windows → Dhcp-Client and Applications and Services Logs → Microsoft → Windows → DHCPv6-Client

  3. Click Enable Log

Verify Data is Arriving in LogScale

Once you have completed the above steps the data should be arriving in your LogScale repository.

You can verify this by doing a simple search for #Vendor = "microsoft" | #event.module = "dhcp-clent" | #event.dataset := "windows.dhcp-client" to see the events.