See the network your traffic describes.
Venom Scope reads a packet capture, or listens quietly on a network, and draws every network, host and conversation it heard. Then it tells you what deserves a look.
| Heard | 292 packets in 81 s |
|---|---|
| Mapped | 3 networks, 13 hosts, 6 OT devices |
| Flagged | 5 findings, 2 high |
| Sent anywhere | Nothing |
Use it, right here.
This is the program's own window with the plant map saved inside it. Everything works except what needs live traffic.
Loading the saved map (773 KB)…
The program's window needs a wider screen than this. Open it on its own and turn the phone sideways, or come back on a laptop.
Open the plant demo full screenThe window is the real program's interface, saved with its map inside. Click a finding or a host, switch to Analyze at the top, or press ? inside it for the keys.
A larger map, built from 8,635,943 packets, is on the demo page.
Why passive and local matters
Venom Scope maps a network without touching it, and the map never leaves the analyst's computer.
It only listens
It reads capture files or hears traffic already on the wire. It sends nothing, so mapping a plant puts no load on its controllers.
It stays on one computer
An engine and a browser window run together on the analyst's machine. No account, no cloud service, nothing fetched from the internet.
It states its limits
A network is only as complete as the traffic that was heard. The map says what it could not see, for example: “The traffic covers only 1 minute: devices that talk rarely will be missing.”
The result travels
A map saves as one HTML file that opens in any browser, without the program. That is what the demo above is.
Parts of the window
Each part reads and writes one shared selection: pick a host anywhere and every part shows it.
| Part | What it does | In the plant demo |
|---|---|---|
| Overview | A one-screen brief: what was heard, what needs attention first, and the zones drawn as stacked layers from the Internet down to Control, or as rings around Control. Anything on it opens in Analyze. | 5 findings, the most severe first. |
| Map | In Analyze, draws each network as a territory with its hosts, in Regions or Plan view (isometric or flat). A host keeps its place as more traffic arrives. | 3 networks: Supervisory, Control, Enterprise / IT. |
| Inventory | Lists every host with the name, maker, product, model and firmware the traffic revealed. Search covers all of them. | plc-press identified as CPU 315-2 PN/DP. |
| Findings | States what deserves a look, in plain language, with its severity and the hosts involved. | “IT hosts talk directly to control devices in 10.10.2.0/24.” |
| Timeline | Shows traffic by category over time. Drag a range and the map and inventory show only what was active then. | Two bursts of traffic, 81 seconds apart. |
| Trace | Shows the way between two hosts through the networks and routers the map knows, with the conversations that really ran. Where no router was seen, it says so and draws no line. | 1 router fronting all 3 networks. |
| Changes | Compares the map with a project saved earlier and marks what is new, gone or changed. | Set a baseline from any saved project. |
| Save packets | Takes out exactly the packets behind a host, a pair, a conversation, a network or a finding, as a pcapng file for Wireshark. | Needs the running program; saved pages hold the map only. |
| Share | Saves a project file, a single-file page anyone can open without the program, or a link to the exact view. | Both demos on this site are share pages. |
From one minute to one hour
The same method holds from a small plant to a competition network of thousands of hosts.
Open MACCDC 2012| Measure | Plant demo | MACCDC 2012 |
|---|---|---|
| Packets | 292 | 8,635,943 |
| Time covered | 81 s | 60 min |
| Networks | 3 | 52 |
| Hosts | 13 | 2,467 |
| Internet addresses | 6 | 300 |
| OT devices | 6 | 0 |
| Findings | 5 | 17 |
MACCDC 2012 is a public capture from the Mid-Atlantic Collegiate Cyber Defense Competition. The plant demo is made up.