Point it at one switch. Get the whole building.
CrossScan starts at one switch and follows the wire from there. By the end of the afternoon you have the port-by-port drawing nobody ever finished, and nobody had to drive to a closet.
One pass, one afternoon
It runs from a laptop on your own network, installed with a double click. Nothing goes on the switches or devices it reads.
Give it one address and an account that can look. It finds the rest itself.
It changes no configuration and mirrors no port. Packet contents are never read.
A single-site sweep finishes inside a working day, and you keep the file.
Every job starts by finding out what is plugged in.
The drawings are from the install. The spreadsheet is from whoever left last. The switch has been patched by four contractors since, and none of them told anyone.
So the first week of every project goes on discovery. It gets billed as project management, because there is no line item called "find out what we own."
Run it once and the next four jobs get cheaper. The inventory is the thing the other seven tools stand on.
The gear, the room, and how certain the match is.
- 1It found four more behind this one
It asks the switch, then it asks the next switch.
You give it an address and a read-only account. It reads the port table, the neighbor advertisements and the address tables.
Neighbor data names the switches behind that one. It walks to each in turn until it stops finding new ones.
Each port reading is checked against a reference library and against whatever record you already keep.
Every device carries a confidence figure. The ones it could not settle stay on the list.
On one demo pass it named 30 devices and refused to name 13.
Thirteen unnamed devices is a finding about the building. It is also the first useful list anyone has handed you about it.
- 1Start with the thirteen it could not identify
Each one is listed with its port, its hardware address and whatever is known. Thirteen things are plugged in and nobody knows what they are. That list is your first week.
- 2Give the rooms back their names
It infers a room from what devices call themselves on the wire, and scores that inference separately from the identity, so a confident device can never smuggle in a guessed location.
- 3Scan again next month
It matches on hardware address. A display carried from Room 3 to Room 5 shows up once, as a move, with both ports.
Wednesday to Friday, on a hospital campus.
Before every audit, somebody senior spent six weeks in the closets. The sweep started on a Wednesday, and the list was done by Friday. Read the whole engagement, including the devices it would not name.
Audit preparation, the old way and with the sweep.
Devices that were on no list at all.
Switches nobody had written down.
Vendor-run devices the IT team had no view of.
One Fortune 500 hospital campus. Anonymized at the customer's request.
Will it change anything on my switches?
Will it change anything on my switches?
No. Every build ships with a test that fails if any write path exists. The account you give it only needs read.
Does it need to be installed?
On one laptop, with a double-click installer for Windows or macOS. Nothing goes on the switches or the devices it reads, and nothing stays behind on them when it finishes.
What if it cannot identify something?
It lists the device anyway, with its port and its hardware address, and the confidence figure drops. A guessed name never goes on the report to make it look complete.
Is this just the small version of CrossConnect?
No. CrossScan is one pass that ends in a file you keep. CrossConnect stays running and compares each day's network with what you meant to build. Most people start here and decide later whether they need the second.
How much of my network does it need to reach?
One switch, and the ability to reach the switches that one names. If a segment is walled off, it reports what it did reach and marks the boundary.
See it work
The real screens, with the real answers.
This is CrossScan's own output, put on the page. CrossScan ships a demo switch, AV-SW-01: 40 ports, 43 devices, and a scan of the same switch from last week so Changes has something to compare. We ran that through the real engine and every port, score and line of evidence below is what it returned. Take the tour, or press Run scan and click around. Nothing here touches a network.
Start here. One scan, and the screens it fills in. The tour takes about a minute, and you can stop and click around at any point.
CrossScan
read-only AV / UC / IoT discovery
No scan loaded
v0.3.5
You know the building. You do not need to know the network.
Give it one switch. It finds the rest, then works out which room each device is in, what the gear is, and who owns it. It only reads: it never signs in, never changes a setting, and nothing you scan leaves this computer.
New here? The three things you need
Fill these into the form below, then press Run scan.
1 Enter the switch's address (its IP), for example 10.10.10.5, in the Switch address box. required
2 Enter the read-only monitoring password for that switch, sometimes called the SNMP community. Your network team sets this up, so ask them if you do not have it. required
3 Say which addresses the scan may read, for example 10.10.120.0/24. CrossScan does not stop at the switch you name: it follows the wired connections to the switches behind it, so this is what decides how far it goes. If you want it to follow them wherever they lead, you can say that instead. required
4 Press Run scan. Everything else on the page is optional and already set to sensible defaults, so you can ignore it.
No switch to look at right now? Click Demo in the left menu. It loads sample data so you can look around, and it does not touch any network.
Scan a switch
2 Read-only monitoring password required
Sometimes called the SNMP community. It is never shown again and never saved to any file or export.
The security level (noAuthNoPriv / authNoPriv / authPriv) is derived from which passwords you supply.
3 Which addresses may this scan read? required
CrossScan starts at the switch you named and follows the wired connections to the switches behind it. These ranges are the fence. An address outside them is never read, and never appears in the results or on the map: you said stay inside the fence, so it stays inside the fence.
One range is fine. Add as many as you need. Each one can be a block (10.10.120.0/24), a single address (10.10.130.5), or a span (10.10.140.10-50). IPv6 works the same way.
Leave the ranges empty and tick this to scan a network whose shape you do not know yet, which is often the whole point. Then the only things deciding where the scan stops are how deep it follows and whether the monitoring password works on the next switch along.
Advanced options (most people can skip these)
A scan spends nearly all its time waiting for switches to answer, so it reads several at once. Lower this if your switches or your monitoring dislike many sessions arriving together; one reads them strictly in turn. It is remembered for next time.
Off by default. Most devices on a switch never get an IP from it, so turning this on would hide most of them.
CrossScan follows the wired connections from the switch you name out to the ones behind it. Leave this at 3 for most sites. Anything past this point still shows on the map, marked 'seen but not scanned'.
Active probing (opt-in): contact endpoints directly
The only setting that lets CrossScan contact a device directly. It stays off unless you turn it on, and asks you to confirm before the scan runs.
The demo switch's stored scan was taken with active probing on, so it is on here to match what you will see.
What this does, and what to know first
This is a read-only look. CrossScan reads the switch you name and the switches wired behind it. It never logs in, changes anything, or contacts the devices themselves.
Read-only discovery. No switch admin login, SSH, Telnet, enable mode, SNMP write, or configuration changes were used.
One switch in, and the whole building comes out.
You just watched it turn one switch address into an inventory with the evidence attached. It does that to a real building in an afternoon.
Sample data from CrossScan's own demo switch. This demo does not connect to any network, and nothing you click changes anything.
Where the list goes next
If the list makes you doubt your drawings, CrossTrust shows where the documents contradict each other. To keep the list current from now on, add CrossConnect. Or stop here. One pass may be all you need.
CrossScan next to the other sevenCrossScan hands you a port-by-port list of what is plugged in, which is where CrossTrust picks up: “Can I believe any of this paperwork?”
Bring one switch and one closet.
Bring a read-only login for one switch. We run CrossScan against it while you watch, and you keep the port list, including every device it would not name.