- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
03-04-2026 03:31 AM
Hi all,
Could someone help me write an XQL query in Cortex XSIAM that:
svc.exe, pwrautomate.exe, mcs.bat, cleanup.bat, uri.bat, p.zip^filters_update_.*_at_abdata\.com\.exe$ATT&CK mapping: T1059, T1204.002, T1105, T1106, T1036.
Looking for syntax that’s fully compatible with XSIAM. Thanks!
03-04-2026 07:00 AM
Hello @N.B238890 ,
Greetings for the day.
To address your request, here is a comprehensive XQL query designed for Cortex XSIAM that unifies process and file telemetry while meeting your specific filtering, regex, and suppression requirements.
This query uses the xdr_data dataset and standard event enums to identify the specified activity.
Case Insensitivity
The config case_sensitive = false stage ensures that all string comparisons and regex matches are handled regardless of capitalization.
Event Filtering
The query targets:
PROCESS_START for executions
FILE_CREATE_NEW, FILE_WRITE, and FILE_RENAME for file activity
Regex Matching
The ~= operator is used for the masquerade regex pattern.
Unified Results
The coalesce() function merges disparate fields (such as action_process_image_name and action_file_name) into unified columns for easier investigation.
Hash Persistence Logic
The optional suppression block is structured to ignore events in common benign paths only if no hash is present. Any event containing a hash is preserved.
Triage View
The comp stage provides a summarized, deduplicated view with hit counts and the most recent timestamp, which is useful for high-level triage and scoping.
If you feel this has answered your query, please let us know by clicking like and on "mark this as a Solution".
Thanks & Regards,
S. Subashkar Sekar
03-04-2026 07:00 AM
Hello @N.B238890 ,
Greetings for the day.
To address your request, here is a comprehensive XQL query designed for Cortex XSIAM that unifies process and file telemetry while meeting your specific filtering, regex, and suppression requirements.
This query uses the xdr_data dataset and standard event enums to identify the specified activity.
Case Insensitivity
The config case_sensitive = false stage ensures that all string comparisons and regex matches are handled regardless of capitalization.
Event Filtering
The query targets:
PROCESS_START for executions
FILE_CREATE_NEW, FILE_WRITE, and FILE_RENAME for file activity
Regex Matching
The ~= operator is used for the masquerade regex pattern.
Unified Results
The coalesce() function merges disparate fields (such as action_process_image_name and action_file_name) into unified columns for easier investigation.
Hash Persistence Logic
The optional suppression block is structured to ignore events in common benign paths only if no hash is present. Any event containing a hash is preserved.
Triage View
The comp stage provides a summarized, deduplicated view with hit counts and the most recent timestamp, which is useful for high-level triage and scoping.
If you feel this has answered your query, please let us know by clicking like and on "mark this as a Solution".
Thanks & Regards,
S. Subashkar Sekar
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

