Home › Topics › Discovering Shadow IT Through Network Data › Finding Unofficial Hardware

Finding Unofficial Hardware: NAS Boxes, Mini-Switches, and Mystery Devices


Cloud services at least have the decency to announce themselves by name. Hardware just shows up. A storage box appears under a desk because a team ran out of shared space. A five-port switch appears behind a monitor because one wall jack was not enough for a docking station, a phone, and a test machine. A personal router appears in a corner office because the Wi-Fi "was bad in here." None of it was announced, none of it is in your asset register, and all of it is now yours to look after. I have found every one of these at some point, and never on purpose.


This guide is about finding them on purpose and, which is harder, working out what they are. The evidence is what turns "unknown hardware address on port 17" into "consumer storage box serving files to the design team." You will learn how to diff what the network sees against what the books say. You will learn how DHCP hostnames and vendor prefixes give devices away, and how traffic patterns reveal a device's role. You will see why a desk switch is the easiest catch of all. You will also learn how to walk the floor with an alert in hand without making anyone feel raided.


You will also learn the one distinction that decides what happens next: is the device somebody's convenience, or a data path outside your control? The two deserve very different responses, and confusing them is how IT gets a reputation for confiscating harmless things while missing the box that matters.


In this guide

  • What counts as unofficial hardware
  • Inventory diffs: the network versus the books
  • DHCP hostnames and vendor prefixes
  • Traffic patterns that reveal a device's role
  • The desk-switch giveaway
  • Walking the floor with the alert in hand
  • The device-clue table
  • Convenience or data path?
  • Where to go next

What counts as unofficial hardware


The test is the same one used for the whole topic. The device is used for work, it touches company data or the company network, and it is not on IT's list. For hardware, the second test is almost automatic: anything plugged into a wall jack or joined to the staff wireless network touches the company network. So the question usually reduces to the third: is it on the books?


"The books" means whatever your organization uses as an asset register: a spreadsheet, a database, an inventory module in your monitoring or ticketing system. If that register is thin or stale, the diff below will be noisy, and the guide on keeping inventory current is worth a read first. But do not wait for a perfect register. Even a rough list turns a flood of unknowns into a short list of genuine surprises, and each surprise you resolve makes the register better.


This guide is about hardware that is unofficial in the shadow IT sense: bought or brought by staff to solve a problem. Devices placed by someone with hostile intent are the concern of the sibling topic on rogue device detection. That topic also covers the alerting mechanics that tell you a new address has appeared. The evidence is the same either way; the intent is not, and you usually cannot tell which you have until you find the device. Treat every unknown as a question, not an accusation.


Inventory diffs: the network versus the books


A diff is simply a comparison of two lists that reports what is in one and not the other. For hardware, the two lists are what the network can see and what the register says should be there. The network side comes from four places you almost certainly already have:


  • Switch MAC address tables — each switch remembers which hardware address was last seen on which port. The MAC address is the factory-assigned identifier burned into every network interface. Read over SNMP, the tables provide the most complete list of what is physically plugged in.
  • ARP tables on routers and firewalls — the mapping between IP addresses and MAC addresses on each subnet, which catches anything that has talked across a subnet boundary.
  • DHCP lease tables — every device that asked for an address, with the name it gave itself and the time it asked.
  • Wireless controller client lists — the same idea for the air: which devices are associated with which access point.

Pull all four and merge on MAC address. You now have a "seen" list: MAC, current IP, hostname if any, switch and port or access point, first seen, last seen. Compare it to the register and you get two outputs. The first is seen but not on the books, which is your unknown-hardware queue. The second is on the books but not seen for a while, which is also useful. It may be decommissioned gear nobody removed from the register, or a device that has quietly walked out of the building.


Run this diff on a schedule, not once. A weekly run catches the storage box that appeared on Tuesday. The alerting version of the same idea polls every few minutes and fires the moment a never-seen MAC shows up. It is covered by new-MAC alerting. It is the right tool when minutes matter rather than days. For the shadow IT program, the weekly diff is the workhorse, because it produces a reviewable list rather than a stream of interruptions.


DHCP hostnames and vendor prefixes


Once you have an unknown MAC, two clues get you most of the way to knowing what it is before you leave your chair. The first is the vendor prefix. The first half of every MAC address is an OUI (organizationally unique identifier), a block assigned to the manufacturer of the network interface. A public registry maps prefixes to makers, and most monitoring and inventory tools do the lookup for you. Your standard laptops and desktops will all carry a handful of familiar prefixes. Suppose an unknown address resolves to a maker of consumer storage products, home routers, televisions, streaming sticks, smart speakers, or cameras. You have then learned a great deal from twelve hexadecimal characters.


Two limits on the prefix trick. Some devices use randomized addresses on wireless networks, which map to no maker and make the prefix useless. Those devices tend to be phones and laptops rather than boxes under desks, which is itself a small hint. And a prefix tells you who made the network chip, which for a small maker may be a component supplier rather than the brand on the box. Treat the prefix as a strong lead, not a verdict.


