Know what’s connected.
from rooms to buildings to the network
Read-only software that finds and identifies every device on your network.

Most people start with a discovery pass: it takes an afternoon, and it is what makes the other seven useful.
-
CrossScan
What is even on my network?
Start it at one switch. It follows the wire to every switch behind it and names the gear on each port.
Run once, in an afternoon -
RoomIQ
Is the thing in this room the thing we installed?
Every device has an electrical fingerprint software cannot fake. RoomIQ reads it and confirms the room matches the paperwork.
Runs continuously, per room -
SpacesIQ
What is on every port, in every building?
Watches every port in every building without stopping, so anything new shows up the day it appears.
Runs continuously, every building -
CrossConnect
Is it right, and what breaks if it fails?
Keeps discovering the network and holds what you meant to build apart from what it found.
Runs every day, from now on -
CrossTrust
Can I believe any of this paperwork?
Reads your own drawings and configs against each other and shows where they contradict, both sides cited to the line.
Run before you trust the documentation -
CrossCheck
Will this change break the room?
Rehearses a firmware change against a model of your own gear and answers Go, Caution or No-Go, with the fix.
Run before you touch anything -
CrossRoom
Why was that call so bad?
Rebuilds the call thirty seconds at a time, scores what the people in the room heard, then names one layer and one device.
Run after the meeting -
CrossVenue
What is tonight costing me?
Reads the controls, the meters and the calendar, and turns them into the calls somebody has to make today.
Run before every event
DETECT·CORRECT·PROTECT
Somebody has to know what is plugged into your network and whether it can be trusted. We make eight tools for that job. All eight only look.

Runs on hardware you already own. There is no box to buy, and nothing gets installed on the equipment we identify.
We sign in to the switches already carrying your traffic, using an account that can look but cannot change anything.
It never changes a setting on anything. It never copies the traffic on your network, and it never sits in the middle of it.
One demo pass declined to name 13 devices out of 43. It listed all thirteen anyway, with the port each one sits on.
Which of these sounds familiar?
Most people arrive with one of these already burning. Find yours and read only that.
The audit found a camera in the boardroom. We never bought it.
RoomIQThe phones died Monday morning and everyone swears nothing changed.
CrossConnectThe utility bill lands and nobody can say which nights ran it up.
CrossVenueWe took over this campus a year ago and we are still finding devices.
CrossScanAn executive said the call was unusable. Every device was green.
CrossRoomSomething appeared on the network last night and nobody can say what it is.
SpacesIQEvery job starts by working out which of our documents is lying.
CrossTrustThere is a firmware upgrade Saturday and the last one took the boardroom down.
CrossCheck
Point it at one switch. See what is plugged in.
Every question above needs the same thing first: a real list of what is connected. Hardly anyone has one.
Buy one and stop there if you like. Every one of the eight stands on its own, and it works the same with or without the other seven.

- 1It found four more behind this one
demo system
You already own four things that were supposed to tell you.
Each one does its own job well. None was built to tell you what is plugged into every port, and what falls between the four is exactly what the auditor finds.
Network access control
SeesAnything that signs on to the corporate network the proper way.
MissesThe switch a contractor put in the AV closet, and the four things hanging off it.
Endpoint protection
SeesAnything that can run its software: laptops, servers, phones.
MissesMost of the room. A camera, a badge reader and a signage player all refuse it.
The asset register
SeesWhatever purchasing wrote down on the day it was bought.
MissesOn one campus it accounted for roughly two thirds of what was live on the ports.
Your own drawings
SeesWhatever was true on the afternoon somebody drew it.
MissesEvery change since. Each job now starts by working out which document is lying.

room summary
The switch already knows. We ask it.
Your building already keeps this information. We read it without changing anything and turn it into something you can act on this week, whether that is a room that drifted, a switch nobody recorded or a device the register never had.
Nothing gets installed on your equipment, by any of the eight. One security review covers all of them.
Your switches already know what is on every port. It asks the switch, and never touches the device itself.
That reading goes against a library of known equipment, and against your own records. When the two disagree, you get both.
Every line says where it came from, and a poor match drags the score down until somebody fixes it.
What to fix, what broke it, and what the auditor gets.
Everything it found overnight, worst at the top, in sentences you can act on.

- 1How many, by how bad
- 2What to do about it
demo system
It worked Monday and broke by lunch, and everybody you ask says they changed nothing.

- 1The change it found
- 2Worked, then broken
version 15.2hostname cor-bb-aes67-01!10 lines unchangedip route 10.11.20.0 255.255.255.0 172.21.0.2end
Removed: the route to the audio network.
version 15.2hostname cor-bb-aes67-01!10 lines unchangedrouter bgp 65111 neighbor 172.21.0.2 route-map REJECT-AES67 in!route-map REJECT-AES67 deny 10 match ip address prefix-list AES67-PREFIX!ip prefix-list AES67-PREFIX permit 10.11.20.0/24end
Added: a rule telling the router to refuse that route.
demo system
Dated, one line per device, so you can hand it over without assembling anything.
One hospital campus stopped walking closets before audits.
Before every audit, somebody senior spent six weeks walking closets and rebuilding the device list by hand. We swept the campus on a Wednesday, and by Friday they had a real list. They never ran the six weeks again.
Audit preparation, before and after.
Devices with no record anywhere. Found, named and dated by Friday.
Switches nobody had recorded, put in by contractors over the years.
Devices run by outside vendors that the IT team could not see.
One Fortune 500 hospital campus, Wednesday to Friday. Anonymized at the customer’s request. Read the engagement
- Audit-ready buildingsThe six-week rebuild, gone.
- Securing the boardroomEvery device behind the camera, accounted for.
- Vendor and supply-chain riskThe gear nobody on the inside owns.
- Banned equipmentFound on the wire, whatever the paperwork says.
- Cyber-insuranceInsurers stopped taking your word for it.
No software on your gear. Nothing written. A list by Friday.
Does this put software on my devices?
No. We read your switches. Nothing is installed on the devices we identify, and we never copy your traffic. The one optional exception is a small USB agent for workstations, part of RoomIQ and SpacesIQ, for spotting USB attack hardware.
Can it break something?
Nothing we ship can write to a device, in any product, under any setting.
What happens when it is not sure?
It says so, and the score drops. The device stays on the list with the port it sits on, so somebody can go and look.
How long until there is a real inventory?
Agree on Monday what to look at. You have a real list by Friday.
We publish what we could not identify.
An auditor cannot use a score that never admits doubt, so every gap gets a name, lowers the number and arrives with the one thing that would close it.
What a device is called when its signature is too thin to name. It stays on the map with its port, so somebody can go and look.
CrossScanThe highest score it gives a verdict built on a remembered firmware version. Passing takes 75, so read the real version first.
CrossCheckIts ceiling when any part of the call went unmeasured, so a half-seen room can never pass as fine.
CrossRoomTwo documents disagree and neither outweighs the other. It says so, and names the check that would settle it.
CrossTrustWe did the clipboard walk ourselves.
Before every audit, somebody spent six weeks in closets writing down by hand what the switches already knew. For years that somebody was us. Nobody else was going to build the tool that ended it, so we did.
Where this came from, and who is doing it
Try it on something of yours, or keep reading.
Thirty minutes, with the right product pointed at it.
Book a 30-minute working sessionThe method, a sample evidence pack and the compatibility list, all on one page.
Evaluate it yourself