Peripheral Control

Peripheral Control lets you define organization-wide policies for USB, Bluetooth, and Thunderbolt peripherals. Policies set whether device classes are allowed, blocked, mounted read-only, or flagged for alerting, while the Breeze agent evaluates them locally, logs every connect and disconnect, and reports activity back for centralized visibility and auditing.

Policy-Based Control

Each policy targets a device class (USB storage, all USB, Bluetooth, or Thunderbolt) and applies one of four actions: allow, block, read-only, or alert. The first policy whose device class matches a detected peripheral wins, so you can layer broad and specific rules without conflicts.

Hierarchical Scope

Policies are scoped through the multi-tenant hierarchy. Target an entire organization, individual sites, device groups, or specific devices, and Breeze distributes each new or updated policy to agents through its job pipeline so they enforce on the next sync.

Exception Rules

Exception rules let approved peripherals bypass a policy’s default action. Each rule matches on vendor, product, or serial number and can carry a reason and expiration date, useful for permitting an encrypted field-tech drive while blocking everything else. Rules are checked before the policy action is applied.

Activity Logging

The Breeze agent logs every peripheral event (connected, disconnected, blocked, mounted read-only, and policy override) with full metadata including vendor, product, and serial number. Query the activity log by organization, device, policy, event type, or peripheral across a window of up to 90 days for auditing and compliance.

Real-Time Alerts

When an agent reports a blocked peripheral, Breeze publishes a high-priority event through the event bus for real-time alerting, so unexpected device connections surface immediately rather than sitting in a report. Alert-action policies let a peripheral connect normally while still generating an event for review.

Cross-Platform Detection

The agent detects peripherals using platform-native APIs: Windows Device Manager and the Bluetooth stack, macOS IOKit and IOBluetooth, and sysfs/udev on Linux. Each peripheral is identified by vendor, product, serial number, and device class, then evaluated against locally cached policies in real time.