# Log Events

# Introduction

CyberSift SIEM depends on the correct configuration of Windows GPO settings to ensure that all relevant logs are generated and collected. This document serves as a starting point for setting up a minimum recommended windows event logging environment

# Recommendations

### **Audit account logon**

These security events tell you when domain controllers or local computers authenticate a user’s access. The default setting is `success`. If possible, monitoring `failed` logins should be enabled too, as this allows detections of various attacks like brute force and attempted lateral movement

Ensure the following are set too:

* **Logon/Logoff\\Audit Account Lockout**  
  Identify when users attempt to sign into an account that was locked out
* **Logon/Logoff\\Audit Logoff and Logon/Logoff\\Audit Logon**  
  Track users logon and logoff events
* **Logon/Logoff\\Audit Special Logon**  
  Track users with privileged access
* **Account Logon → Audit Kerberos Service Ticket Operations** *(Domain Controllers only)*  
  Track when users request Kerberos service tickets (Event 4769)


---

### **Audit account management**

***These can be left as per windows default***

These audit logs tell you about account management activities for:

* **User account**: created, changed, deleted, renamed, disabled, or enabled
* **Group:** created, changed, or deleted
* **Password**: set or changed

The default settings are:

* **Domain controller**: success


---

### **Audit directory service access**

***These can be left as per windows default***

This security audit log tells you whether a user accesses an Active Directory object with its own system access control list (SACL).

The default settings are:

* **Domain controller**: success


---

### **Audit policy change**

***These can be left as per windows default***

This audit event tells you about changes to:

* User risks assignment policies
* Audit policies
* Trust policies

The default settings are:

* **Domain controller**: success


---

### **Audit process tracking**

Please refer to “**Monitoring the Process Command Line**” article


---

### **Audit system events**

***We deviate from default here***

The default settings are:

* **Domain controller**: success

However we recommend you also set **Member server** to success


---

### Audit File Share Access

***Only apply this to important file shares, as it is extremely verbose***

Modify the settings under **__Object Access\\Audit File Share__** to track who accessed the resource and where they accessed it from


---

### Audit Startup Folder Access

Modify the settings under **Object Access → Audit File System** for the Startup folders `(``*C:\\ProgramData\\…\\Startup and C:\\Users<username>\\…\\Startup*``)` to track who created, modified, or deleted files in these locations.


---

### PowerShell Script Block Logging

This will capture full contents of executed PowerShell scripts (Event ID 4104 in *Microsoft-Windows-PowerShell/Operational*). Enable PowerShell Script Block Logging via GPO:

`Computer Configuration → Administrative Templates → Windows Components → Windows PowerShell → Turn on PowerShell Script Block Logging`


---

### WMI Activity Logging

Enabling WMI logging helps detect malicious persistence and remote execution. 

Deploy a GPO that creates the following registry preference to enable the WMI-Activity Operational log:

`[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-WMI-Activity/Operational]`  
`"Enabled"=dword:00000001`  
`"Retention"=dword:00000000`  
`"MaxSize"=dword:04000000`

This will activate the log and allow collection of key events (e.g., 5858, 5861, 5862) from *Microsoft-Windows-WMI-Activity/Operational*.


---

### Audit Registry (Object Access)

Enabling registry auditing helps detect persistence and unauthorized changes.


1. Enable Audit Registry via GPO:

`Computer Configuration → Windows Settings → Security Settings → Advanced Audit Policy Configuration → Object Access → Audit Registry`

* Recommended: Success and Failure


2. Apply auditing (SACLs) to critical keys to generate actual events:

* `HKCU\Software\Microsoft\Windows\CurrentVersion\Run` (user logon persistence)
* `HKLM\Software\Microsoft\Windows\CurrentVersion\Run` (machine logon persistence)
* `HKLM\SYSTEM\CurrentControlSet\Services` (services/startup programs)
* `HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon` (Shell/Userinit)
* `HKLM\SECURITY\Policy\Secrets ` (sensitive credentials)


---

### Monitor user activity

The following settings are recommended to be set, however further tuning would be required after initial setup due to their verbosity

* **DS Access\\Audit Directory Service Access and DS Access\\Audit Directory Service Changes**  
  Monitors users’ attempts to access, create, modify, delete, move, or undelete Active Directory Domain Services (AD DS) objects

  
:::tip
  Enable only on Domain Controllers

  :::
* **Object Access\\Audit Certification Services**  
  **Only applicable IF a server has the Active Directory Certificate Services (AD CS) role installed**  
  Monitor activities on devices that host Active Directory Certificate Services (AD CS) role services
* **Privilege Use\\Audit Sensitive Privilege Use**  
  Track privileged access across one or more systems


---


:::info
tags:

* Log events for GPO deployments
* Recommended GPO Settings

:::

---

**Documents**

- [Logs and Architecture](https://outline.cybersift.io/s/sentio-siem/doc/logs-and-architecture-acvUiDgvI5)
- [Sentio](https://outline.cybersift.io/s/sentio-siem/doc/sentio-KuYAbF5grr)
- [ISO27001:2022](https://outline.cybersift.io/s/sentio-siem/doc/iso270012022-7S5IzvF6a0)
- [FAQ](https://outline.cybersift.io/s/sentio-siem/doc/faq-vVyRNyNb60)