syslog-ng Premium Edition 7.0.33 - Windows Event Collector Administration Guide

In the Windows domain client host, start gpedit.msc.
Navigate to Computer Configuration > Administrative Templates > Windows Components > Event Forwarding.
Select SubscriptionManagers and enable it.
To add a subscription, click Show.
Set Server to HTTP://<linux_host_fqdn>:5985/wsman/SubscriptionManager/WEC,Refresh=10

For example:

Server=HTTP://testlinuxhost.testdomain.com:5985/wsman/SubscriptionManager/WEC,Refresh=10

Configuring Kerberos authentication on Linux hosts

Configuring Windows event logs to be forwarded to the syslog-ng Premium Edition server using WEC > Configuring Kerberos authentication on Linux hosts

Perform the following procedure on the Linux host to use Kerberos-based authentication between Windows Event Forwarding (WEF) and Windows Event Collector (WEC).

On the Linux host, configure the gateway and DNS settings so that the other hosts in the domain can reach the Linux host.

In Windows Active Directory DNS Manager, use the same name and IP address that you set for the Linux host.

Copy the generated keytab file from the Windows Domain Controller to the Linux host.

CAUTION:

Risk of unauthorized access!

Protect the keytab file with proper file permissions, as anyone with read permissions can use the credentials in the network to access other services. Give administrators all permissions (6) to the keytab file, but do not give read or any other permissions (0) to users.

(Optional) If there was a keytab file already installed on the Linux host, merge it with the keytab file that you generated previously in this procedure:
1. Start the ktutil tool, and enter:
```
read_kt [path of the keytab file previously installed on Linux host]
									read_kt [path of the currently generated keytab file]
									write_kt [path of the new, merged keytab file]
					q
```
2. After the ktutil tool has created the new, merged keytab file, configure it for WEC.

Configuring Windows Event Collector

Configuring Windows event logs to be forwarded to the syslog-ng Premium Edition server using WEC > Configuring Windows Event Collector

Once you have configured your event source computer(s), the next step is to configure your event collector, in this case, the Windows Event Collector (WEC) for syslog-ng PE.

NOTE: The configuration file of WEC is YAML based. Note that YAML uses spaces, not tabs, for indentation.

To configure WEC, use the following options.

For an example wec.yaml file, see WEC configuration example for certificate-based authentication.

server

Type:	string
Default:	N/A

Description: The hostname, IP address, or FQDN of the server where WEC is running.

NOTE: The value of the Server parameter must match the Common Name of the SSL certificate.

NOTE: If you use Kerberos authentication between WEF and WEC, set server to the FQDN of the Linux host.

port

Type:	integer
Default:	5986

Description: The port where the server running WEC is listening.

NOTE: If you use Kerberos authentication between WEF and WEC, set port to 5985.

kerberos | keytabfile

Type:	string
Default:	N/A

Description: The path to the keytable (also called keytab) file.

Specify the path to the keytab file in the keytabfile option, as it is a mandatory option for the kerberos parameter.

For more information, see WEC configuration example for Kerberos authentication.

keyfile

Type:	string
Default:	N/A

Description: The path to the file that contains the unencrypted private key of the server running WEC. The file is in PEM format.

certfile

Type:	string
Default:	N/A

Description: The path to the file that contains the X.509 certificate of the server running WEC. The file is in PEM format.

cadir

Type:	string
Default:	N/A

Description: The path to the directory that contains the trusted CA certificates in PEM format.

log

Type:	map
Default:	N/A

Description: The options to specify how to handle the internal logs of WEC:

level
file

WEC sends internal log messages to stderr. You can also optionally specify a file to send logs to (in parallel with stderr). If you are using a systemd platform and start WEC using systemctl, then stderr is redirected to systemd-journal, and this is where you will find the internal logs of WEC.

level
Type:	debug\|info
Default:	info
Description: The application log level of WEC. Possible values are: debug: Information with the most details, useful when debugging WEC and diagnosing issues. info: Basic information about the initialization of WEC. Following initialization, no information is displayed on screen, unless an issue occurs.

file
Type:	string
Default:	N/A
Description: The path to the file where WEC should write internal log messages. The log file is automatically created by syslog-ng PE. You can send this file to syslog-ng using a file() source.

eventdestination

Type:	map
Default:	N/A

Description: The options to specify how to store the event logs that are forwarded to WEC:

file
unixdatagram
queuesize

file
Type:	string
Default:	N/A
Description: The path to the file where WEC should write the events received from the Windows host(s). Use this option for debug purposes only, when you wish to check what WEC is sending to syslog-ng PE. It is possible to log both to a file and a Unix datagram socket in parallel.

