NP-View and NP-Live have a similar feature set: 1) parsing configuration files from firewalls, routers, switches, 2) visualizing the network topology map, 3) reviewing rulesets, 4) visualizing path analysis.
The two key differences are:
- NP-View is a desktop application (one user at a time can work on a project) and NP-Live is a server application (multiple users can collaborate at the same time on a workspace)
- The import of configuration files into NP-View is a manual process. NP-Live includes data connectors to automate that import process.
The foundation of a NP-View project or NP-Live workspace is configuration files from layer-3 network device equipment (firewalls, routers, switches). The full list of supported devices is available here and is frequently updated with new manufacturers.
In addition to configuration files, one can also import network data to enrich the topology map with new nodes, ports and services information, and vulnerability information. The full list of additional data supported is available here.
If the import of a configuration file fails, the next step is to send the debug logs to the support team (email@example.com). This can be done automatically through the Log tab in NP-View Java, and the Help Center in NP-Live and NP-View HTML (available through the user menu in the top right corner).
NP-Live is a server application that runs on Linux. The minimum requirements are 2GB of RAM and having Docker installed.
NP-View Java is a desktop application that runs on Windows, Linux, and Mac. The minimum requirements are 2GB of RAM and having Java installed.
NP-View HTML is desktop application that runs on Windows. The minimum requirements are 2GB or ram.
No, NP-View and NP-Live are designed to work offline or in an isolated network. Automated updates are not possible if off-line.