Transition from a legacy on-premises management console to the cloud
This article describes how to transition from the on-premises management console to the cloud.
Important
The on-premises management console won't be supported or available for download after January 1st, 2025. For more information, see on-premises management console retirement.
Our current architecture guidance is designed to be more efficient, secure, and reliable than using the legacy on-premises management console. The updated guidance has fewer components, which makes it easier to maintain and troubleshoot. The smart sensor technology used in the new architecture allows for on-premises processing, reducing the need for cloud resources and improving performance. The updated guidance keeps your data within your own network, providing better security than cloud computing.
Architecture guidance
If you're an existing customer using an on-premises management console to manage your OT sensors, we recommend transitioning to the updated architecture guidance. The following image shows a graphical representation of the transition steps to the new recommendations:
How to manage the transition period
- In your legacy configuration, all sensors are connected to the on-premises management console.
- During the transition period, your sensors remain connected to the on-premises management console while you connect any sensors possible to the cloud.
- After fully transitioning, you'll remove the connection to the on-premises management console, keeping cloud connections where possible. Any sensors that must remain air-gapped are accessible directly from the sensor UI.
Transition your architecture
For each of your OT sensors, identify the legacy integrations in use and the permissions currently configured for on-premises security teams. For example, what backup systems are in place? Which user groups access the sensor data?
Connect your sensors to on-premises, Azure, and other cloud resources, as needed for each site. For example, connect to an on-premises SIEM, proxy servers, backup storage, and other partner systems. You may have multiple sites and adopt a hybrid approach, where only specific sites are kept completely air-gapped or isolated using data-diodes.
For more information, see the information linked in the air-gapped deployment procedure, as well as the following cloud resources:
Set up permissions and update procedures for accessing your sensors to match the new deployment architecture.
Review and validate that all security use cases and procedures have transitioned to the new architecture.
After your transition is complete, decommission the on-premises management console.