--- sourceDocument: Australia Operational Technology Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/operational-technology Release : - australia ft:locale : - en-US ft:publication_title : - Australia Operational Technology Management ft:clusterId : - optm bundleId : - optm workflow : - Technology --- # OT Discovery Deployment scenarios # OT Discovery deployment scenarios {#ariaid-title1} Release version: Australia Updated March 24, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of OT Discovery deployment scenarios OT Discovery deployment scenarios vary based on the architecture of your operational technology (OT) network. These scenarios guide you in deploying OT Discovery components effectively within your OT environment. Key factors include network segmentation, communication pathways, traffic loads, redundancy, and environmental conditions. The OT Discovery Collector can be co-located with the Discovery Sensor for OT for streamlined deployment. Show full answer Show less ## Deployment Scenarios * **Flat Network Architecture Across Multiple Sites:** This design features all Discovery Console for OT, Discovery Sensor for OT, and OT Discovery Collector components connected within a single network where direct communication is possible. One Console can manage multiple sites. Consoles should be deployed at a network layer accessible by the MID Server and the ServiceNow instance. Sensors are placed according to desired discovery speed; more Sensors increase discovery performance. Typically, the Console and Sensors operate at Purdue level 3.5, pushing data through switches and firewalls to ServiceNow. * **Multiple Independent Segmented Sites:** Networks are divided into multiple isolated segments with no inter-site communication. Each segment acts as an independent flat network with its own Discovery Console for OT, Sensors, and Collectors. This segmentation enhances security and operational clarity by isolating zones such as Operational Technology segments and Physical Security networks. Consoles and Sensors operate locally, managing credentials, protocols, and discovery operations without direct internet access. * **Micro-segmented Site with Multiple Networks:** This network design includes multiple segments within sites, each containing several network segments. Each segment deploys its own Discovery Console for OT and Sensors. Sensors must have communication pathways to their Console and be capable of performing active discovery and protocol queries (e.g., Modbus, DNP3, BACnet). OT Discovery Collectors can be installed on existing hosts such as HMIs or Engineering Workstations to facilitate discovery in specific segments. ## Key Components and Considerations * **Discovery Console for OT:** Acts as the command-and-control center for asset discovery, managing credentials, protocol handlers, and initiating scans within its segment. * **Discovery Sensor for OT:** Performs active discovery, collects network traffic, and queries known OT protocols, reporting findings to the Console. * **OT Discovery Collector:** Supports discovery processes and can be co-deployed with Sensors or installed on existing OT hosts. When planning your deployment, ensure Sensors and Collectors have appropriate communication pathways to their Consoles, and consider environmental factors and network architecture to optimize discovery speed and security. For detailed resource requirements, refer to the OT Discovery System Resources documentation. Deployment scenarios for OT Discovery vary based on a network's architecture. Use these scenarios to help determine how to deploy the OT Discovery components in your OT environment. Note: The OT Discovery Collector can be deployed to the same locations as the Discovery Sensor for OT. ## General recommendations {#deployment-scenarios__general-requirements} General recommendations and guidance are listed in each scenario in these sections. Not all networks are the same. The requirements in this section are a generalization for the scenario. Consider factors such as segmentation level, communication pathways, network traffic, redundancy, and environmental conditions. For resource recommendations for the OT Discovery components see, [OT Discovery System Resources](https://www.servicenow.com/docs/tolf~qFiLKjZV~Bu62rbPQ "You can review the OT Discovery component resources before setting up your OT network."). ## Flat network architecture across multiple sites {#deployment-scenarios__section_smf_pb4_zfc} A flat network architecture is a network design that has all available Discovery Console for OT, Discovery Sensor for OT, and OT Discovery Collector connected to a single network, where the Sensors and Collectors can communicate with each other directly. You can have one or more sites that communicate with each other.Figure 1. Flat network The Console, Sensors, and MID Server connect at Purdue level 3.5 and push data through the switches and the firewall to the ServiceNow instance for ingestion. **Components in the flat network** The following are the components in a flat network. * Discovery Console for OT and Discovery Sensor for OT. * A localized appliance or VM that serves as the command-and-control interface for asset discovery and communication in its respective segment. This appliance or VM manages credentials, protocol handlers, and initiates querying operations locally. In such a scenario, a typical deployment means that one Console covers multiple sites. * Deploy the Console at a layer where the MID Server can connect to the Console and the ServiceNow instance. * Deploy Sensors based on the desired speed of the discovery. In a truly flat network, a Discovery Sensor for OT can reach all the OT assets in that network. More Sensors in the network can help improve the speed of discovery. {#deployment-scenarios__ul_lhs_yhv_5gc} ## Multiple independent segmented sites {#deployment-scenarios__section_lyd_sb4_zfc} A segmented site architecture is a network design that has the network split into multiple segments. Each segment contains its own Discovery Console for OT and multiples of the Discovery Sensor for OT and the OT Discovery Collector. There is no communication between sites. Each of the segments could be considered a flat network. Figure 2. Segmented sites In this OT environment, the network is segmented into three distinct zones for operational clarity, security, and control: * Site 1 Operational Technology segment * Site 2 Operational Technology segment * Physical Security Network segment {#deployment-scenarios__ul_nyb_jt2_3gc} Each segment contains its own isolated infrastructure to reduce risk and increase visibility in its respective domain. Components in each segment: * Discovery Console for OT or VM that serves as the command-and-control interface for asset discovery and communication in its respective segment. It manages credentials, protocol handlers, and initiates scanning operations locally. * Discovery Sensor for OT is deployed in each segment. The Sensor performs active discovery, collects network traffic, and queries for known protocols (for example, Modbus, DNP3, BACnet). It reports findings to its segment's Console. {#deployment-scenarios__ul_inc_352_3gc} The Consoles and Sensors are deployed in their respective network zones and don't have direct outbound access to the internet. ## Micro-segmented site with multiple networks {#deployment-scenarios__section_npc_tb4_zfc} A segmented site architecture with multiple networks is a network design that has more than one network split into multiple segments. Each segment contains multiple network segments and its own Discovery Console for OT and Discovery Sensor for OT. * Make sure the Sensors and Collectors have a communication pathway to the Console. * Deploy Sensors in each segment where the Sensor can perform active discovery in the segment and collect network traffic and can scan or query for known protocols (for example, Modbus, DNP3, BACnet). It reports findings to its segment's Console. * If you use an existing host to do the discovery in the network such as Human Machine Interface (HMI) or Engineering Workstation (EWS), you can install the OT Discovery Collector to perform discovery. {#deployment-scenarios__ul_knq_xjv_5gc}Figure 3. Segmented site with multiple networks