Home
Guardian
Learn how Guardian provides comprehensive asset inventory and network visibility for OT and IoT environments.
Administrator Guide
Information and resources about the Administration section of Guardian, and the tasks that you can do in this part of the software.
Administration
Settings
Data integration
Tanium
This integration enables seamless forwarding of node and asset data to a Tanium instance, facilitating centralized management and enhanced visibility within your network.

Guardian
Learn how Guardian provides comprehensive asset inventory and network visibility for OT and IoT environments.
- Introduction
  An overview of Guardian.
- Installation Guide
  Information and resources on how to install Guardian, and the different options and settings that are available.
- Administrator Guide
  Information and resources about the Administration section of Guardian, and the tasks that you can do in this part of the software.
  - Administration
    - Administration page
      The administration page lets a user with administrator privileges configure settings and do other tasks.
    - Settings
      - Security control panel
        The Security control panel page shows an overview of the current status of the learning process and lets you configure the features that manage the: learning, security profile, zones, alerts tuning, and alert closing options.
      - Features
        The Features page shows an overview of the current status of system features configuration and lets you fine tune specific values.
      - Users management
        The Users management page shows all the pages that you need to let you manage authentication and authorization policies for users and groups.
      - CLI
        The CLI page lets you change configuration parameters and perform troubleshooting activities.
      - Dashboards
        The Dashboards page lets you create and configure widget-based dashboards that provide information about your network. The dashboards created here will show on the Guardian home page, and give an overview of the monitored environment.
      - Threat Intelligence
        The Threat Intelligence page lets you manage packet rules, YARA rules, Sigma rules, structured threat information expression (STIX) indicators and vulnerabilities to provide detailed threat information.
      - Custom fields
        The Custom fields page lets you create a custom field to the Nodes (All-In-One CMC only) and Assets tables. A custom field lets you add information that might be relevant to your organization, and cannot be extracted from network traffic.
      - Data integration
        Data integration overview
        An overview of Data integration in the Nozomi Networks software.
        Data integration
        The Data integration page lets you exchange data with different third-party platforms.
        Google Chronicle (Ingestion API - UDM)
        This integration lets you forward alerts, asset information and vulnerabilities to an instance of Google Chronicle.
        IBM QRadar (LEEF)
        The IBM QRadar integration lets you send all alerts, and optionally health logs, in LEEF format. You can also send asset information to QRadar beginning with version 2.0.0 of the QRadar App.
        Common Event Format (CEF)
        CEF lets you send alerts and health logs in CEF format. You can also enable encryption of the data through the TLS checkbox and check the validity of the CEF server’s certificate with the CA-emitted TLS certificate checkbox.
        ServiceNow
        The ServiceNow integration allows you to receive asset information from a ServiceNow instance and enrich local nodes.
        Tanium
        This integration enables seamless forwarding of node and asset data to a Tanium instance, facilitating centralized management and enhanced visibility within your network.
        Splunk - Common Information Model (JSON)
        If you need to send alerts to a Splunk - JavaScript Object Notation (JSON) instance, you can use integration. Data are sent in JSON format and you are also able to filter on alerts. You can also send health logs and audit logs.
        SMTP forwarding
        To send reports, alerts and/or health logs to an email address, you can configure a simple mail transfer protocol (SMTP) forwarding endpoint. In this case, you are also able to filter alerts.
        SNMP trap
        Use this kind of integration to send alerts through a simple network management protocol (SNMP) trap.
        Syslog Forwarder
        Use this type of integration to send syslog events captured from monitored traffic to a syslog endpoint.
        Custom JSON
        This type of integration uses the JavaScript Object Notation (JSON) format to send the results of the related query to a specific uniform resource identifier (URI).
        Custom CSV
        This type of integration sends the results of the specified query to a specific URI in comma-separated value (CSV) format.
        DNS Reverse Lookup
        This integration sends reverse domain name server (DNS) requests for the nodes in the environment and uses the names provided by the DNS as nodes' labels. You can pre-filter the nodes by specifying a query filter.
        Kafka
        The Kafka integration allows you to send the results of custom queries in JavaScript Object Notation (JSON) format to existing topics of a Kafka cluster.
        Cisco ISE
        With the Cisco ISE integration, you can use the simple text-oriented messaging-protocol (STOMP) to send the results of custom node queries to Cisco's ISE asset information, or you can use hypertext transfer protocol (HTTP) to receive asset information from a Cisco ISE instance and enrich local nodes.
        External Storage
        The external storage integration uploads files to an external machine. This enables the external machine to keep remote copies of files that are kept beyond the retention settings.
        Microsoft Endpoint Configuration Manager (WinRM RPC)
        With the Windows Remote Management (WinRM) RPC, you can collect information coming from the Microsoft Endpoint Configuration Manager to update Windows nodes.
        Microsoft Endpoint Configuration Manager (DB)
        The goal of this integration is to collect information from the Microsoft Endpoint Configuration Manager DB to update the existing Windows nodes.
        NetWitness
        If you require sending alerts to a NetWitness instance, you can utilize this integration. Data is transmitted in JavaScript Object Notation (JSON) format prepended by the NOZOMI: header. You can also apply filters, and determine whether historical data should be sent or not.
        Aruba ClearPass
        This integration lets you send node information to Aruba ClearPass. Only nodes with confirmed media access control (MAC) addresses are sent. You can specify a query filter to pre-filter the nodes. If Enable update Node information is not selected, nodes are only sent once.
        CarbonBlack Defense
        The strategy runs once a day by default. The strategy uses its representational state transfer (REST) application programming interface (API) over hypertext transfer protocol secure (HTTPS) to extract information about nodes from an external CarbonBlack service.
        Nozomi syslog data events and syslog messages
        For customers implementing syslog, Guardian generates three types of syslog events: alerts, health, and audit.
        Configure data integration
        The Data integration page lets you configure one of the available options.
      - Firewall integration
        The Firewall integrations page shows all the firewall integrations and lets you add new ones.
      - Credentials manager
        The Credentials manager is a tool that lets you centralize the management of monitored endpoints to make it easier to create, delete, or update the credentials that are needed to access those endpoints.
      - Zone configurations
        The Zone configurations page shows all the zone configurations in your environment and lets you add new zone configurations and edit them.
      - Synchronization settings
        The Synchronization settings page lets you customize the parameters related to Vantage or Central Management Console (CMC).
      - Alert playbooks
    - System
- User Guide
  Information and resources about the main features of Guardian, and the tasks that you can do from the user interface (UI).
- Maintenance Guide
  Information about the maintenance tasks of Guardian, to help you administer and maintain the solution in a production environment.
- Print format documentation
  A list of all the print-format documentation that is available for Guardian.

Tanium

This integration enables seamless forwarding of node and asset data to a Tanium instance, facilitating centralized management and enhanced visibility within your network.

You can select How this integration works to view additional details.

Note:

If the Tanium instance does not have a valid signed hypertext transfer protocol secure (HTTPS) certificate authority (CA), users must add an ! before the uniform resource locator (URL). For example, !https://192.168.1.1

Note:

Nodes are sent, not assets.

Note:

Nodes are sent regardless of whether media access control (MAC) addresses are confirmed or not (all nodes).

Note:

If integrating with the Central Management Console (CMC), use All-In-One mode. This is because multicontext a CMC does not have nodes.

Tanium dialog — Figure 1. Tanium dialog

Receive assets

The integration can be configured to receive asset data from Tanium. When configuring the integration to receive data, it is important to ensure that only one integration at a time is designated to interact with a specific endpoint. This means that if you have an integration set to receive data from an endpoint, another integration should not be set to send data to that same endpoint. This will help to avoid potential conflicts, or data inconsistencies.

Send assets

The integration can be configured to send asset data to Tanium. When configuring the integration to send data, it is important to ensure that only one integration at a time is designated to interact with a specific endpoint. This means that if you have an integration set to send data to an endpoint, another integration should not be set to receive data to that same endpoint. This will help to avoid potential conflicts, or data inconsistencies.