OT Discovery communications

This section describes how the OT Discovery components should be connected so they can communicate with each other.

Component communications

When determining the environment architecture for your deployment, consider how the following OT Discovery components interact.

• MID Server-to-ServiceNow instance:

  • The MID Server needs to communicate with the ServiceNow instance to push the information from Discovery Console for OT.

    Note: If the Discovery Console for OT can reach the internet, the MID Server might not be needed in your OT configuration.

  • This configuration and deployment is the same as with any other MID Server.

  • The Service Graph Connector (SGC) needs to communicate with the MID Server, the Console, and the ServiceNow instance.

  • Console-to-MID Server communication:

  • Deploy a separate MID Server for each network or network segment.

  • Configure firewall rules to enable communication across networks or network segment boundaries.
  • The Console needs to communicate with the Sensors, the Collectors, the MID Server, the SGC, and your ServiceNow instance.

• Sensor-to-Console communication:
  • Deploy a separate Console for each network, network segment, or system.
  • Configure firewall rules to enable communication across networks or network segment boundaries.
  • The Discovery Sensor for OT needs to communicate with OT assets and with the Discovery Console for OT.
  • Discovery Sensor for OT data is pushed to the ServiceNow instance by the Service Graph Connector.
• Sensor-to-asset communication:
  • Deploy a separate Sensor for each network, network segment, or system.
  • Configure firewall rules to enable communication across network, network segment, or system boundaries.
• Discovery OT Collector-to-Console communication:
  • Discovery OT Collector needs to communicate with the Console.
  • The Collector communicates with the Console and with your system's assets.

Network port map

The following table describes how to set up network ports.