1. Home
  2. How it works
The methodBehind all eight products

We read your switches and leave them alone.

Your building already knows what is plugged into it. The information sits in the switches, in tables they keep in order to do their job. We read those tables, compare what they say against a library and against your own record, and publish how sure we are. There are no other steps.

What the switch knowsSix readings, all of them already there

Nothing is asked of the device itself.

A managed switch keeps these because it needs them to forward traffic. Reading them costs the switch nothing and tells the device nothing.

  1. 01
    Link state and negotiated speed

    What the port agreed with whatever is on the end of it, and what it has agreed to in the past. A device that negotiates 100 megabit half duplex is a different class of thing from one that negotiates a gigabit.

  2. 02
    Power draw and class

    How much power the device pulls over the wire and which class it declared. A camera, a phone and an access point sit in different places, and a device whose draw changes has usually changed.

  3. 03
    Neighbor advertisements

    Many devices announce themselves to the switch: a model, a name, a capability set. That is the device vouching for itself, so it counts as one signal among six.

  4. 04
    Hardware address and vendor prefix

    The first half of a hardware address is assigned to a manufacturer. It narrows the field. It is also trivial to forge, so it is never used alone.

  5. 05
    VLAN membership

    Which segment the port has been placed in, and whether that matches where a device of this kind is supposed to live.

  6. 06
    Error counters over time

    Errors, discards and resets, watched across days. This is the signal that catches a device that has been replaced with one that behaves differently under load.

Device DNAWhat the six readings become

Six weak signals make one signature.

No single reading identifies anything. A hardware address can be set to whatever you like. A neighbor advertisement is whatever the device chose to say. Power draw alone gives you a range.

Taken together and watched over time they add up to a physical description of how something behaves on a wire. Making one thing behave electrically like another is far harder than changing what it says about itself.

That combined description is what we call Device DNA, and it is compared against two things: a reference library of known equipment, and whatever record of your own you already keep.

This is why it caught a tampered conference camera that had passed every paper, serial and software check. The paperwork was right and the behavior was wrong.

Three outcomesAnd only three

Confirmed, disagreed, or weak.

The signature matches your recordConfirmed

The reading and the record agree. The device is named, the confidence is high, and it stops needing anybody's attention.

They do not matchDisagreed

You get both sides, cited. We never quietly pick one. Deciding which is right is a person's job, and the report is written to make that decision short.

The reading is thinWeak

Not enough signal to claim anything, usually because the port has been up for minutes and not days. It says weak, and weak never counts as confirmed.

On one demo pass over forty-three devices, twenty-five came back confirmed, five came back likely, and thirteen were too thin to name. All thirteen stayed on the map with the port they sit on, because a device nobody can name is still a device somebody has to go and look at. Each product publishes the number it will not go past.

What we never doThe same four answers, every time

Read-only is built into the product.

No writesNothing can change a device

Every build ships with a test that fails if a write path exists anywhere in the product. There is no setting to flip, by accident or on purpose.

Nothing on your gearNothing is installed on it

Nothing is placed on the equipment being identified. The device is never contacted directly at all.

No traffic captureNo SPAN, mirror or tap

Packet contents are never examined. We read counters and tables, which is a different thing from reading traffic.

No enforcementNothing is blocked

We identify and we evidence. Blocking, quarantining and remediation are somebody else's tools, deliberately.

All eight products give these same four answers, so one security review covers every one of them. The evaluation pack is public for the same reason, and so is our accessibility statement.

NextTwo ways from here

See it read one of your switches.

Bring something of yours

A room, a closet or a folder of drawings. Thirty minutes, and the product runs against it while you watch.

Book a 30-minute working session
Or read the rest first

The catalog, and where each product stops.

All eight products