--- title: "Detecting user anomalies" slug: "detecting-user-anomalies-1" tags: ["Install and Get Started", "NDR 4.x", "Customer", "Network Security"] updated: 2026-11-17T09:22:59Z published: 2026-11-17T09:22:59Z canonical: "docs.trellix.com/detecting-user-anomalies-1" --- > ## 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. # Detecting user anomalies Trellix NDR continuously ingests user logon events from Active Directory. The system correlates these events against historical baselines. When the system detects anomalous user behavior, it generates a security alert in the dashboard. ### Scenarios for detecting anomalous users The system monitors these detection scenarios to trigger alerts. - **Unusual host access**: The system detects a successful user login to a host usually used by another user. The system specifically excludes new machine deployments from this detection. - **Unusual time**: The system detects a user login occurring outside standard activity periods. - **Brute force attempt**: The system detects multiple failed login attempts followed by a successful login. ### Integrating with On-prem Active Directory Trellix NDR integrates with Microsoft Active Directory. This architecture retrieves user logon events from your domain controllers. Upon initial connection, the system fetches historical logon event records from the monitored domain. ### Enriching events with user data From user logon data, Trellix NDR enriches the events from Packet Capture, Network Security, and IPS with user information. Every event will have a **user_info** object present in it. The **user_info** object contains user details, such as the name, computer, domain, and details on whether the user is a privileged user or not. A sample **user_info** object is provided below: **"user_info": {"name": ["admin@piblr.qa"], "computer": ["FileServer2016.piblr.qa"], "domain": ["piblr.qa"], "privilegedAccount": "yes"}}** > [!NOTE] > Note > > The **privilegedAccount** field in the **user_info** object is present only if the ad-sync feature is enabled in the Trellix NDR Web UI. ### Configure the Active Directory integration Connect Trellix NDR to Microsoft Active Directory to retrieve user logon event records. > [!NOTE] > Note > > If you previously used the **Trellix Logon Collector**, you must reconfigure your domains using these steps. 1. Log in to the Trellix NDR CLI as an administrator. 2. Type `ad-sync` to access the configuration menu. 3. Type `1` to select **Configure servers**. 4. Type `A` to select **Add an entry**. 5. Verify whether any Active Directory servers are already configured. 1. If no servers are configured, add the Active Directory server details. 2. If a server already exists, verify that the configuration details are correct. 6. Type `1` to toggle the state between **Enable** and **Disable**. > [!NOTE] > Note > > Set the option to **Enable** to retrieve logon event data. Setting this option to **Disable** halts the retrieval of logon event data. 7. Type the domain controller address in the **Host address** field. 8. Type `5986` in the **Port** field. 9. Type the username in the **Bind DN** field. 10. Type the password in the **Bind Password** field. 11. Type a value in the **Base DN** field. > [!NOTE] > Note > > The **Base DN** field requires input to save the configuration. You can type any value. This input does not affect event data flow. Keep the default values for fields, such as **LDAP Encryption Type** and **Verify Server Certificate**. 12. Type `Q` to save the configuration and exit. #### Configure the Active Directory machine listener Ensure specific configurations are set up on the Active Directory machine. 1. Log in to the Active Directory machine. 2. Open PowerShell. 3. Run this command to verify the listener status: **winrm enumerate winrm/config/listener** 4. Verify that a listener exists on port **5986**. #### Configure WinRM service and basic authentication These commands prepare the WinRM service to accept API connections. 1. Run this command to initialize the WinRM service: **winrm quickconfig -quiet** 2. Run this command to allow basic authentication: **winrm set winrm/config/service/auth '@{Basic="true"}'** 3. Run this command to ensure encrypted traffic: **winrm set winrm/config/service '@{AllowUnencrypted="false"}'** 4. Run this command to bypass remote restrictions. **New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" -Name "LocalAccountTokenFilterPolicy" -Value 1 -PropertyType DWord -Force** > [!NOTE] > Note > > This registry key ensures administrative credentials work over WinRM. #### Optional: Create the SSL certificate for WinRM Use a CA-signed certificate to encrypt the WinRM HTTPS connection. If a CA-signed certificate is not available, generate a self-signed certificate. > [!NOTE] > Note > > Set the certificate expiration according to your requirements. Trellix NDR cannot fetch Active Directory records after a certificate expires. 1. Run this command to check for existing certificates: **Get-ChildItem -Path Cert:\LocalMachine\My** 2. Run this command to find the fully qualified domain name: **$FQDN = [System.Net.Dns]::GetHostByName($env:computerName).HostName; Write-Host "Your FQDN is: $FQDN"** 3. Run this command to generate a self-signed certificate. **$Cert = New-SelfSignedCertificate -DnsName "YOUR_DC_FQDN" -CertStoreLocation "Cert:\LocalMachine\My" -NotAfter (Get-Date).AddYears()** > [!NOTE] > Note > > - Replace **YOUR_DC_FQDN** with the domain name retrieved in the previous step. > - Replace **** with the required validity period in years. 4. Run this command to capture the certificate thumbprint: **$Thumb = $Cert.Thumbprint; Write-Host "Certificate Thumbprint: $Thumb"** #### Set up the secure HTTPS listener The listener waits for connections on port 5986. 1. Run this command to remove conflicting listeners: **winrm delete winrm/config/Listener?Address=*+Transport=HTTPS** 2. Run this command to create the secure listener: **winrm create winrm/config/Listener?Address=*+Transport=HTTPS "@{Hostname=`"YOUR_DC_FQDN`";CertificateThumbprint=`"$Thumb`"}"** > [!NOTE] > Note > > Replace **YOUR_DC_FQDN** with your correct domain name. #### Verify network access for the listener Ensure traffic can physically reach the server. 1. Run this command to open firewall port 5986: **netsh advfirewall firewall add rule name="WinRM-HTTPS" dir=in action=allow protocol=TCP localport=5986** 2. Run this command to confirm the active listener: **winrm enumerate winrm/config/listener** 3. Verify that the new listener appears in the output. Add the command here again for the user to verify the listener. ### Detections for Active Directory events The system monitors specific Event IDs to detect suspicious activity. - **Logons and sessions:** The system tracks successful logons, failed logons, logoffs, and session connections. - **Kerberos authentication:** The system tracks ticket requests and authentication failures. - **Account changes:** The system tracks unexpected changes to user accounts and password resets. - **Privilege escalation:** The system detects audit policy changes and newly assigned privileges. - **Advanced threat detections:** The system detects replay attacks, SID history changes, and new services.