XQL Query: Event Sub Type causing issues in Query

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

XQL Query: Event Sub Type causing issues in Query

L3 Networker

We have written a query to get certain files types being downloaded from browser process and get its parent process details etc. When we try to add the field event_sub_type we start receiving and error. If we exclude the field from the query we get proper results. If you run the below queries you will be able to produce the error.

 

Please try the below query: (Status == Success)

config case_sensitive = false 
| preset = xdr_process 
| filter action_process_image_name in ("chrome.exe","firefox.exe","msedge.exe","brave.exe","iexplorer.exe")
| fields agent_hostname as Host, action_process_image_name as Process, action_process_os_pid as PID, action_process_image_command_line as Command, actor_process_image_name as Parent_Process, actor_process_os_pid as PPID, actor_process_command_line as Parent_Command
| join (preset = xdr_file) as PF pf.actor_process_image_name = Process and pf.actor_process_os_pid = PID and pf.agent_hostname = Host
| filter event_sub_type in (ENUM.FILE_CREATE_NEW, ENUM.FILE_RENAME, ENUM.FILE_WRITE)
| filter action_file_name ~= ".*exe|.*dll|.*zip|.*rar|.*msi|.*vbs|.*one|.*html"
| filter action_file_name not contains "zone.identifier"
| filter action_file_path contains "Desktop" or action_file_path contains "Downloads" or action_file_path contains "Documents"
| fields Host, action_file_name as Filename, action_file_path as FilePath, Process, PID, Command, Parent_Process, PPID, Parent_Command

 

Now, please try the below query: (Status == Fail)

config case_sensitive = false 
| preset = xdr_process 
| filter action_process_image_name in ("chrome.exe","firefox.exe","msedge.exe","brave.exe","iexplorer.exe")
| fields agent_hostname as Host, action_process_image_name as Process, action_process_os_pid as PID, action_process_image_command_line as Command, actor_process_image_name as Parent_Process, actor_process_os_pid as PPID, actor_process_command_line as Parent_Command
| join (preset = xdr_file) as PF pf.actor_process_image_name = Process and pf.actor_process_os_pid = PID and pf.agent_hostname = Host
| filter event_sub_type in (ENUM.FILE_CREATE_NEW, ENUM.FILE_RENAME, ENUM.FILE_WRITE)
| filter action_file_name ~= ".*exe|.*dll|.*zip|.*rar|.*msi|.*vbs|.*one|.*html"
| filter action_file_name not contains "zone.identifier"
| filter action_file_path contains "Desktop" or action_file_path contains "Downloads" or action_file_path contains "Documents"
| fields Host, event_sub_type, action_file_name as Filename, action_file_path as FilePath, Process, PID, Command, Parent_Process, PPID, Parent_Command

Notice the last line entry contains event_sub_type field, whereas in the first one we do not have this entry and the query succeeds.

 

Is anyone else facing this issue? Would we good to know and can we please get this sorted?

 

Cortex XDR 

Kind Regards
KS
1 accepted solution

Accepted Solutions

L3 Networker

Hi KanwarSingh01,

When defining 'event_sub_type' as part of the fields stage you must also include the 'event_type' field. Simply add  'event_type' to your fields stage and I think you will find the issue is resolved.

Thanks,
Ben

View solution in original post

2 REPLIES 2

L3 Networker

Hi KanwarSingh01,

When defining 'event_sub_type' as part of the fields stage you must also include the 'event_type' field. Simply add  'event_type' to your fields stage and I think you will find the issue is resolved.

Thanks,
Ben

Thank you for the response. Yes that fixes the issue.

Kind Regards
KS
  • 1 accepted solution
  • 1524 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!