The second clue is the DHCP hostname: the name a device reports about itself when it asks for an address. Managed machines carry names from your naming standard. Everything else carries whatever the manufacturer set as the default, and those defaults are wonderfully honest. A storage box calls itself the product name with a few digits appended. A personal router calls itself the router's model. A streaming stick announces its brand. Some DHCP servers also record the vendor class field, in which many devices state their type outright. Here is a lease table excerpt after unofficial hardware has moved in; the names are invented, the shape is typical:


lease          MAC                hostname            vendor prefix       first seen
10.20.4.112    a4:xx:xx:71:0c:9e  WS-DESIGN-07        (corporate laptop)  long ago
10.20.4.140    00:xx:xx:1d:88:e2  MyStorage-3F2A      consumer NAS maker  38 days
10.20.4.171    d8:xx:xx:0b:45:11  HomeLink-Router     home router maker   12 days
10.20.4.188    b0:xx:xx:92:ff:04  Streambox-living    streaming stick     5 days
10.20.4.203    (none)             WS-SALES-11         (corporate laptop)  long ago

Three of those rows practically introduce themselves. The storage box has been there for over a month, which means it probably has data on it by now. The streaming stick is almost certainly a conference-room television and almost certainly harmless, but it still belongs on the books.


Tip: keep a small table of the hostname patterns and vendor prefixes you have already identified in your own environment. After a few months it becomes a local field guide, and the next unknown is usually a repeat of one you have seen before.


Traffic patterns that reveal a device's role


A prefix and a hostname tell you what a device is. Traffic tells you what it is doing, which is the part that decides how much it matters. You do not need packet captures for this; flow records and per-port counters from the switch are enough, because the question is about shape, not content. A few roles stand out clearly:


A device serving files to many peers. Many internal workstations open connections to it, on file-sharing ports. Traffic flows mostly out of the device and into the workstations during the day. That is a file server, whatever the box calls itself. If it is not yours, it is holding company data you do not back up. The number of distinct clients tells you how many people depend on it.


A device translating addresses for others. One MAC address, but far more simultaneous sessions than one machine would open, to a mix of destinations that looks like several different users at once. Sometimes the traffic carries the fingerprints of several different operating systems behind a single address. That is a router doing NAT (network address translation — hiding several devices behind one address), and everything behind it is invisible to your inventory. A personal router in this role is the finding that turns a diff into a priority. It is both a hidden population of devices and, usually, an unmanaged wireless network.


A device streaming constantly outbound. The upload is steady and unbroken, to a single outside destination at all hours. Its rate never varies with the working day. That is the shape of a camera or a sensor phoning home. Harmless in a lobby, less so pointed at a whiteboard.


A device that mostly listens. Occasional multicast discovery announcements, very little unicast traffic, bursts when someone uses it: a printer, a smart display, a speaker. These are the low-risk end of the scale and are mainly a register-keeping problem.


The per-port counters on the switch give you a second opinion that costs nothing. Consider a port on a jack labeled for a single desk. If its inbound and outbound byte counters both climb steadily through the day, it is carrying more than one person's workstation. With the role clues above, that is usually enough to know what you will find before you walk over.


The desk-switch giveaway


Of all unofficial hardware, the small unmanaged switch is the easiest to find, because it cannot hide what it does. An access port is a switch port meant for a single end device. It should show exactly one MAC address in the switch's table, or two where a desk phone passes a computer through. When the table shows five or six addresses on one access port, there is a switch on the other end of that cable. The switch itself does not appear (unmanaged switches have no address of their own), but the crowd behind it does. Desk switches breed, too: nobody ever buys the second one, but there it is.


sw-floor2-01# show mac address-table interface Gi1/0/17
VLAN   MAC address         type      port
  20   a4:xx:xx:71:0c:9e   dynamic   Gi1/0/17
  20   00:xx:xx:1d:88:e2   dynamic   Gi1/0/17
  20   3c:xx:xx:5a:20:b7   dynamic   Gi1/0/17
  20   d8:xx:xx:0b:45:11   dynamic   Gi1/0/17
  20   f0:xx:xx:c3:19:4d   dynamic   Gi1/0/17
Total addresses on port: 5      (port description: "Rm 214 jack B - single desk")

Read that with the lease table from earlier and the picture assembles itself. The list shows a corporate laptop, the storage box, the home router, and two more addresses, all behind one jack in one room. That is not one finding; it is a small unofficial network. And the router in the middle of it may be handing out its own addresses to whatever is on its wireless side. A rising count of MACs on one access port, or a port that suddenly starts reporting topology changes, is exactly the kind of condition to alert on. The rogue device detection topic covers how. For the shadow IT review, a weekly report of "access ports with more than two addresses" is a fine place to begin.


Walking the floor with the alert in hand


