Third-party
sensors,
without
third-party network access
An international legal firm needed accurate, real-time meeting room occupancy data — but the best-suited sensors only worked by connecting straight to the manufacturer’s own servers. dbr, working with delivery partner Technik IMS, closed that gap without ever letting the sensors touch the firm’s private network.
Data the firm needed, from sensors it couldn’t allow
An international legal firm needed accurate, real-time meeting room occupancy and attendance data to plan future floor space — without it, they risked over- or under-provisioning valuable office space, and manual observation wasn’t practical across multiple rooms and floors.
The best-suited occupancy sensors sent data straight to servers operated by the manufacturer, Milesight, with usage figures returned to the client via an API. That put the firm’s IT security policy directly at odds with the operational need: no third-party device was permitted to connect to the private corporate Wi-Fi, yet that connectivity was exactly what the sensors relied on.
A physical shield, not a firewall rule
Working with business partner Technik IMS, dbr deployed its Olympus data collection module on site, using BusByte technology to create a secure, isolated collection layer between the sensors and the manufacturer’s third-party servers.
This created a physical shield: sensor data was captured and forwarded without ever bridging onto the firm’s private network — delivering the occupancy and attendance data the client needed, without the connectivity risk that came with it.
A risk removed, not managed
Had the firm connected Milesight’s sensors the way they were designed to work, every one of them would have become a standing dependency on a third party: a device on the corporate network, phoning home to servers the firm didn’t operate, patched and secured on a schedule it didn’t control. That’s not a single incident waiting to happen — it’s an ongoing exposure someone has to keep tracking for as long as the sensors stay installed.
dbr’s collection layer takes that dependency off the table entirely. No Milesight device, firmware update, or manufacturer server ever gets a path onto the firm’s private network — not a restricted one, not an audited one, none at all. There’s nothing there for a future vendor breach or a firmware vulnerability to reach, because the connection it would need never exists. The risk isn’t mitigated by policy or monitoring; it’s designed out of the architecture.
What changed on the ground
Reliable, room-by-room occupancy and attendance data for space planning
No third-party connectivity to the firm’s private network
Wider choice of sensor hardware, regardless of manufacturer or origin
Low-disruption deployment, with no network reconfiguration required
Innovation delivered without compromising security standards
“This project needed a solution that respected the client’s IT security policy without compromising on the data they needed. Working with dbr gave us exactly that — a way to bring third-party sensor data in without a single device touching the client’s network.”
— Amar Mackay, COO, Technik IMS