Your network,in layers.

A model you can walk around, and a diagram you can draw

Each information system is a stack of plates: one per zone, one colour per VLAN, an object per asset. Orbit, move across with the middle button, zoom, filter by severity or exposure. Switch to the 2D diagram to add assets, draw flows and arrange plates; both views share the same positions, so what you draw flat is what you see in 3D.

• Flows routed through the firewalls, routers and switches they cross, each in its own lane
• One colour per flow, on demand
• Plates movable anywhere on their level
• Five sites in the demo, linked by WAN

What is exposed, and who to call about it

Every port is classed by where its traffic comes from: the Internet, another VLAN, or the same VLAN. “Reachable from the Internet” lights the path hop by hop. Click an asset for its system, applications, vulnerabilities, exposed ports and the incident contacts to call, with a copy button for each number.

• Internet services as endpoints: ESET updates, Ubuntu mirrors, Microsoft 365…
• Severity pins from your scanner

From the network to the business

Look at the same IS three ways: physical, application by application, or business service by business service. Say which assets a service runs on; Strata follows the flows to find what else it relies on. Open any asset and it tells you which business services would stop if it went down or were taken over.

• Dependencies worked out from the flows
• A business service picked out on the model

What to fix first

One risk score per asset, from CVSS, EPSS, the CISA list of known exploited vulnerabilities, exposure, reachability from the Internet and criticality. The result is a remediation list in the right order, exported as CSV, and a “Why?” on every asset that shows how its score was made.

• EPSS and KEV from the Cyberwatch connector
• Works offline: no feed to download
• Attack paths from the Internet to the critical assets, and where to cut them
• Blast radius: everything an attacker holding one asset could reach

Documents that write themselves

Pick an asset and get its architecture plan, ready for a PNG or SVG in your documentation. Every flow is drawn as its own numbered line, with the table of its flows and of the firewall rules the asset needs. Filter by direction or by kind of flow. Export its flow matrix and firewall rules as CSV.

• An architecture file per IS for audits and security accreditation: diagrams, flow matrix, exposure, vulnerabilities, contacts, history, ready to print
• Plans stay light, whatever the theme
• Whole map or one site as JSON

Changes are proposed, reviewed, then published

Contributors edit in a draft, or submit a JSON file. Approvers see the changes on the map itself, green for added and amber for modified, comment, then approve or reject. Nobody approves their own work. Every change is a version you can view or roll back to.