Software, tests and network security for a ceiling microphone, inside the client's team
Sennheiser makes a ceiling microphone for meeting rooms. As part of their engineering team we developed one of its software services in Rust, tested the system on the device itself, and added the network access control that company networks ask for.
- 1The microphone on the ceiling of a meeting room
- 2Its services small programs, each with one job
- 3The network port opens once the device has proved who it is (802.1X)
- 4The company network where the device is installed
- Client
- Sennheiser
- Product
- A ceiling microphone for meeting rooms
- Industry
- Audio and conferencing
- Our role
- Part of the client's engineering team
- Our scope
- A service in Rust, tests on every change and on the real device, network set-up and access control, security logging, vulnerability checks
- Stack
- Rust
- C++
- Python
- pytest
- D-Bus
- Yocto
- HIL
- 802.1X
- Azure DevOps
- CRA
The challenge
A microphone that is also a computer on the company's network
The microphone is plugged into the network of the company that installs it. That network expects the device to prove who it is, keep its clock in sync, answer to its name and log what happens on it.
Its software is a set of small services that each do one job and pass messages to one another, which engineers call a microservice architecture. The client's engineering team develops it, and we worked as part of that team.
What we did
Code, tests and network security
Software
Parts of the product itself.
01A service between the device and its user interface
The services inside the microphone talk to one another over D-Bus. We developed, in Rust, the service that faces the user interface and passes their events on.
- Rust
- D-Bus
- microservice
02A shared security log
A library that services use to record security events and who did what on the device, known as an audit log. It can be called from C, C++ and Rust.
- security logging
- audit log
- C, C++, Rust
Tests
Unit, integration and system tests.
03Tests that run on every change
Unit tests check one part on its own, and integration tests check parts working together. Both run automatically in CI, the system that builds and checks each change to the software.
- unit tests
- integration tests
- CI
04Tests on the device itself
System tests check the whole product on the hardware itself, not on a simulation. This is called hardware-in-the-loop testing, or HIL.
- system tests
- HIL
Network and security
What a company network asks of a device.
05Network basics, built into the device's own Linux
Yocto builds the device's Linux from recipes, one for each part. We wrote the recipes for the firewall, network time (NTP), the device name (hostname), discovery on the local network (mDNS) and other network settings.
- Yocto recipes
- firewall
- NTP
- hostname
- mDNS
06Network access control with 802.1X
With 802.1X a network port stays closed until the device plugged into it has proved who it is. We added this access control to the microphone.
- 802.1X
- port-based access control
07Automatic checks for known vulnerabilities
Automated checks search the software the device is built from for known vulnerabilities, and the notice listing its open-source licences is generated automatically. We did both with the EU Cyber Resilience Act (CRA) in view.
- vulnerability checks
- licence notice
- CRA
In the client's team
Responsible for the stability of the whole system, and for bug fixes across several projects.

Oleksii Kvasnikov · Founder and lead engineer
We can work inside your team, with your tools
Tell us what your product is built from and where your team is short of people or skills.