IBM Support

QRadar: Microsoft Windows Security DSM does not extract usernames from events when they end with a dollar sign "$"



When an event for the Microsoft Windows Security DSM has a user ending with dollar sign "$", this user is not extracted.


For example, in this Windows Security event:
<13>Jun 23 12:03:29 MyServerName AgentDevice=WindowsLog	AgentLogFile=Security	
PluginVersion=	Source=Security	Computer=Server	OriginatingComputer=x.x.x.1	
User=SYSTEM	Domain=NT AUTHORITY	EventID=540	EventIDCode=540	EventType=8	
EventCategory=2	RecordNumber=27741234	TimeGenerated=1656000205	
TimeWritten=1656000205	Level=0	Keywords=0	Task=0	Opcode=0	
Message=Successful Network Logon:   User Name: SERVERFLOW2$   Domain:…
The username SERVERFLOW$ is not extracted, even if the event is open with the DSM Editor:


Note: By default the Microsoft Windows Security DSM extracts the username information from the "Message" field and not from the "User" metadate field, which usually says SYSTEM when the user is a system account.


QRadar does not populate usernames for Windows events that are system-generated since there is not a user login generating the events. Parsing is completed this way by design to help administrators filter events generated by human beings from computer or system accounts. Another benefit of this change is that computer or system users do not update or populate assets with the last logged in user when the source is a system account.

The following values are considered by QRadar to be system-generated usernames. When the Windows Security Event Log DSM encounters these values within a Windows event, the value is populated as N/A in the Username column.
  • System
  • Username$
  • Management
  • Unknown
  • Dash (-)
  • Name

    Note: The Windows DSM also considers variations in capitalization and also spelling differences for events generated in the following group 1 languages: English, Chinese (simplified and traditional), Japanese, Korean, French, German, Italian, Spanish, and Portuguese (Brazil).

Resolving The Problem

To revolve the issue, use the DSM Editor to create a custom field, then extract all the users even users for system accounts (users ending with a dollar sign "$").
This article contains two methods for extracting the user information, which might need to be customized based on the admin needs and event formats. The first method involves extracting only the SYSTEM user, while the second extracts both. Users need to complete only one of the two methods.

How to create a custom field

  1. Go to the DSM Editor.
  2. Select the Microsoft Windows Security Event Log DSM.
  3. Confirm you are in the Properties tab, then click the blue button with a white plus sign on it:
  4. Scroll down and click Create New:
  5. Give it the name you want, for this example the field name is Windows User, confirm the Field Type is Text, then click Save, then Select
The custom field is created and users must extract either only the SYSTEM user or both users.

How to extract only the SYSTEM user

Go the field that was created in the How to create a custom field section, then use the next configuration:
Expression Type: Regex
Expression: \tUser=SYSTEM.*User Name:\s(.*?)\s
Capture Group: 1
Make sure no spaces are left before or after the Expression.
The custom field extracts the user only when this user is a SYSTEM user:

How to extract both users

Using the user that was created in the How to create a custom field section, two expressions are needed to extract both type of users:
Expression 1:
Expression Type: Regex
Expression: \tUser=SYSTEM.*User Name:\s(.*?)\s
Capture Group: 1
Expression 2:
Expression Type: Regex
Expression: User=\t.*Message=.*0x\w\w+\s\w+\\(.*?)\s
Capture Group: 1
Make sure no spaces are left before or after the Expressions.
The custom fields extract the user for both type of users:
Note: Depending on the event format, the regex might need to be adjusted.

Document Location


[{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"ARM Category":[{"code":"a8m0z000000cwtSAAQ","label":"DSM Editor"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Document Information

Modified date:
20 February 2024