Installing Agent

Introduction

This article is a guide to demonstrate how to install winlogbeat.exe agent on your end-points to start ingesting logs to the SIEM. Winlogbeat is a lightweight Windows service, part of the Elastic Beats family, designed to ship Windows event logs (Application, System, Security) to OpenSearch.


Cybersift recommends only onboarding your corporate servers rather than all of your endpoints to prevent throttling your network.


Refer to our other articles for deployment via group policy (GPO) if you require it.

Requirements

  • If your SIEM is on Cybersift Cloud, please let support know the public IP from which data will be sent.


Downloading the Agent

  1. Download and install Winlogbeat:

  2. Configuration:

    • After installation, replace the default winlogbeat.yml config file with the provided configuration.


A note on Windows Event Forwarding

In order for winlogbeat to pick up forwarded logs, you will need to add the following lines at the bottom of this snippet to your winlogbeat configuration:

winlogbeat.event_logs: # feel free to add any additional logs you need below
  - name: Application
    ignore_older: 72h
    language: 0x0409 # en-US
  - name: Security
    language: 0x0409 # en-US
  - name: System
    language: 0x0409 # en-US
  - name: Microsoft-Windows-PowerShell/Operational
    event_id: 4103,4104
  - name: Microsoft-Windows-WMI-Activity/Operational
    event_id: 5858,5861,5862
  - name: ForwardedEvents # <---------- NEW SECTION starts here
    ignore_older: 72h
    language: 0x0409 # en-US
    forwarded: true #<------ this MAY need to be set to "false", see:https://blog.davidvassallo.me/2017/11/18/lessons-learned-winlogbeat-forwarded-events-no-event-description/

Important: Winlogbeat Security Log Requirements

To ensure the Security channel is collected correctly (especially on Domain Controllers), the following two requirements must be met:

  • System Permissions: The Winlogbeat service must run under the Local System account. Standard service accounts often lack the specific privileges required to read the Security log.

  • Service Restart: A full restart of the Winlogbeat service is mandatory after any configuration change or permission update.

Winlogbeat Configuration

Important: Search and change the IP: “192.168.1.1” to match the CyberSift SIEM IP address

SHA256: ccea8b4de3dd8fa713979351c9015a3a2d3162c2cf230e5b63cc258d4b9495d8


Winlogbeat Configuration w/TLS

Important: Search and change the IP: “192.168.1.1” to match the CyberSift SIEM IP address

SHA256: d4e91ec08dbe8155efa4cf923a69b6f3e7a01058786512b1f033677784f295a2



tags:

  • Installing winlogbeat.exe

  • Configuring winlogbeat.yml

  • Windows logs setup

  • Winlogbeat