USB Use - empty results table rows

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

USB Use - empty results table rows

L1 Bithead

Hello, 

Currently I am monitoring USB device use within my tenant, with the following query:

config case_sensitive = false
| preset = device_control 
| join (dataset = endpoints ) as EP EP.endpoint_name = agent_hostname
| filter event_sub_type = ENUM.MOUNT_DRIVE_MOUNT 
| dedup agent_hostname 
| fields _time, agent_hostname, user, agent_ip_addresses, agent_os_type, action_device_usb_vendor_name, action_device_bus_type, action_device_class_guid, agent_ip_addresses, action_device_class_name, action_device_usb_vendor_id, action_device_usb_product_id, event_type, event_sub_type, active_directory
| sort desc _time

This mostly yields good results however I'm a just wondering what these rows with no values and the action_device_bus_type = action_device_bus_type_0

 

Example output:

PaulThomas00_0-1709669155349.png

If anyone has any idea that would help thank you. 





1 accepted solution

Accepted Solutions

L4 Transporter

Hi @PaulThomas00, thanks for reaching us using the Live Community.

 

I ran the same query in my lab, and found some similar results.

 

Then I created a new basic XQL Query to search for the same event in the xdr_data dataset, and found that the process creating those mounting events are system itself for the recovery volume:

 

jmazzeo_0-1709818758478.png

In Windows shows a similar behavior, but with less details. Probably is the OS mounting the recovery partition and creating a recovery point.

Check it in your end and let us know:

dataset = xdr_data 
| filter event_sub_type = ENUM.MOUNT_DRIVE_MOUNT 
| filter (agent_hostname = """HOSTNAME""") 

 

JM

View solution in original post

1 REPLY 1

L4 Transporter

Hi @PaulThomas00, thanks for reaching us using the Live Community.

 

I ran the same query in my lab, and found some similar results.

 

Then I created a new basic XQL Query to search for the same event in the xdr_data dataset, and found that the process creating those mounting events are system itself for the recovery volume:

 

jmazzeo_0-1709818758478.png

In Windows shows a similar behavior, but with less details. Probably is the OS mounting the recovery partition and creating a recovery point.

Check it in your end and let us know:

dataset = xdr_data 
| filter event_sub_type = ENUM.MOUNT_DRIVE_MOUNT 
| filter (agent_hostname = """HOSTNAME""") 

 

JM
  • 1 accepted solution
  • 768 Views
  • 1 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!