Every conference room has devices nobody has counted.
RoomIQ reads the switch each room hangs off and names what is on every port. Swap a display or add a presenter and the record follows. The audit team gets a per-room inventory nobody assembled by hand.
Always on, room by room
On your hardware, or hosted by us in a region you pick. It watches the rooms you point it at.
One read-only account on the switch already carrying the room's traffic.
It never talks to the codec, the display or the camera. It asks the switch about them.
When the signature is thin it says weak, and a weak match never counts as confirmed.
An all-green control system proves the room turned on.
The control surface says the room is operational. It cannot say which devices are connected or what they really are. Whether anything changed since the last sweep, it has no idea.
The codec ships with the integrator. The drop sits behind a small unmanaged switch. The wireless presenter, the camera and the table sensor share one VLAN. None of them is on the asset register, and network access control cannot see them.
A supply-chain implant in a conference camera passed every paper, serial and software check. Only the electrical fingerprint caught it.
Ready, at risk, drifted, offline.
- 1A packet capture tool, named as an attack device
- 2What it was seen doing, and when
It trusts the wire over the label.
Link state, negotiated speed, power draw and class, neighbor advertisements, hardware address, VLAN, and error counters over time.
Those readings combine into a Device DNA signature, which is compared against a reference library and against your own record.
Agreement is marked confirmed. Disagreement is named with both sides cited. A thin match stays marked weak.
Weak stays weak until the signature fills in.
Every room report carries some doubt. Here is the order to work through it.
- 1Take the weak matches first
A weak match means the signature was thin, usually because the device was idle or the port has been up for minutes and not days. Leave it a day and look again before sending anyone.
- 2Then the drift
Drift means the room no longer matches what it matched last week. Something was swapped, added or unplugged. The record names which.
- 3Then decide what "installed" means here
Confirm the room once, deliberately. From then on you ask "what changed?" instead of "what is in this room?", and the meeting gets much shorter.
Does anything get installed in the room?
Does anything get installed in the room?
No. Nothing is installed on the codec, the display, the camera or anything else in the room. RoomIQ reads the switch the room hangs off. The one optional piece is a small USB agent for workstations, if you want USB attack hardware detected, and it never goes on room equipment.
Will it work with our AV equipment?
It does not need to. It never talks to the AV equipment directly. It reads the switch, so what the room is built from matters far less than which switch it lands on.
What does the auditor get?
A dated, per-device, per-port record, by room, showing what was on the wire and how it was identified. It is the same record the screens are built from, exported.
Can it tell a real camera from a tampered one?
It can tell when a camera's electrical behavior does not match the rest of the fleet, which is how the supply-chain case above was caught. A person acts on it. RoomIQ hands over evidence and stops there.
Does it block anything?
No. Nothing we ship blocks, quarantines or remediates. RoomIQ reports, and your team decides.
From rooms to whole buildings
For the same record on every port in the building, including ports that belong to no room, look at SpacesIQ. A bad call in a room RoomIQ watches is a job for CrossRoom.
RoomIQ next to the other sevenRoomIQ hands you a record of every device in every room, which is where SpacesIQ picks up: “What is on every port, in every building?”
Bring one conference room.
Pick the room that matters most to you. In thirty minutes we read the switch it hangs off and show you every device on it, with how sure we are of each one.