unixdatagram
Type:	string
Default:	N/A
Description: The path to the Unix datagram socket receiving the Windows events. WEC writes the received events to the Unix datagram socket specified here. The listening socket is automatically created by syslog-ng PE. It is possible to log both to a file and a Unix datagram socket in parallel.

queuesize
Type:	integer
Default:	10000
Description: The number of events that the destination memory queue can store. Note that the main purpose of queuesize is to speed up the writing of data into memory and smooth out peaks. It is recommened to use the default value for this option. For more information about flow control, see Flow control.

subscriptions

Type:	map
Default:	N/A

Description: The options related to the subscriptions you have set up on WEC:

name
computers
contentformat
heartbeats
connectionretry
batchsizelimit
batchtimeoutlimit
queries
readexistingevents

NOTE: You can set up multiple subscriptions to events coming from the same Windows host. If an event matches more than one subscription, the event log comes in to WEC as many times as there is a match.

name
Type:	string
Default:	N/A
Description: The unique name of the subscription in WEC.

computers
Type:	list of strings
Default:	N/A
Description: A list of strings that specifies the DNS names of the non-domain computers that are allowed to initiate subscriptions. Specifies the Windows hosts from which you want WEC to receive event logs. The names can be specified using the * and ? wildcards, for example, *".mydomain.com" or ""*.

contentformat
Type:	Events\|RenderedText
Default:	N/A
Description: A value that specifies the format of the returned events. Possible values are: RenderedText: Events are returned with the localized strings (such as event description strings) attached to the events Events: Events are returned without any of the localized strings One Identity recommends setting this option to RenderedText.

heartbeats
Type:	integer
Default:	N/A
Description: A value that specifies the heartbeat interval for the subscription in seconds.

connectionretry
Type:	integer
Default:	N/A
Description:WEC attempts to reconnect to the Windows host(s) at the specified interval of time in seconds.

batchsizelimit
Type:	integer
Default:	0 (meaning that there is no limit)
Description: Specifies the maximum number of items for batched delivery in the event subscription. Set this value to 1 if you wish to perform tests or debugging. NOTE: This option is not enforced on the Windows host side. Windows is handling this value only as a recommendation. The only exception is the value 1.

batchtimeoutlimit
Type:	integer
Default:	N/A
Description: Specifies the maximum latency allowed in delivering a batch of events (in seconds). NOTE: This option is not enforced on the Windows host side. Windows is handling this value only as a recommendation.

queries
Type:	string
Default:	N/A
Description: Specifies the query string for the subscription. You can: type this value manually, or copy this value from the XML tab of the Create Custom View pop-up window in Windows For examples of queries, check the following Windows blog posts: Microsoft TechNet blog post Advanced XMl filtering in the Windows Event Viewer Microsoft Developer Network article Wecutil.exe

readexistingevents
Type:	true\|false
Default:	false
Description: When the value is true, all existing events are read from the subscription event source if the subscription in question has not been read yet. When the value is false, only future (arriving) events are delivered. If the subscription has a state in the persist file, this option will have no effect.

Configuring syslog-ng PE

Configuring Windows event logs to be forwarded to the syslog-ng Premium Edition server using WEC > Configuring syslog-ng PE

Prerequisites

syslog-ng Premium Edition (syslog-ng PE) version 7.0.6 or newer.

To enable syslog-ng PE to read and accept Windows events, you need to configure a source called windowsevent().

To configure syslog-ng PE

Configure the windowsevent() source.
```
source s_wec {
    windowsevent();
};
```
The windowsevent() source takes the following options:
- unix-domain-socket(): The path to the Unix domain socket to read messages from.
  
  The default value is /opt/syslog-ng/var/run/wec.sock.
- prefix(): The prefix that you wish to append to the key-value pairs.
  
  The default value is ".windowsevent.".
  
  If you want to send Windows event logs to SDATA, then set prefix(".SDATA."). This can be useful, for example, when you forward Windows event logs to a syslog-ng Store Box.
For more information on the windowsevent() source, see "windowsevent: Collecting Windows event logs" in the Administration Guide.

Define a complete log path in syslog-ng.conf to enable the windowsevent() source, s_wec. Otherwise, the WEC process will not run (connection refused).

For example:

source s_wec {
    windowsevent();
};

log {
    source(s_wec);
    destination {
        file("/var/log/example.log"
            template("$(format-json --scope dot-nv-pairs)\n")
        );
    };
};

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem