4. Reports & Dashboards

You are here:
< All Topics

Workspace Reports

NP-Live and NP-View provide reports that present network information related to the open workspace.  These reports are available to all users and can be accessed from the left menu.

Access rules

This report provides a summary of all device rules loaded into the workspace.

Access rules column details
  • ACL: Name of the access list under which the rule is defined.
  • ACL Hits: Number of times the ACL was accessed (only implemented for Cisco so far and requires importing logs).
  • Action: Permit or deny.
  • Application: Filtered application name associated with the rule (only for next-gen firewall).
  • Compared Result: Used only when a previous version of the ruleset is selected to show rules added / unchanged / removed.
  • Description: Remarks associated with rules.
  • Details: Links to the config file and pat table for the selected rule.
  • Destination: Object group destination for the rule.
  • Device: Device host name as defined in a configuration file.
  • Dst Binding: Outbound interface to which the rule is bound.
  • Dst Criticality: Criticality of the object group destination (or the parent zone containing the object group destination).
  • Enabled: Rule is enabled (True / False).
  • Line #: Line number(s) in the configuration text file where the rule can be found.
  • Risk: Compliance or security risk associated with rule based on NP and user defined policies / requirements.
  • Rule: Name of the rule found in the configuration. If the rule doesn’t have a name, the value is RULE_X where X is the rule index.
  • Src Binding: Inbound interface to which the rule is bound.
  • Service: Object group service associated with the rule.
  • Source: Object group source for the rule.
  • Src Criticality: Criticality of the object group source (or the parent zone containing the object group source).
  • Type: Type of rule (regular or VPN).
  • User: Filtered user name associated with the rule.
  • + Comment: Drop down for user entered comments (or justification) and criticality levels (low, medium, high).
  • Comment Count: Label less column that indicates the number of comments available for each asset

A rule with a strikethrough shows that the rule is disabled. It is based on the parsed field “enabled” that can be either “true” or “false”. Columns can be displayed or hidden using the

feature in the upper right corner of the report.

By clicking on +, additional details for each rule is presented including: User-defined comment (justification) and justification tag, Click on the +Add to add a new comment or the trash can to delete a comment.

Asset inventory

This report provides a summary of all assets loaded into the workspace including: Firewalls, Routers, Switches, Gateways and Hosts.

Asset inventory column details
  • Alias: List of alternative names identified in configuration(s), separated by “:”.
  • Category: User assigned category from the topology map.
  • Created At: Time and date when the device was added to the workspace.
  • Created By: Files used to create the device or host.
  • Criticality: User assigned criticality from the topology map.
  • Description: Description from the configuration file if available.
  • Hostname: Device name as defined from a host file.
  • IP address: IP address of the device, gateway, or host.
  • Label: Initially mirroring the Name field but can be changed by the user on the topology map and represented in this field.
  • Name: Device host name as defined in a configuration file.
  • OS: Host operating system derived from third party data files,
  • Services: Host services derived from third party data files,
  • Type: Device type; firewall, router, switch, gateway, host, unmapped host.
  • Updated At: Time and date when the device was last updated (configuration change).
  • Updated By: Type of file used to update the device.
  • + Comment: Drop down for user entered comments (or justification) and criticality levels (low, medium, high).
  • Comment Count: Label less column that indicates the number of comments available for each asset.

If an IP address is displayed as 0.0.0.0 this device has an IP address assigned by DHCP and while the device was detected, an IP address could not be extracted.

Unmapped hosts have enough information for identification but not for mapping purposes on the topology map.

Change Tracking

As modifications are made to the network and the updated configuration files are imported, the NP-Live and NP-View automatically detects the changes and logs them in the Change Tracking table. For each change, the timestamp, action, device, and description are recorded.

The actions recorded are as follows:

File import – for each file uploaded, of the following statuses will be displayed

  • “successful import” – file imported successfully
  • “ignored file: <filename>” – unknown file type, ignored
  • “failed import” – file failed to import, review help center for reason

Topology map – for each file uploaded, of the following statuses will be displayed for the topology map

  • “device path information” – triggered if the connectivity matrix changes
    • Path can be added or removed
    • Assets refers to destination IP addresses
    • Services refers to the unique ports (or any) associated with the imported device
    • Details on the above can be viewed in the Connectivity paths
  • “topology updated” – indicates the topology map has been successfully updated
  • “topology failure” – indicates the topology map has failed, review help center for reason

Connectivity Paths – for each file uploaded, of the following statuses will be displayed for the workspace

  • “workspace analysis updated” – all other tables have been successfully updated

Changes are displayed by calendar day. At the top of the table is a drop down that allows the user to select which day to review. The default is the current day.

The change tracking table can be searched, sorted by any column, switched to a list view, exported, and configured with alternate columns if required. These functions are available in the upper right corner of the table.

Connectivity Paths

This report provides a summary of network paths and their analysis results:

Connectivity paths column details
  • Destination: IP address of the destination
  • Device Sequence: Name of device which contains the rue sequence
  • Ports: The ports that are open along the path
  • Protocol: The protocol enabled on the path
  • Rule Sequence: Access list sequence of rules and reference line number within the configuration file
  • Source: IP address of the source
  • + Comment: Drop down for user entered comments (or justification) and criticality levels (low, medium, high).
  • Comment Count: Label less column that indicates the number of comments available for each asset.

The IP groups are highlighted with light colors to allow for quick scanning of the table.

Compare path history

This interactive report provides a network path comparison between two points in time. When a configuration file is added to the system and is different from the previously imported file, a new “Version” is created.  The user can select two versions to compare.  The resulting table will display the changes between the two files. Removals in the left column and adds in the right column.

