A command-line forensics tool for tracking USB device connection history on GNU/Linux systems.
usbrip is a forensic tool for Linux that tracks and analyzes USB device connection events by parsing system logs. It helps identify when USB devices were connected or disconnected, providing details like vendor ID, product ID, serial number, and timestamps. This is crucial for security audits, incident response, and detecting unauthorized device usage.
System administrators, security professionals, and forensic investigators who need to monitor USB activity on Linux servers or workstations for compliance, security, or troubleshooting purposes.
Developers choose usbrip for its lightweight, scriptable CLI design, open-source transparency, and focus on USB-specific forensics without requiring complex enterprise tools. It fills a niche for automated USB event tracking and violation detection in security-sensitive environments.
Tracking history of USB events on GNU/Linux
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Parses journalctl or syslog files to display detailed USB event history with timestamps, VID/PID, serial numbers, and host information, as shown in the 9-column output table.
Compares current USB events against a JSON whitelist (auth.json) to identify unauthorized device connections, aiding in forensic investigations and compliance audits.
Supports encrypted 7-Zip archives for USB event storage, schedulable via cron jobs for regular, automated backups, as detailed in the storage module.
Allows filtering by date, host, device attributes, and event type, and exports data to JSON dumps for external analysis, enabling precise log queries.
Requires modifying rsyslog configuration for accurate timestamps if journalctl is unavailable, adding setup complexity and potential system changes.
Admits in a warning that it does not intelligently handle devices with identical serial numbers, which could lead to false positives in trusted lists and violation detection.
Many features, such as storage management and violation checks, require sudo privileges, limiting usability in environments with restricted access or containerized deployments.