Where the file comes from

In the appliance: NAC → Discovery Sources → DHCP Probe → Contribute. You get either a .zip package (the corpus plus a prompt you can hand to an AI assistant) or a .json file. Send whichever you have — the corpus if you would rather we did the work, the rules if you already did it.

What is inside it

The export is not a packet capture. It carries the DHCP options a device requested, its vendor class, hostnames and up to five example names, the manufacturer behind the MAC prefix, device counts, and your installation id and version. No MAC addresses, no IP addresses, no relay addresses, no VLANs, no timestamps.

Hostnames are in there because for an embedded device the name is often the only clue there is. If yours are sensitive, tick “Don't include hostnames” in the product before exporting — the file then says so and we work without them.

Who sees it

We do. This is a private channel, handled like a support ticket: the file goes to storage only we can reach, and no URL leads to it. What becomes public is the rules — a vendor class or a name pattern, and a verdict.

Be precise about that last part, because it is the one thing people get wrong: your list of hostnames is never published, but a rule derived from those names can be, and often is — hostname_glob = KM-SCAN-* may be the only thing that tells a scanner from a printer. If the shape of your naming is itself sensitive, export with hostnames omitted and we work from the rest.