How it works
Traffic goes in; a model of the network comes out. Nothing in between leaves the computer, and nothing is sent onto the network.
Give it traffic
Open capture files (pcap or pcapng, gzip is fine), or drop them anywhere on the window. Or listen on a network interface of the computer, live. Listening needs administrator rights, and can also hear traffic that is not addressed to the computer.
The engine reads every packet
It learns addresses, hardware addresses, names, services and who talks to whom. Industrial protocols are decoded down to the command: in the plant demo that is S7comm, EtherNet/IP, Modbus, DNP3, including 3 S7comm commands such as a PLC stop.
It builds a model, and says why
Networks, hosts, routers and conversations come only from what was heard. Each inference carries its reason, for example: “2 hosts seen with their own MAC address; /24 assumed (no boundary evidence).” Findings are written from the same model.
The window shows the model
Two modes read the same model. Overview is a one-screen brief: the counts, what needs attention first, and the zones as stacked layers or as rings around Control. Analyze is the full workspace, where the map, inventory, findings, timeline and inspector all read one shared selection. Anything in Overview opens in Analyze. The window runs in a browser on the same computer, and everything it loads comes from the program itself.
What limits the map
A network is only as complete as the traffic that was heard. A device that stayed silent during the capture is not on the map; a network seen through one switch port shows only what crossed that port. Venom Scope lists these limits next to the map rather than hiding them. For the plant demo it says:
The traffic covers only 1 minute: devices that talk rarely will be missing.
Lines on the map are conversations that were seen. Two networks are joined only when a router was seen fronting both. Where none was seen, a trace says so and draws no line.
Projects and baselines
A project is the map as it stood, in one file. Open it later as a snapshot, or set it as a baseline: the next capture is then compared with it, and the window marks every host, network, conversation and finding that is new, gone or changed.
Sharing a map
Three ways, for three readers:
- A project
- For a colleague with Venom Scope. Opens as a snapshot, with your tags and notes if you choose.
- A page to share
- One HTML file with the map inside, for someone without the program. The demos on this site are such pages; the plant demo is 773 KB.
- A link
- Holds the view, the selection, the trace, the time range and the panels in front, so opening it returns to the same place.
Back to the packets
When a finding needs proof, select a host, a pair of hosts, a conversation, a network, a router or the finding itself and save its packets. Venom Scope counts them first, then writes exactly those packets as one pcapng file to open in Wireshark.