How to List USB Devices Across All Mac and Linux Devices
Using Kolide, you can easily view and query USB Devices across your fleet.
Introduction
The majority of common peripheral hardware devices (headphones, keyboards, mice, flash storage, microphones, etc.) communicate over some variant of the Universal Serial Bus (USB). Kolide collects information about connected USB devices on macOS and Linux computers. This data includes basic identifying information such as Manufacturer, Model and Serial Number, as well as the address/port via which the USB device is connected.
What USB Device Data Can Kolide Collect?
Kolide's endpoint agent bundles in osquery to efficiently collect USB Devices from Mac and Linux devices in your fleet. Once collected, Kolide will parse, clean up, and centrally store this data in Inventory for your team to view, query, or export via API.
Kolide meticulously documents every piece of data returned so you can understand the results.
USB Devices Schema
| Column | Type | Description | |
|---|---|---|---|
| id | Primary Key |
Unique identifier for the object |
|
| device_id | Foreign Key |
Device associated with the entry |
|
| device_name | Text |
Display name of the device associated with the entry |
|
| model | Text |
Model name reported by the device |
|
| model_id | Text |
Hex-encoded USB product ID |
|
| protocol | Integer |
USB protocol code, interpreted relative to |
|
| removable | Boolean |
|
|
| serial | Text |
Serial number reported by the device. Inexpensive devices often report a blank or shared serial number, so this is not guaranteed to be unique. |
|
| usb_address | Integer |
On macOS, the device's address on its USB bus. On Linux, the number of the USB bus the device is on. |
|
| usb_class | Text |
USB device class code (eg. |
|
| usb_port | Integer |
On Linux, the device number the kernel assigned on its bus. It changes when the device is reconnected and is not a physical port. Often blank on macOS. |
|
| usb_subclass | Text |
USB device subclass code, interpreted relative to |
|
| vendor | Text |
Name of the device's manufacturer. On macOS this is reported by the device; on Linux it is looked up from |
|
| vendor_id | Text |
Hex-encoded USB vendor ID (eg. |
|
| version | Text |
Device release number reported by the device. The format differs
by platform (eg. |
|
| collected_at | Timestamp |
Time the row of data was first collected in the database |
|
| updated_at | Timestamp |
Time the row of data was last changed in the database |
|
Why Should I Collect USB Devices?
Many organizations have compliance requirements or Acceptable Use Policies which govern the usage of peripheral hardware, which necessitates periodic audit and review. USB devices have been viewed as a security risk due to the possibility of someone inserting a found USB device which has been loaded by an attacker with malware.
End-User Privacy Consideration
Kolide practices Honest Security. We believe that data should be collected from end-user devices transparently and with privacy in mind.
USB devices are unlikely to contain private or sensitive data but due to the commonplace utilization of USB for charging and software updates, a device may be attached whose name may contain or suggest certain personal or private behavioral information which a user does not intend to disclose.
Hypothetical examples of this may include: - A USB chargeable/configurable Adult Toy - A USB wearable health device intended to track Fertility cycles
When you use Kolide to list USB Device data from end-user devices, Kolide gives the people using those devices insight into exactly what data is collected, the privacy implications, and who on the IT team can see the data. This all happens in our end-user privacy center which can be accessed directly by employees.