--- title: "Operating system events" slug: "operating-system-events-1" tags: ["Reference", "Helix Enterprise", "Sec Ops and Analytics"] updated: 2026-09-05T14:07:16Z published: 2026-09-05T14:07:16Z canonical: "docs.trellix.com/operating-system-events-1" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Operating system events Newer versions of Windows have granular control over what is audited by the operating system. We recommend you carefully plan out your policy to collect logs for the events that matter. The Microsoft Security Compliance Manager has templates that can guide you through creating a robust baseline policy for all Microsoft operating systems. See [http://technet.microsoft.com/en-us/library/cc677002.aspx](http://technet.microsoft.com/en-us/library/cc677002.aspx) for additional information. Important event IDs At a minimum, we recommend the following Event IDs be sent to Helix Enterprise: | 4624 | 551 | 592 | 680 | 528 | 4648 | | --- | --- | --- | --- | --- | --- | | 4689 | 4778 | 540 | 552 | 593 | 682 | | 4634 | 4672 | 4698 | 4779 | 538 | 576 | | 602 | 683 | 4647 | 4688 | 4776 | | DNS query logging DNS logs are critical to the ability to find and detect malicious activity, and query logs attribute those requests to the inside host. We recommend you enable DNS query logging, and send those logs to Helix Enterprise using NXLog. To configure DNS logs: 1. Find the DNS server in the **Server Manager** console. 2. Expand DNS, right-click the server, and choose **Properties**. 3. On the **Debug Logging** tab, click or confirm that: - **Outgoing** and **Incoming** are both checked - **UDP** and **TCP** are both checked - **Queries/Transfers** is checked - **Details** is not checked ![DHCP-logging1.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-52a243f6-68a5-8c86-2a9b-a50c180c63c0.png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A28%3A20Z&se=2026-11-20T11%3A28%3A20Z&sr=c&sp=r&sig=qnt8ONKMQyJMjKsBF0lKTAv86hg50OWavXhP6vlj%2BFs%3D) Windows DHCP logging DHCP logs help connect the dots from perimeter activity (such as a firewall event showing a connection to a C2 server) to the inside host. As hosts are dynamically assigned IPs via DHCP or roaming between wireless access points, tracking who is where becomes difficult without DHCP logs. We recommend enabling DHCP audit logging and sending those logs to Helix Enterprise using NXLog. You must change the logging path from the default in order to forward with NXLog. To enable logging: 1. Find the DHCP server in the **Server Manager** console. 2. Expand DHCP, right-click the server, and choose **IPv4 Properties**. 3. On the **General** tab, click **Enable DHCP audit logging**. ![DHCP-logging2.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-34be1fce-8a92-034d-32c7-07fa0428398d.png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A28%3A20Z&se=2026-11-20T11%3A28%3A20Z&sr=c&sp=r&sig=qnt8ONKMQyJMjKsBF0lKTAv86hg50OWavXhP6vlj%2BFs%3D) 4. On the **Advanced** tab, verify the path to the log files for the Audit log file path option. Note the path has been changed from `c:\Windows\system32\dhcp`. ![DHCP-logging3.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-928a3921-4e17-4e86-595d-095da173f416.png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A28%3A20Z&se=2026-11-20T11%3A28%3A20Z&sr=c&sp=r&sig=qnt8ONKMQyJMjKsBF0lKTAv86hg50OWavXhP6vlj%2BFs%3D) Windows Netlogon debug logging Enabling netlogon debug logging provides detailed activity about authentication beyond what is normally contained in security event logs. These logs can also be shipped using NXlog. For more information, see [http://support.microsoft.com/kb/109626](https://support.microsoft.com/en-us/help/109626/enabling-debug-logging-for-the-netlogon-service). Windows IIS logs Internet Information Server (IIS) logs do not provide much information by default, but they can be very verbose. Trellix recommends you enable logging to capture important information for detecting malicious activity, such as the method, bytes transferred, and other critical data. IIS logs can be sent to Helix Enterprise using NXLog. The system requirements are: To configure IIS log settings: 1. Open the **Internet Information Services (IIS) Manager,** select the IIS server that is to be configured, and then select **Logging**. ![IIS_logging1.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-b148f192-2c0c-23fd-0aae-9cc906fed333.png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A28%3A20Z&se=2026-11-20T11%3A28%3A20Z&sr=c&sp=r&sig=qnt8ONKMQyJMjKsBF0lKTAv86hg50OWavXhP6vlj%2BFs%3D) 2. Configure the log settings to reflect the following configuration: - For the One log file per option, select **Site**. - For the Format option, select **W3C**. - Click **Select Fields**and check all field options. - For Log Event Destination, select **Log file only** or **Both log file and ETW event**. - For Schedule under Log File Rollover, select **Daily** ![IIS_logging2.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-9037365a-9537-c59c-cf6d-5faee5555b4d.png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A28%3A20Z&se=2026-11-20T11%3A28%3A20Z&sr=c&sp=r&sig=qnt8ONKMQyJMjKsBF0lKTAv86hg50OWavXhP6vlj%2BFs%3D) 3. Apply the changes to the logging configuration. - IIS 6, 7, or 8 - A reliable NTP source