You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/ot-deploy/air-gapped-deploy.md
+5-45Lines changed: 5 additions & 45 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,10 @@ ms.date: 09/19/2023
9
9
10
10
Microsoft Defender for IoT helps organizations achieve and maintain compliance of their OT environment by providing a comprehensive solution for threat detection and management, including coverage across parallel networks. Defender for IoT supports organizations across the industrial, energy, and utility fields, and compliance organizations like NERC CIP or IEC62443.
11
11
12
+
> [!IMPORTANT]
13
+
> The legacy on-premises management console won't be supported or available for download after January 1st, 2025. We recommend transitioning to the new architecture using the full spectrum of on-premises and cloud APIs before this date. For more information, see [On-premises management console retirement](on-premises-management-console-retirement).
14
+
>
15
+
12
16
Certain industries, such as governmental organizations, financial services, nuclear power operators, and industrial manufacturing, maintain air-gapped networks. Air-gapped networks are physically separated from other, unsecured networks like enterprise networks, guest networks, or the internet. Defender for IoT helps these organizations comply with global standards for threat detection and management, network segmentation, and more.
13
17
14
18
While digital transformation has helped businesses to streamline their operations and improve their bottom lines, they often face friction with air-gapped networks. The isolation in air-gapped networks provides security but also complicates digital transformation. For example, architectural designs such as Zero Trust, which include the use of multi-factor authentication, are challenging to apply across air-gapped networks.
@@ -61,52 +65,8 @@ Use the following steps to deploy a Defender for IoT system in an air-gapped or
61
65
62
66
-**Configure a backup server**, including configurations to save your backup to an external server. For more information, see [Back up and restore OT network sensors from the sensor console](../back-up-restore-sensor.md).
63
67
64
-
## Transitioning from a legacy on-premises management console
65
-
66
-
> [!IMPORTANT]
67
-
> The [legacy on-premises management console](../legacy-central-management/legacy-air-gapped-deploy.md) won't be supported or available for download after January 1st, 2025. We recommend transitioning to the new architecture using the full spectrum of on-premises and cloud APIs before this date.
68
-
>
69
-
70
-
Our [current architecture guidance](#architecture-recommendations) 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.
71
-
72
-
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:
73
-
74
-
:::image type="content" source="../media/on-premises-architecture/transition.png" alt-text="Diagram of the transition from a legacy on-premises management console to the newer recommendations." border="false" lightbox="../media/on-premises-architecture/transition.png":::
75
-
76
-
-**In your legacy configuration**, all sensors are connected to the on-premises management console.
77
-
-**During the transition period**, your sensors remain connected to the on-premises management console while you connect any sensors possible to the cloud.
78
-
-**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.
79
-
80
-
**Use the following steps to transition your architecture:**
81
-
82
-
1. 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?
83
-
84
-
1. 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.
85
-
86
-
For more information, see the information linked in the [air-gapped deployment procedure](#deployment-steps), as well as the following cloud resources:
87
-
88
-
-[Provision sensors for cloud management](provision-cloud-management.md)
89
-
-[OT threat monitoring in enterprise SOCs](../concept-sentinel-integration.md)
90
-
-[Securing IoT devices in the enterprise](../concept-enterprise.md)
91
-
92
-
1. Set up permissions and update procedures for accessing your sensors to match the new deployment architecture.
93
-
94
-
1. Review and validate that all security use cases and procedures have transitioned to the new architecture.
95
-
96
-
1. After your transition is complete, decommission the on-premises management console.
97
-
98
-
### Retirement timeline of the Central Manager
99
-
100
-
The on-premises management console will be retired on **January 1, 2025** with the following updates/changes:
101
-
102
-
- Sensor versions released after **January 1, 2025** won't be managed by an on-premises management console.
103
-
- Air-gapped sensor support isn't affected by these changes to the on-premises management console support. We continue to support air-gapped deployments and assist with the transition to the cloud. The sensors retain a full user interface so that they can be used in "lights out" scenarios and continue to analyze and secure the network in the event of an outage.
104
-
- Air-gapped sensors that can't <!-- or don't / aren't connected to-->connect to the cloud can be managed directly via the sensor console GUI, CLI, or API.
105
-
- Sensor software versions released between **January 1st, 2024 – January 1st, 2025** still support the on-premises management console.
106
-
107
-
For more information, see [OT monitoring software versions](../release-notes.md).
108
68
109
69
## Next steps
110
70
111
71
> [!div class="step-by-step"]
112
-
> [Maintain OT network sensors from the sensor console](../how-to-manage-individual-sensors.md)
72
+
> [Transition from a legacy on-premises management console to the cloud](transition-on-premises-management-console-to-cloud.md)
title: On-premises management console retirement - Microsoft Defender for IoT
3
+
description: This article describes the retirement of the on-premises management console from **January 1, 2025**.
4
+
ms.topic: conceptual
5
+
ms.date: 12/17/2024
6
+
---
7
+
8
+
# On-premises management console retirement
9
+
10
+
This article describes the retirement of the on-premises management console from **January 1, 2025**.
11
+
12
+
### Retirement timeline of the Central Manager
13
+
14
+
The on-premises management console will be retired on **January 1, 2025** with the following updates/changes:
15
+
16
+
- Sensor versions released after **January 1, 2025** won't be managed by an on-premises management console.
17
+
- For versions released prior to **January 1, 2025**:
18
+
- You can still use the on-premises management console.
19
+
- In these versions, Defender for IoT no longer provides support service or maintains the on-premises management console.
20
+
21
+
For a list of supported versions, see [OT monitoring software versions](release-noted.md).
22
+
23
+
- Following any version upgrade, you will no longer be able to use the on-premises management console. For example, if you're using the on-premises management portal on version 24.1.2, and you upgrade to version 24.1.6, you can no longer use the on-premises management console.
24
+
- Air-gapped sensor support isn't affected by these changes to the on-premises management console support. We continue to support air-gapped deployments and assist with the transition to the cloud. The sensors retain a full user interface so that they can be used in "lights out" scenarios and continue to analyze and secure the network in the event of an outage.
25
+
- Air-gapped sensors that can't connect to the cloud can be managed directly via the sensor console GUI, CLI, or API. For more information, see [Transition from on-premises management console to the cloud](transition-from-on-premises-management-console-to-cloud).
26
+
27
+
## Next steps
28
+
29
+
> [!div class="step-by-step"]
30
+
> [Transition from a legacy on-premises management console to the cloud](transition-on-premises-management-console-to-cloud.md)
title: Transition from a legacy on-premises management console to the cloud
3
+
description: This article describes how to transition from the on-premises management console to the cloud.
4
+
ms.topic: how-to
5
+
ms.date: 12/17/2024
6
+
---
7
+
8
+
# Transition from a legacy on-premises management console to the cloud
9
+
10
+
This article describes how to transition from the on-premises management console to the cloud.
11
+
12
+
> [!IMPORTANT]
13
+
> The [legacy on-premises management console](../legacy-central-management/legacy-air-gapped-deploy.md) won't be supported or available for download after January 1st, 2025. For more information, see [On-premises management console retirement](on-premises-management-console-retirement).
14
+
>
15
+
16
+
Our [current architecture guidance](#architecture-recommendations) 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.
17
+
18
+
## Architecture guidance
19
+
20
+
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:
21
+
22
+
:::image type="content" source="../media/on-premises-architecture/transition.png" alt-text="Diagram of the transition from a legacy on-premises management console to the newer recommendations." border="false" lightbox="../media/on-premises-architecture/transition.png":::
23
+
24
+
## How to manage the transition period
25
+
26
+
-**In your legacy configuration**, all sensors are connected to the on-premises management console.
27
+
-**During the transition period**, your sensors remain connected to the on-premises management console while you connect any sensors possible to the cloud.
28
+
-**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.
29
+
30
+
## Transition your architecture
31
+
32
+
1. 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?
33
+
34
+
1. 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.
35
+
36
+
For more information, see the information linked in the [air-gapped deployment procedure](#deployment-steps), as well as the following cloud resources:
37
+
38
+
-[Provision sensors for cloud management](provision-cloud-management.md)
39
+
-[OT threat monitoring in enterprise SOCs](../concept-sentinel-integration.md)
40
+
-[Securing IoT devices in the enterprise](../concept-enterprise.md)
41
+
42
+
1. Set up permissions and update procedures for accessing your sensors to match the new deployment architecture.
43
+
44
+
1. Review and validate that all security use cases and procedures have transitioned to the new architecture.
45
+
46
+
1. After your transition is complete, decommission the on-premises management console.
47
+
48
+
## Next steps
49
+
50
+
> [!div class="step-by-step"]
51
+
> [Maintain OT network sensors from the sensor console](../how-to-manage-individual-sensors.md)
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/release-notes.md
+50-43Lines changed: 50 additions & 43 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,52 +31,59 @@ When updating your on-premises software, we recommend:
31
31
32
32
For more information, see [Update Defender for IoT OT monitoring software](update-ot-software.md).
33
33
34
-
### On-premises monitoring software versions
34
+
### OT monitoring software versions (sensor versions)
35
35
36
36
Cloud features may be dependent on a specific sensor version. Such features are listed below for the relevant software versions, and are only available for data coming from sensors that have the required version installed, or higher.
37
37
38
-
| Version / Patch | Release date | Scope | Supported until |
> The on-premises management console is being retired on **January 1, 2025**. The table below specifies whether each version includes the on-premises management console.
40
+
> - For versions where the management console is specified as included, you can use the on-premises management console, but no support service or maintenance is available.
41
+
> - For versions where the management console is specified as not included, you can't use or access the management console.
42
+
>
43
+
> For more information, see [On-premises management console retirement](on-premises-management-console-retirement).
44
+
45
+
| Version / Patch | Release date | Scope | Supported until |Management console |
The legacy on-premises management console won't be available for download after **January 1st, 2025**. We recommend transitioning to the new architecture using the full spectrum of on-premises and cloud APIs before this date. For more information, see [On-premises management console retirement](on-premises-management-console-retirement).
0 commit comments