Object groups

Object groups classify users, devices, or protocols into “groups” and apply those groups to access control lists (ACLs) to create access control policies for those groups.  This report provides a summary of network ACL object groups including:  Host IP addresses,  network address of group members, and nested object groups.

Object groups column details
  • Name: Name of the object group which may include:
    • Any IP address–includes a range from 0.0.0.0 to 255.255.255.255
    • Host IP addresses
    • Hostnames
    • Other network object groups
    • Ranges of IP addresses
    • Subnets
  • Origin: Name of the device containing the object definition
  • Type: Address, Service, Zone or Protocol
  • Value: Content of the object group
  • + Comment: Drop down for user entered comments (or justification) and criticality levels (low, medium, high).
  • Comment Count: Label less column that indicates the number of comments available for each ass

Note:  The parsing algorithms between NP-View Java and the NP-Live platform differ slightly in that default but unused groups displayed in NP-View have been filtered out in NP-Live.

Risks & Warnings

When a potential risk or warning is identified, it is logged in the “Risks and Warnings” table with a time and date stamp. Each potential risk is assigned a “type” (Risk or Warning) and a Criticality (High, Medium, Low) based on the active policies in the Policy manager. Additionally, the device name and a description of the infraction is listed with the status (New, Confirmed, Resolved, False Positive, Will Not Fix or Fixed).

Risk & Warning Status and Life Cycle

For new risks or warnings, the expectation is that the user will review each item, determine if the issue needs to be addressed and they can manually change the action status accordingly.

  • confirmed: new risks or warnings that are acknowledged by the user as a valid problem to address
  • resolved: risks or warnings that are closed because the problem has been addressed
  • false positive: risks or warnings that are closed because they are not a valid problem to address
  • will not fix: risks or warnings that are closed because it was decided to not address them

Upon subsequent network updates, the system will adjust the status if required. For example:

  • If the user marks a risk as Resolved and upon the next network update the risk is still identified, the status will automatically be changed to Confirmed.
  • If upon the next network update the risk is no longer identified, the status will be changed to Fixed. Fixed items are removed from the list after a period of 7 days.
Risks & Warnings column details
  • Time: Date and Time the potential risk was identified:
  • Type: Risk or Warning.
  • Criticality: High, Medium or low as defined by the identifying policy and requirements.
  • Workspace: Name of the workspace containing the potential risk or warning.
  • Device: Name of the device containing the potential risk or warning.
  • Description: Description of the potential risk or warning.
  • Status: Current status as defined above.
  • Action: Action options as defined above.
  • + Comment: Drop down for user entered comments (or justification) and criticality levels (low, medium, high).
  • Comment Count: Label less column that indicates the number of comments available for each asset

Report Personalization

All of the above tables are continuous scroll and can be searched by table or column.  Searches can be combined.  The report can also be personalized by adding / removing columns, changing column size and order of the columns.  The updated configuration can be globally saved by user by selecting the save button in the upper right.

Workspace Dashboard

NP-Live provides a Dashboard that presents summary information related to the active workspace.  The Dashboard is available to all users and can be accessed from the main menu on the top-left corner.  The Dashboard contains the following widgets:

Topology Summary: Count of all Networks, Paths, Rules and Object Groups for the devices loaded into the workspace.  This widget drills to the appropriate report (Connectivity Paths, Access Rules, Object groups).

Asset Summary:  Count of all devices loaded into the workspace including: Firewall, Switch, Host, Gateway and Routers.  This widget drills to the Asset Inventory report filtered by the device type selected.

Best Practice Summary:  Summary of issues identified that do not follow industry best practice including:  Unused Groups, Unjustified Rules, ACL w/o Deny, Unnamed Nodes.  The Best Practice report can be launched from this widget.

Network Access Overview: Provides a summary of Paths and the associated services on those paths. This widget drills into the Connectivity Paths for the service selected.

Change Tracking: Provides a summary of workspace changes for a specific day and has three components:

    • Risks & Warnings shows a summary or workspace related Risks, Changes, Warnings, Errors, and Comments.  The filter lets the user select to view by type, status and criticality.
    • Path Summary shows the number of paths added or removed.
  • File Upload shows a summary of the number of new files added and files removed from the workspace.

The calendar function allows the user to select day for which to view the change tracking information

Policies: Provides a summary of Active and Disabled Policies as well as Active and Disabled Requirements.  This provides visibility into unmonitored devices and unused requirements.

System Logs

The system logs features shows a detailed sequence of tasks attempted and completed.  This log is primarily used for system debugging and contains information, errors and warnings derived during system operation.  The system log feature has three views, Workspace, User, and System.  The System view is accessible only by the Administrator and shows the overall operation of system across users and workspaces.  The workspace and user views are available to the Administrator and Workspace Admin.  The user view shows the actions taken by the current user on the open workspace.   The Workspace view shows system actions for the open workspace.  The views can be filtered to show only information, errors, warnings or all.  Errors are generated when a system operation fails to complete.  Warnings are generated during data parsing and when policy / requirement infractions are identified.

Background Tasks

The background task functions shows the status of each task spawned by a data import, merge or analysis. A parsing task indicates the imported file is being normalized and hosts inferred.  Merge tasks combine the blueprints into the topology map. Analysis defines all of the paths and reviews the paths against the active policies / requirements to identify infractions for review. If a task gets stuck, the user can select the “i” indicator and cancel a specific task.

Next: Connectors and Notifications

Next, please proceed to the Connectors and Notifications section to learn how to set up data collection connectors and real time notifications. If you have any question, please don’t hesitate to contact support@network-perception.com.

Table of Contents