At some point the evidence runs out and you have to go look. How you do that matters at least as much as what you find. You are walking toward a colleague's desk, not a crime scene. And the goal is to leave with an accurate inventory and an intact relationship. A short procedure:


  1. Bring the facts. Switch and port, the jack label, the MAC addresses, the vendor prefixes, the hostnames, and how long each has been seen. You should be able to say "there is a storage device on the jack under this desk" rather than "something is wrong here."
  2. Go at a reasonable time. Not during a deadline crunch, not first thing Monday, and not when the person is away. Poking around an empty desk is how trust gets lost.
  3. Ask before you touch. "I'm chasing down some devices the network sees that aren't in our inventory — is that a storage box under there? Mind if I take a look?" Nearly everyone says yes, and the ones who hesitate usually just need to know you are not there to confiscate anything.
  4. Identify, label, photograph. Confirm what the device is and note its make and model. Put an inventory label on it if it is staying for now. Photograph the setup and the cabling. Ten seconds now saves a second visit.
  5. Ask what it is for. This is where discovery turns into the conversation covered in the diplomatic conversation. You are not there to decide anything on the spot. You are there to learn what problem the device solves.
  6. Update the register before you sit back down. Whatever you found, it is now on the books, tagged with its status: sanctioned, tolerated pending a decision, or scheduled for removal. An unknown you identified and then forgot to record will be an unknown again next week.

The device-clue table


Most real findings match two or three of these rows at once, and the combination is far stronger than any single clue.


ClueWhere you see itWhat it usually means
MAC on network, not in registerWeekly inventory diffUnknown device; start here
Vendor prefix: consumer storage makerOUI lookupNAS or external drive with a network port
Vendor prefix: home router makerOUI lookupPersonal router or access point
Vendor prefix: TV, streaming, speaker makerOUI lookupMedia device; low risk, still record it
Hostname is a product defaultDHCP lease tableConsumer device, never renamed, never managed
Vendor class names a device typeDHCP optionsConfirms the prefix guess
Many clients connect to it on file portsFlow recordsActing as a file server
One MAC, many sessions, mixed fingerprintsFlow recordsRouter doing NAT; hidden devices behind it
Second DHCP server answering on a subnetDHCP logs, client complaintsPersonal router with its LAN side plugged in
Steady outbound stream, all hoursFlow records, port countersCamera or sensor
More than two MACs on an access portSwitch MAC tableUnmanaged desk switch
Port counters busy on a single-desk jackSNMP interface countersMore than one device behind the jack
New wireless network name near the officeWireless controller scanPersonal router or hotspot broadcasting

Convenience or data path?


Everything you find falls on one side of a single line, and which side decides the response. The question is: does company data live on this device or pass through it in a way you cannot see or control?


On the convenience side: a desk switch with two docked laptops and a phone behind it. A streaming stick on the conference-room television. A wireless printer someone brought because the shared one is three rooms away. These are inconveniences of yours that somebody solved for themselves. They belong on the books, and some deserve a better answer — more jacks, a proper media device, a closer printer — but they are not emergencies. Removing a desk switch with nothing on it but the user's own equipment achieves very little except a resentful user with two fewer working ports.


On the data-path side: the storage box that has become a team's working file store. The personal router whose wireless side carries who-knows-what into your staff network, past every control you built. A camera pointed at a whiteboard, uploading to a consumer account. These hold or carry company data in a place you do not back up, patch, or control access to. They are the findings that justify a real conversation and, usually, a migration onto something managed. The router is the most urgent of the three, not because of what is on it but because of what it lets in.


The honest complication is that convenience turns into data path over time. The desk switch that started with two laptops now has a storage box behind it. The "temporary" drive has a year of project files. That is why the register matters. A device recorded as "tolerated, convenience" gets checked again at the next review. If its role has changed, so does its status.


Tollgate Foods learned this the first time it ran the access-port report. It came back with eleven ports: eleven desk switches, none on the books. People had bought them one at a time after asking for a second jack and being told it was "in the plan." One of them, a five-port unit on the floor behind a plant pot, carried the entire boardroom. That meant the video system, the presentation laptop, and the conference phone. Nobody had seen it, because nobody had looked behind the plant pot. The register now lists it as "boardroom core switch," which is at least honest.


Where to go next


You can now turn an unknown MAC address into an identified device, a known role, and a decision. The service-side equivalent, using DNS and flow logs to find cloud tools, is in finding unsanctioned SaaS. What to say at the desk when the box is full of a team's work is the diplomatic conversation. For making the weekly diff a routine someone owns, see the program guide. All of it lives under Discovering Shadow IT Through Network Data. Hardware will keep showing up without announcing itself. The difference now is that you are listening.


Put this into practice with SysPeep Monitor

Every clue in this guide comes from your switches, DHCP server, and flow exports — data that just needs collecting on a schedule. SysPeep Monitor auto-discovers the devices and interfaces on your network. It polls switch tables and port counters over SNMP, and shows them on maps and dashboards in one web console. A jack that suddenly carries five addresses has somewhere to be noticed. The free trial installs on any Windows machine in minutes.

Download Free TrialLearn About SysPeep