A cybersecurity analyst consistently searches for suspicious activity involving the 'System' user on Windows endpoints. However, logs from different Windows versions or agents report the 'System' user as 'NT AUTHORITY\SYSTEM', 'SYSTEM', or 'S-1-5-18'. This inconsistency hinders effective searching. To optimize content for this specific use case within XSIAM, which data modeling rule should the engineer prioritize?
正解:B
The core problem is inconsistency in reporting the 'System' user. A 'mapping rule' (often part of a broader 'normalization' or 'transformation' rule in XSIAM's content optimization) is designed precisely for this: taking various forms of an input value and consistently mapping them to a single, standardized output value. By mapping 'NT AUTHORITY\SYSTEM', 'SYSTEM', and 'S-1-5-18' to 'SYSTEM_ACCOUNT' in a new 'normalized_user' field, the analyst can perform a single, efficient query on 'normalized_user'='SYSTEM_ACCOIJNT' regardless of the raw log variant. Option A extracts a specific identifier but doesn't solve the inconsistent naming problem for 'SYSTEM' vs 'NT AUTHORITY\SYSTEM'. Option C is for resolving SIDS to usernames, not normalizing different names for the same system account. Option D is data loss. Option E is for correlating events, not normalizing data.